This International Standard provides a standard interface to hardware biometric modules designed to be integrated in embedded systems which can be constrained in memory and computational power. This International Standard specifies a full interface for such hardware-based biometric modules. This interface, called Embedded BioAPI, is defined by the specification of commands to be implemented by these modules. Such a specification is done in two levels:<\/p>\n
For low level implementations, a frame definition is provided, as well as the coding of all commands and their relevant responses. Being defined as a single-master\/multiple-slave half-duplex protocol, these messages can be implemented over any communication interface at the physical and link layers. The definition of such communication interfaces is outside of the scope of this International Standard.<\/p>\n<\/li>\n
A C-based function header description, for those manufacturers that want to provide a C-library for integration as a Software Development Kit for the overall embedded system.<\/p>\n<\/li>\n<\/ul>\n
Regarding security, this International Standard defines two kinds of devices:<\/p>\n
Type A: devices that, due to lack of processing capabilities, do not implement any kind of security mechanism.<\/p>\n<\/li>\n
Type B: devices that implement security mechanisms for achieving confidentiality, integrity and\/or authenticity. Use of the Type B kind of devices is recommended. For Type B devices a set of minimum requirements is defined, but the security mechanisms to be used are out of the scope of this International Standard.<\/p>\n<\/li>\n<\/ul>\n
Low level implementation is outside of the scope of the normative part of this International Standard, although an informative annex (see Annex B) is provided.<\/p>\n
Security mechanisms, although considered in this International Standard, are outside of the scope of this International Standard, and are referred to other relevant standards. In particular, key management is outside of the scope of this International Standard, and is expected to be done prior to the application of this International Standard.<\/p>\n
Specifications and requirements for Embedded BioAPI subcomponents, or any kind of devices suitable to implement Embedded BioAPI, are outside of the scope of this International Standard.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 9<\/td>\n | 1 Scope 2 Conformance <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 3 Normative references 4 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 5 Symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 6 Embedded BioAPI environment 6.1 Operating environment of Embedded BioAPI <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 6.2 Security in Embedded BioAPI 7 Embedded BioAPI general architecture <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 8 Frames structure <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 9 Patron format for Embedded BioAPI 10 Security block format for Embedded BioAPI 10.1 Security Block format owner 10.2 Security Block format owner identifier 10.3 Security Block format name 10.4 Security Block format identifier <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 10.5 ASN.1 object identifier for this security Block format 10.5.1 The case of BER encodings 10.5.2 The case of canonical XER encodings 10.6 Domain of use 10.7 Version identifier 10.8 CBEFF version 10.9 General 10.10 Specification <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 11 Data types, formats and coding 11.1 Slave ID field [S] 11.2 Command field [C] <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 11.3 Status\/Error field [E] 11.4 Biometric modalities coding <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 12 Commands definition <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 12.1 Management commands 12.1.1 emBioAPI_BSPAttach (mandatory) <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 12.1.2 emBioAPI_BSPDetach (mandatory) 12.1.3 emBioAPI_QueryUnit (mandatory) <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 12.1.4 emBioAPI_ControlUnit <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 12.1.5 emBioAPI_Cancel 12.2 Template management commands 12.2.1 emBioAPI_DBStoreBIR (onboard template storage) <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 12.2.2 emBioAPI_DBGetBIR (onboard template storage) 12.2.3 emBioAPI_DeleteBIR (mandatory for devices with template storage capabilities) <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 12.3 Enrolment commands 12.3.1 emBioAPI_Capture4Enrol 12.3.2 emBioAPI_GetBIR <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 12.3.3 emBioAPI_CreateTemplate <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 12.4 Biometric process commands 12.4.1 emBioAPI_Capture 12.4.2 emBioAPI_Process <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 12.4.3 emBioAPI_CaptureProcess <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 12.4.4 emBioAPI_VerifyExternal 12.4.5 emBioAPI_VerifyMatchExternal <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 12.4.6 emBioAPI_ProcessVerifyMatchExternal <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 12.4.7 emBioAPI_VerifyInternal <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 12.4.8 emBioAPI_VerifyMatchInternal <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 12.4.9 emBioAPI_ProcessVerifyMatchInternal <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Information technology. Biometrics. Embedded BioAPI<\/b><\/p>\n |