| Revision as of 05:21, 23 July 2013 editShavaiz Shams (talk | contribs)92 editsmNo edit summaryTag: Visual edit← Previous edit | Latest revision as of 17:56, 3 November 2022 edit undoFerien (talk | contribs)Extended confirmed users, Pending changes reviewers, Rollbackers26,806 editsm Reverted edits by 112.135.69.172 (talk) to last revision by 129.126.238.50: addition of unnecessary/inappropriate external linksTags: Rollback SWViewer [1.4] | ||
| (29 intermediate revisions by 22 users not shown) | |||
| Line 1: | Line 1: | ||
| {{Short description|Biometric Interworking Protocol}} | |||
| ] | ] | ||
| ⚫ | '''BioAPI''' ('''Biometric Application Programming Interface''') is a key part of the International Standards that support systems that perform biometric enrollment and verification (or identification). It defines interfaces between modules that enable software from multiple vendors to be integrated together to provide a biometrics application within a system, or between one or more systems using a defined Biometric Interworking Protocol (BIP) – see below. | ||
| '''BioAPI''' '''(Biometric Application Programming Interface)''' | |||
| ⚫ | is a key part of the International Standards that support systems that perform biometric enrollment and verification (or identification). It defines interfaces between modules that enable software from multiple vendors to be integrated together to provide a biometrics application within a system, or between one or more systems using a defined Biometric Interworking Protocol (BIP) |
||
| ] (measurements of physical characteristics of a person) are increasingly being used to provide verification of the identity of an individual, once they have been enrolled (one or more of their physical characteristics has been measured). | ] (measurements of physical characteristics of a person) are increasingly being used to provide verification of the identity of an individual, once they have been enrolled (one or more of their physical characteristics has been measured). | ||
| Line 10: | Line 10: | ||
| ==Origins== | ==Origins== | ||
| The BioAPI specification is one of a set of International Standards produced jointly by the ] and the ] under their ], ]. | |||
| The BioAPI specification is one of a set of International Standards | |||
| produced combines by the ] and the | |||
| [[International Electrotechnical Commission| International | |||
| Electrotechnical Commission (IEC)]] under their [[International Organization for Standardization| Joint Technical Committee 1 (JTC1), Subcommittee | |||
| SC37 Biometrics]]. | |||
| The Standard was based on some early work done in the United States of | The Standard was based on some early work done in the United States of America and by the | ||
| ⚫ | which was called BioAPI 1.0 and BioAPI 1.1, but these specifications were revised and extended when the work | ||
| America and by the | |||
| ⚫ | which was called BioAPI 1.0 and BioAPI 1.1, but these specifications were | ||
| heavily revised to correct bugs and to provide enhancements when the work | |||
| was introduced to ISO/IEC. The first international version | was introduced to ISO/IEC. The first international version | ||
| was therefore called BioAPI 2.0. A subsequent international version of BioAPI | was therefore called BioAPI 2.0. A subsequent international version of BioAPI | ||
| Line 31: | Line 25: | ||
| ==What and why?== | ==What and why?== | ||
| The purpose of the BioAPI specification is to define an architecture | The purpose of the BioAPI specification is to define an architecture and all necessary interfaces (using C programming language | ||
| ⚫ | specifications) to allow biometric applications (perhaps distributed across a network) to be integrated from modules provided by different vendors. | ||
| and all necessary interfaces (using C programming language | |||
| specifications) to allow biometric applications (perhaps distributed | |||
| ⚫ | across a network) to be integrated from modules provided by different | ||
| vendors. | |||
| The ability for system |
The ability for system integrator to produce complete systems using | ||
| components from multiple vendors is essential in the rapidly changing | components from multiple vendors is essential in the rapidly changing | ||
| technology of biometrics. It gives flexibility in the provision of | technology of biometrics. It gives flexibility in the provision of modules, avoids ], provides a degree of future-proofing as the best available biometrics technologies change. | ||
| modules, avoids ], provides a degree of future-proofing as | |||
| the best available biometrics technologies change. | |||
| The modules being integrated may be software components containing | The modules being integrated may be software components containing | ||
| capture devices, such as fingerprint readers, cameras for face recognition, iris | capture devices, such as fingerprint readers, cameras for face recognition, iris scanners, ] devices, vascular imaging systems, etc. | ||
| scanners, signature recognition devices, vascular imaging systems, etc. | |||
| They can also be modules that provide support for image processing of biometric data, feature extraction (a form of compression that is specific to a given biometric technology and allows direct matching of the compressed formats – for example, the relative distances on the face of eyes, nose, mouth, or the number of ridges between identifiable ridge endings or ridge bifurcations). | |||
| They can also be modules that provide support for image | |||
| processing of biometric data, feature extraction (a form of compression | |||
| that is specific to a given biometric technology and allows direct | |||
| matching of the compressed formats.For example, the relative distances | |||
| on the face of eyes, nose, mouth, or the number of ridges between | |||
| identifiable ridge endings or ridge bifurcations). | |||
| In addition, modules that provide archiving and retrieval of biometric | In addition, modules that provide archiving and retrieval of biometric records to support matching or searching for a match are also a recognized part of the BioAPI architecture. | ||
| records to support matching or searching for a match are also a | |||
| recognised part of the BioAPI architecture. | |||
| Applications can be concerned with personal identification (for example for credit cards), or with more specific areas such as identity card verification, checks for duplicate enrollment, passports, or physical access control in a commercial environment or for airport employees or merchant seamen wishing to go on-shore at their arrival port. | |||
| Applications can be concerned with personal identification (for | |||
| example for credit cards), or with more specific areas such as identity | |||
| card verification, checks for duplicate enrolment , passports, or physical | |||
| access control in a commercial environment or for airport employees or | |||
| merchant seamen wishing to go on shore at their arrival port. | |||
| Whilst today a system is commonly built using a single device for a single application, it is likely that in the long term many such applications will interact (securely, and via a network) with a common set of trusted devices (with various security policies and certificates). | |||
| single application, it is likely that in the long term many such | |||
| applications will interact (securely, and via a network) with a common | |||
| set of trusted devices (with various security policies and certificates). | |||
| It is also expected that future biometrics applications will use | It is also expected that future biometrics applications will use multiple biometric modalities (for example, fingerprint, iris, and face), | ||
| ⚫ | both to improve the accuracy of identification and to cope with people that are missing a finger, or have disability problems that prevent use of iris or face recognition. | ||
| multiple biometric modalities (for example fingerprint, iris and face), | |||
| ⚫ | both to improve the accuracy of identification and to cope with people that | ||
| missing a finger, or have disability problems that prevent use of iris or | |||
| face recognition. | |||
| '''BioAPI supports all these use cases.''' | '''BioAPI supports all these use cases.''' | ||
| Line 79: | Line 50: | ||
| ==The basic architecture== | ==The basic architecture== | ||
| The basic architecture of BioAPI 2.0 is illustrated in the figure at the top of this page. There are multiple possible (independent) ''biometric applications'' that interact with a ''BioAPI Framework'', which in turn routes their messages to ''Biometric Service Providers (BSPs)'' that support the various biometric capture devices, image enhancement modules, feature extraction, matching, searching, etc. | |||
| The basic architecture of BioAPI 2.0 is illustrated in the figure at | |||
| the top of this page. There are multiple possible (independent) | |||
| ''biometric applications'' that | |||
| interact with a ''BioAPI Framework'', which in turn routes their | |||
| messages to ''Biometric Service Providers (BSPs)'' that support the | |||
| various biometric capture devices, image | |||
| enhancement modules, feature extraction, matching, searching, etc. | |||
| A later extension of the architecture introduces the concept of a ''Biometric Function Provider (BFP)'' and defines further lower-level interfaces between a BFP and a controlling BSP. This minimizes the amount of software that a biometric device vendor needs to develop, allowing (other) software vendors to do most of the work of producing the BSP with an interface to the framework. | |||
| A later extension of the architecture introduces the concept of a | |||
| ''Biometric Function Provider (BFP)'' and defines further lower-level | |||
| interfaces between a BFP and a controlling BSP. This minimises the | |||
| amount of software that a biometric device vendor needs to | |||
| develop, allowing other software vendors to do most of the work of | |||
| producing the BSP with an interface to the framework. | |||
| ==Procurement issues== | ==Procurement issues== | ||
| The ''BioAPI Framework'' is the heart of BioAPI. |
The ''BioAPI Framework'' is the heart of BioAPI. Procurement of biometric systems need to consider the merits of basing their invitations-to-tender on systems conforming to the BioAPI Standard, which contain a BioAPI Framework module. | ||
| biometric systems need to consider the merits of basing their | |||
| invitations-to-tender on systems conforming to the BioAPI Standard, | |||
| which contain a BioAPI Framework module. | |||
| ⚫ | The importance of this Framework module is recognized by the , which identifies an implementation of this Framework from BioFoundry. | ||
| The importance of this Framework module is recognised by | |||
| ⚫ | the , which identifies an implementation of this Framework | ||
| from . | |||
| ==Distributed systems== | ==Distributed systems== | ||
| Line 109: | Line 64: | ||
| It might be uncommon to find multiple biometric applications and | It might be uncommon to find multiple biometric applications and | ||
| multiple biometric devices on a single computer system, but the long-term | multiple biometric devices on a single computer system, but the long-term | ||
| aim of ] is to allow | aim of ] is to allow multiple biometrics applications on multiple systems on the Internet to interwork with multiple other systems that support biometrics devices. | ||
| multiple biometrics applications on multiple systems on the Internet to | |||
| interwork with multiple other systems that support biometrics devices. | |||
| BioAPI has already laid the foundations for this, with its | BioAPI has already laid the foundations for this, with its | ||
| architecture. | architecture. | ||
| Another ISO/IEC |
Another ISO/IEC JTC 1/SC 37 Standard – BioAPI Interworking Protocol (BIP) – specifies an enhancement of the BioAPI Framework that essentially maps all API calls into network messages (defined using ]) to provide a distributed BioAPI system. | ||
| (BIP) - specifies an enhancement of the BioAPI Framework that essentially | |||
| maps all API calls into network messages (defined using ]) to provide a distributed BioAPI system. | |||
| BIP is also being progressed as a Recommendation in ] as | BIP is also being progressed as a Recommendation in ] as Joint text with ISO/IEC. | ||
| Joint text with ISO/IEC. | |||
| ==References== | ==References== | ||
| ISO/IEC 19784-1, ''Information Technology – BioAPI – Biometric Application Programming Interface – Part 1: BioAPI Specification'' | * ISO/IEC 19784-1, ''Information Technology – BioAPI – Biometric Application Programming Interface – Part 1: BioAPI Specification'' | ||
| ISO/IEC 24708, ''Information Technology — BioAPI Interworking Protocol (BIP)'' | * ISO/IEC 24708, ''Information Technology — BioAPI Interworking Protocol (BIP)'' | ||
| ] | ] | ||
Latest revision as of 17:56, 3 November 2022
Biometric Interworking Protocol
BioAPI (Biometric Application Programming Interface) is a key part of the International Standards that support systems that perform biometric enrollment and verification (or identification). It defines interfaces between modules that enable software from multiple vendors to be integrated together to provide a biometrics application within a system, or between one or more systems using a defined Biometric Interworking Protocol (BIP) – see below.
Biometrics (measurements of physical characteristics of a person) are increasingly being used to provide verification of the identity of an individual, once they have been enrolled (one or more of their physical characteristics has been measured).
Computer systems that perform biometric enrollment, verification, or identification are becoming increasingly used. The BioAPI specification enables such systems to be produced by the integration of modules from multiple independent vendors.
Origins
The BioAPI specification is one of a set of International Standards produced jointly by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) under their Joint Technical Committee 1 (JTC1), Subcommittee 37 on Biometrics.
The Standard was based on some early work done in the United States of America and by the BioAPI Consortium which was called BioAPI 1.0 and BioAPI 1.1, but these specifications were revised and extended when the work was introduced to ISO/IEC. The first international version was therefore called BioAPI 2.0. A subsequent international version of BioAPI containing extensions of the user interface-related features and other enhancements produced a BioApi 2.1. Further enhancements to BioAPI are expected.
BioAPI 2.0 is specified in ISO/IEC 19784-1 and was first published on 1 May 2006.
What and why?
The purpose of the BioAPI specification is to define an architecture and all necessary interfaces (using C programming language specifications) to allow biometric applications (perhaps distributed across a network) to be integrated from modules provided by different vendors.
The ability for system integrator to produce complete systems using components from multiple vendors is essential in the rapidly changing technology of biometrics. It gives flexibility in the provision of modules, avoids vendor lock-in, provides a degree of future-proofing as the best available biometrics technologies change.
The modules being integrated may be software components containing capture devices, such as fingerprint readers, cameras for face recognition, iris scanners, signature recognition devices, vascular imaging systems, etc.
They can also be modules that provide support for image processing of biometric data, feature extraction (a form of compression that is specific to a given biometric technology and allows direct matching of the compressed formats – for example, the relative distances on the face of eyes, nose, mouth, or the number of ridges between identifiable ridge endings or ridge bifurcations).
In addition, modules that provide archiving and retrieval of biometric records to support matching or searching for a match are also a recognized part of the BioAPI architecture.
Applications can be concerned with personal identification (for example for credit cards), or with more specific areas such as identity card verification, checks for duplicate enrollment, passports, or physical access control in a commercial environment or for airport employees or merchant seamen wishing to go on-shore at their arrival port.
Whilst today a system is commonly built using a single device for a single application, it is likely that in the long term many such applications will interact (securely, and via a network) with a common set of trusted devices (with various security policies and certificates).
It is also expected that future biometrics applications will use multiple biometric modalities (for example, fingerprint, iris, and face), both to improve the accuracy of identification and to cope with people that are missing a finger, or have disability problems that prevent use of iris or face recognition.
BioAPI supports all these use cases.
The basic architecture
The basic architecture of BioAPI 2.0 is illustrated in the figure at the top of this page. There are multiple possible (independent) biometric applications that interact with a BioAPI Framework, which in turn routes their messages to Biometric Service Providers (BSPs) that support the various biometric capture devices, image enhancement modules, feature extraction, matching, searching, etc.
A later extension of the architecture introduces the concept of a Biometric Function Provider (BFP) and defines further lower-level interfaces between a BFP and a controlling BSP. This minimizes the amount of software that a biometric device vendor needs to develop, allowing (other) software vendors to do most of the work of producing the BSP with an interface to the framework.
Procurement issues
The BioAPI Framework is the heart of BioAPI. Procurement of biometric systems need to consider the merits of basing their invitations-to-tender on systems conforming to the BioAPI Standard, which contain a BioAPI Framework module.
The importance of this Framework module is recognized by the BioAPI Consortium, which identifies an implementation of this Framework from BioFoundry.
Distributed systems
It might be uncommon to find multiple biometric applications and multiple biometric devices on a single computer system, but the long-term aim of telebiometrics is to allow multiple biometrics applications on multiple systems on the Internet to interwork with multiple other systems that support biometrics devices.
BioAPI has already laid the foundations for this, with its architecture.
Another ISO/IEC JTC 1/SC 37 Standard – BioAPI Interworking Protocol (BIP) – specifies an enhancement of the BioAPI Framework that essentially maps all API calls into network messages (defined using ASN.1) to provide a distributed BioAPI system.
BIP is also being progressed as a Recommendation in ITU-T as Joint text with ISO/IEC.
References
- ISO/IEC 19784-1, Information Technology – BioAPI – Biometric Application Programming Interface – Part 1: BioAPI Specification
- ISO/IEC 24708, Information Technology — BioAPI Interworking Protocol (BIP)