Download:
pdf |
pdfDepartment of Defense
Electronic Biometric Transmission
Specification
8 DECEMBER 2011
Version 3.0
DIN: BIMA-STB-STD-11-001
U N C L A S S I F I E D - DI S T R I B UT I O N U NL I M I T E D
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Revision History
Draft
Version
Date
Document Status
Participants/Comments
0.1 Draft 1
8 March
Initial Draft
Call for comments
0.2 Draft 2
30 September
Second Draft
Call for comments
1.0 Final
17 November
Final
Letter Ballot
1.0 Final
8 December
Approved Final
Version
BSWG and BIMA Internal Staffing Approval
Change Requests
CR ID
1
2
3
4
5
6
7
8
9
10
11
12
13
Change Request (CR) Description
Support of data fields for blue force biometrics with DoD Enterprise functionality in Integrated
Data Dictionary (IDD) (Fields listed as emerging in IDD)
Reinstate Encounter Protection, BAT GUID, Internment Serial Number, DoD Number,
Electronic Data Interchange Personnel Identifier, Defense Biometric Identification System,
Biometric Subject Personnel Type, Request Mug Shot, Request IAFIS Search, and XML-Based
Rap Sheet fields
Support FBI EFTS 7.1 – Include all FBI EBTS v9.3 mandatory data fields identified by Base
Application Profile (BAP)
Support Base Access fields with DoD Enterprise functionality as identified in the BAT-A v5
Application Profile
Support of International Caveat
Synchronization with the IDD
Fixes to EBTS v2.0 (i.e., mnemonics and field assignments)
Implement business rules for FBI legacy fields used in EBTS v3.0 and the BAP
Restructuring of certain Type-2 data fields to improve alignment to FBI EBTS v9.3 and NIEM
Adoption of Type-18, 20, 21, and 98 Records from ANSI/NIST ITL 1-2011
Additional guidelines on image formats and compressions adopted from ITL 1-2011
Support of missing palm omitted and facial image omitted indicators in Type-2
Update EBTS to support existing records in ITL 1-2011
i
UNCLASSIFIED - DISTRIBUTION UNLIMITED
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
TABLE OF CONTENTS
1.0
1.1
1.2
1.3
1.4
1.5
2.0
2.1
2.2
2.3
2.4
2.5
2.6
2.7
3.0
3.1
3.2
3.3
3.4
3.5
3.6
4.0
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13
INTRODUCTION .............................................................................................................. 1
Background ..................................................................................................................... 1
Scope and Purpose .......................................................................................................... 2
References ....................................................................................................................... 3
Change Control ............................................................................................................... 4
Contact Information ........................................................................................................ 4
CONFORMANCE AND UNIQUE REQUIRMENTS ...................................................... 5
Application Profile .......................................................................................................... 5
DoD EBTS Domain ........................................................................................................ 5
Conformance and Testing ............................................................................................... 6
DoD ABIS Backward Compatibility .............................................................................. 6
Character Encoding......................................................................................................... 6
Structure of a Mnemonic ................................................................................................ 7
Encounter Protection ....................................................................................................... 7
DoD EBTS TRANSACTIONS........................................................................................... 8
Record Types .................................................................................................................. 8
Transaction Control Numbers ....................................................................................... 11
Origination Identifiers ................................................................................................... 12
Tagged Fields ................................................................................................................ 12
Error Handling .............................................................................................................. 13
Image Quality and Image Sets Requirements ............................................................... 14
DoD EBTS RECORDS AND FIELDS ............................................................................ 17
Type-1 Records [Transaction Information] .................................................................. 17
Type-2 Records [User-Defined Descriptive Text] ........................................................ 20
Type-9 Records [Minutiae Data] .................................................................................. 34
Type-10 Records [Facial & SMT] ................................................................................ 40
Type-13 Records [Variable-Resolution Latent Image]................................................. 46
Type-14 Records [Var-Res Fingerprint Image] ............................................................ 49
Type-15 Records [Var-Res Palmprint Image] .............................................................. 53
Type-17 Records [Iris Image] ....................................................................................... 56
Type-18 Records [DNA Record] .................................................................................. 61
Type-20 Record [Source Representation Record] ........................................................ 65
Type-21 Record [Associated Context Record] ............................................................. 69
Type-98 Record [Information Assurance Record] ....................................................... 72
Type-99 Records [CBEFF Biometric Data Record] ..................................................... 74
Appendix A: Change Request Template....................................................................................... 77
Department of Defense Electronic Biometric Transmission Specification Change Request
(CR) Submission Form ............................................................................................................. 77
ii
UNCLASSIFIED - DISTRIBUTION UNLIMITED
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
LIST OF FIGURES
Figure 1: Transaction Submission and Response Sequence ........................................................ 11
Figure 2: TCN Layout .................................................................................................................. 12
LIST OF TABLES
Table 1: Logical Records ............................................................................................................... 8
Table 2: Response to Unrecognized Reception ........................................................................... 14
Table 3: Type-1 Transaction Information Record Layout ........................................................... 18
Table 4: Type-2 User-Defined Descriptive Text Record Layout ................................................ 24
Table 5: Type-9 Minutiae Data Record Layout (IAFIS Features) ............................................... 35
Table 6: Type-9 Minutiae Data Record Layout (INCITS-378 Features) .................................... 37
Table 7: Type-10 Facial and SMT Record Layout ...................................................................... 41
Table 8: Type-13 Variable-Resolution Latent Record Layout .................................................... 47
Table 9: Type-14 Variable-Resolution Fingerprint Record Layout ............................................ 50
Table 10: Type-15 Variable-Resolution Palmprint Record Layout ............................................. 54
Table 11: Type-17 Iris Image Record Layout.............................................................................. 57
Table 12: Type-18 DNA Data Record Layout .............................................................................. 62
Table 13: Type-20 Source Representation Record Layout .......................................................... 66
Table 14: Type-21 Associated Context Record Layout ................................................................ 70
Table 15: Type-98 Information Assurance Record Layout .......................................................... 73
Table 16: Type-99 CBEFF Biometric Data Record Layout ........................................................ 75
iii
UNCLASSIFIED - DISTRIBUTION UNLIMITED
Electronic Biometric Transmission Specification Version 3.0
1.0
DIN: BIMA-STB-STD-11-001
INTRODUCTION
This Department of Defense (DoD) Electronic Biometric Transmission Specification (EBTS) is based
on the American National Standards Institute (ANSI)/National Institute of Standards and Technology
(NIST) Information Technology Laboratory specification number 1-2011 (ITL 1-2011). The DoD’s
EBTS builds upon the ITL 1-2011 to meet DoD requirements via additions to and customizations of the
ITL 1-2011 data format.
1.1 Background
The DoD EBTS was originally developed as an interface to the DoD Automated Biometric
Identification System (ABIS). The DoD ABIS is an electronic database and an associated set of
software applications that support the storage, retrieval, and searching of fingerprint and latent data
collected from persons of national security interest. The DoD ABIS was designed to be similar to the
FBI Criminal Justice Information Services (CJIS) Integrated Automated Fingerprint Identification
System (IAFIS) and therefore its interface was based on the FBI’s Electronic Fingerprint Transmission
Specification (EFTS). Because of the different nature of DoD encounters and detainment
circumstances, the DoD has additional operational requirements beyond those defined in the FBI EFTS.
The DoD-unique capabilities are defined in the DoD EBTS.
Following extensive expert review and multiple revisions, the first widely distributed version (version
1.2) of the DoD EBTS was released in November 2006. That document described a set of capabilities
that had been implemented in the DoD Biometric Enterprise as well as defining future capabilities.
DoD EBTS version (v) 1.2 was based on the FBI Electronic Fingerprint Transmission Specification
(EFTS) v7.0 and ANSI/NIST-ITL 1-2000. After the release of DoD EBTS v1.2, a number of events
shaped the release of DoD EBTS Version 2.0:
•
•
•
•
•
•
•
As biometric support for various DoD mission activities evolved, so did the requirements for
a more flexible standard.
The scope of DoD biometric data collection and sharing expanded to a wider range of
operational scenarios. This broader set of scenarios necessitated the use of a mechanism to
tailor the DoD EBTS to individual applications. This mechanism is called an “application
profile.” It is used to describe customizations for individual operational scenarios that make
use of the DoD EBTS. The concept of an application profile is described in Section 2.1.
Data elements pertaining to biometric data collection and sharing have been defined in a
Glossary, a Data Dictionary, and a Data Model. All of the data elements used in the DoD
EBTS are defined in the Data Dictionary.
ANSI/NIST-ITL 1-2000 was updated to ANSI/NIST-ITL 1-2007 Part 1.
The DoD ABIS has evolved into the Next Generation ABIS (NG-ABIS), which provides
additional functionality such as searching of iris images and face images.
DoD EBTS needs to be usable for communications with DoD biometric repositories in
addition to DoD ABIS (or NG-ABIS).
FBI EFTS v7 was updated to FBI EBTS v8 to reflect ANSI/NIST ITL-1 2007 Part 1.
Page 1 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Following the release of EBTS v2.0, there were a number of Change Requests submitted and fixes to
Version 2.0 identified. Furthermore, DoD EBTS v3.0 allows for the transmission of new functionality.
DoD EBTS v3.0 addresses the needs of the Biometrics Enterprise and will be based on ANSI/NIST ITL
1-2011 and will be closely aligned to the FBI Electronic Biometric Transmission Specification (EBTS)
v9.3.
New functionality to EBTS v3.0 adopted from ANSI/NIST-ITL 1-2011 is as follows:
•
•
•
•
Type-18 in DoD EBTS v3.0 shall be used to exchange DNA and related data
Type-20 in DoD EBTS v3.0 shall contain the source representation(s) (a source
representation is used to generate one or more representations for use in other record types)
from which other Record Types were derived
Type-21 in DoD EBTS v3.0 shall contain an associated context, audio/visual recording or
other related data (i.e., pocket litter)
Type-98 in DoD EBTS v3.0 shall contain security information that allows for the assurance
of the authenticity and/or integrity of the transaction including such information as binary
data hashes, attributes for audit or identification purposes and digital signatures
Change Requests submitted from the Biometrics Enterprise that are incorporated in EBTS v3.0 can be
found in the Change Request Log.
The DoD EBTS v3.0 is described in this document.
1.2 Scope and Purpose
The DoD EBTS is a transmission specification to be used between DoD systems that capture biometric
data and repositories of biometric data. The DoD EBTS does not attempt to specify all data used in all
biometric enabled applications. It does allow for the definition of application specific data elements as
specified in Section 1.6 of this document.
This version of the DoD EBTS has been restructured to contain only the definitions of individual fields
and the structure of logical records. It does not attempt to define transactions; any definition of the
combination of logical records into transactions is defined in individual application profiles (described
in Section 3.0). Furthermore, this document provides only the traditional encoding description of DoD
EBTS v3.0. The DoD EBTS v3.0 Extensible Markup Language (XML) Information Exchange Packet
Documentation (IEPD) will align with the traditional encoding and will be provided separately.
The primary audience for this specification consists of software/system engineers who develop, support,
and/or test systems that interface with the DoD authoritative repository (i.e., DoD ABIS) or other DoD
biometric systems. This document contains the technical details of the DoD EBTS. Readers are
expected to have working knowledge of the ANSI/NIST-ITL 1-2011 as a prerequisite for understanding
this specification.
This document may also be used by program managers, trainers, or other system design personnel to
gain an understanding of the capabilities enabled by the DoD EBTS.
Page 2 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Users who wish to begin using services or implement biometric identification services should contact
the Biometrics Identity Management Agency (BIMA) for further assistance. Refer to Section 1.5 for
contact information.
1.3 References
EBTS v3.0 references multiple normative documents, which are listed in the “1.3 References" section of
this standard. Although, some references listed in this section are informational rather than normative.
[ITL 1-2011] ANSI/NIST-ITL 1-2011, “American National Standard for Information Systems – Data
Format for the Interchange of Fingerprint, Facial, & Other Biometric Information” (NIST Special
Publication 500-290).
[IDD] DoD Integrated Data Dictionary, v5.0.
[BAP] DoD Baseline Application Profile, v1.0.
[EIP] DoD EBTS Implementation Guide, Draft.
[SOP] DoD Application Profile Approval Standard Operating Procedure.
[SOP] DoD EBTS Change Request Standard Operating Procedure.
[FBI EBTS] Department of Justice, Federal Bureau of Investigation, Criminal Justice Information
Services (CJIS), “Electronic Biometric Transmission Specification” (IAFIS-DOC-01078-9.3).
[INCITS 385] ANSI INCITS 385-2004, “Face Recognition Format for Data Interchange.”
[ISO 19794-5] ISO/IEC 19794-5, “Information technology — Biometric data interchange formats —
Part 5: Face Image Data.”
[ISO/IEC 19794] ISO/IEC 19794-6:2011, “Information technology – Biometric data interchange
formats – Part 6: Iris image data.”
AR 190–8/OPNAVINST 3461.6/AFJI 31–304/MCO 3461.1, 1 October 1997, “Enemy Prisoners of War,
Retained Personnel, Civilian Internees and Other Detainees.”
[ISO 3166-1] ISO/IEC 3166-1, “Codes for the representation of names of countries and their
subdivisions – Part 1: Country Codes.”
Chief Information Officer/G-6 Memorandum, 29 November 2005, “Department of Defense Compliance
with the Electronic Biometric Transmission Specification.”
The Under Secretary of Defense for Acquisition, Technology and Logistics, 6 June 2011,
“Memorandum on DoD Country Code Standard.”
Page 3 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
1.4 Change Control
The BIMA Standards Branch maintains change control responsibilities for this document. Requested
changes to this document should be submitted to the DoD Biometrics Web site. Refer to Section 1.5 for
more information.
1.5 Contact Information
DoD Biometrics Web site: http://www.biometrics.mil.
For technical issues, contact the BIMA Watch Desk at (304) 326-3024, or by e-mail at
[email protected]. The BIMA Watch Desk operates 24 hours a day and 7 days a week. For
questions on the standard or for assistance with the Application Profile approval process, please contact
the BIMA Standards Branch by e-mail at [email protected].
Page 4 of 79
Electronic Biometric Transmission Specification Version 3.0
2.0
DIN: BIMA-STB-STD-11-001
CONFORMANCE AND UNIQUE REQUIRMENTS
2.1 Application Profile
An application profile is a document that describes how the DoD EBTS can be applied to a particular
operational scenario. An application profile must be specified to fully describe an implementation.
An application profile includes:
• Transaction details for each transaction:
o which fields are mandatory or optional for each logical record;
o how many occurrences of each field are required/allowed;
o which logical records are mandatory or optional; and
o how many occurrences of each logical record are required/allowed.
• Definition of the names and purposes of each transaction;
• The identifier assigned by the BIMA to name the Application Profile (to be placed in the
Application Profile Specifications field (1.016)); and
• Conformance requirements for both originators and receivers of transactions.
An Application Profile shall only use data elements defined in the Integrated Data Dictionary and those
data elements shall stay within the defined range. An Application Profile describes the transactions
(submissions and responses) that provide a data transfer equivalent to the Types of Transactions (TOTs)
identified in the Application Profile. An Application Profile provides an additional level of granularity
and sets restrictions or extensions on how EBTS is implemented.
An implementation may use the application profile associated with this Version (3.0) of the standard, or
may generate a new application profile. In the latter case, those DoD entities who wish to develop an
application profile must contact the BIMA Watch Desk and the BIMA Standards Branch (see Section
1.5). The Standard Operating Procedure for generating a new Application Profile should be followed
and BIMA will assist in the approval process. All application profiles will be maintained by the BIMA.
The BIMA will maintain a registration authority for managing the set of application profiles. This
includes the management of the identifiers used in the Domain Name field.
2.2 DoD EBTS Domain
The domain for a transaction is identified by the Domain Name field (1.013). The BIMA is the domain
registrar for the DoD EBTS implementation domain and assigns values for this field. ITL 1-2011
defines an implementation domain as “a group of organizations that have agreed to use specific preassigned data blocks for exchanging information unique to their installations.
The ANSI/NIST-ITL 1-2011 uses implementation domains to define common sets of Type-2 tags. The
DoD EBTS allows an application profile to define much more (including transactions). Users of the
DoD EBTS v3.0 domain shall populate the field as follows:
Field 1.013 Domain Name
• Subfield 1.013_1 Domain Name (DNM) – DoD EBTS.
• Subfield 1.013_2 Domain Version Number (DVN) – 3.0.
Page 5 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
2.3 Conformance and Testing
DoD EBTS implementations shall conform to the mandatory features of ANSI/NIST-ITL 1-2011.
DoD EBTS implementations shall conform to the mandatory features of this specification which are
defined by the Type of Transaction in the associated Application Profile.
Implementations shall also conform to one or more application profiles that have been registered with
the BIMA. DoD EBTS does not have a requirement for an implementation to conform to more than one
application profile, nor does it require that all implementations conform to the application profile
associated with EBTS Version 3.0. Each application profile will have its own conformance
requirements.
A DoD EBTS v3.0 transaction is conformant to ANSI/NIST-ITL 1-2011 standard if the Biometric
Electronic File Transaction (EFT) is capable of being morphologically (satisfies all of the normative
morphological requirements related to its data structure and data values), syntactically (satisfies all of
the normative requirements related to the relationships between fields, subfields, or information items)
and semantically (checks if the biometric transaction is a faithful representation of the parent biometric
data and ensures requirements are satisfied that are not merely syntactical or morphological) conformant
to the requirements of the standard.
The same rules shall also apply to the usage of FBI EBTS v9.3 data fields utilized in the Type-2 logical
record.
2.4 DoD ABIS Backward Compatibility
To achieve backward compatibility, it is the onus of the DoD Authoritative Biometric Repository (i.e.,
ABIS and future evolutions of the authoritative repository) to handle the capability to process DoD
EBTS v1.1, DoD EBTS v1.2, DoD EBTS v2.0, and DoD EBTS v3.0 transactions. Systems that collect
DoD EBTS data shall plan their acquisition phases accordingly and use the mandated DoD Information
Technology Standards and Profile Registry (DISR) EBTS version for data transmission. Legacy
collection systems that send DoD EBTS v1.2 and DoD EBTS v2.0 transactions shall receive responses
that conform to their respective versions.
2.5 Character Encoding
All of the fields in the Type-1 transaction record shall be recorded using the 7-bit ASCII code, which is
the default character encoding set code within a transaction. In order to affect data and transaction
interchanges between non-English speaking or foreign-based agencies, a technique is available to
encode information using character encoding sets other than 7-bit ASCII. Fields from the Type-1 logical
record and ASCII Field xx.001 and Field xx.002 text fields shall still be encoded using 7-bit ASCII, but
all other designated text fields may be encoded using an alternate character encoding set, if they are
shown with the character type of ‘U’ or ‘user-defined’ in the ITL 1-2011 record layout tables at the
beginning of each Record Type Section of the ITL 1-2011 standard. Unicode Consortium Standard
Page 6 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Transformation Format (UTF) – 8 should be used if necessary for expressing special characters or other
character sets in fields with the character type of ‘U’ or ‘user-defined.’
For further clarification on character encoding, please refer to ANSI/NIST-ITL 1-2011.
2.6 Structure of a Mnemonic
A record is comprised of fields. Within the standard, each field is assigned a number, a description, and
a mnemonic. The mnemonic structure shall follow __ which allows for the mnemonics to be unique within a
given data field and used for identification purposes. For example, Field 2.8003_2 Biometric Birth Date
with Information Item Date Validity is displayed as “T2_SUBJ_DOB_DATE_VLD.”
2.7 Encounter Protection
DoD EBTS v3.0 identifies Field 2.351 for Encounter Protection. However, Field 2.351 Encounter
Protection shall not be configurable by the user or the biometric capturing device (i.e., Encounter
Protection is for internal use only at this time). Submissions from organizations that must use Encounter
Protection should contact BIMA operations and coordinate the use of Encounter Protection with them. It
is the responsibility of ABIS to follow the Encounter Protection business rules based on the Originating
Agency Identifier.
Page 7 of 79
Electronic Biometric Transmission Specification Version 3.0
3.0
DIN: BIMA-STB-STD-11-001
DoD EBTS TRANSACTIONS
DoD EBTS does not define individual transactions. Transaction contents are defined in Application
Profiles. Please consult with the BIMA Standards Branch for information on developing and receiving
approval for Application Profiles. This section describes the rules and concepts that apply to any of
those transactions. This includes the use of logical records for each biometric modality, transaction
control numbers, origination identifiers, error handling, and image quality requirements.
3.1 Record Types
Table 1 identifies the types of biometric data supported by the DoD EBTS Version 3.0 and indicates
which logical record type is used to carry the data for each modality and other associated data (i.e.,
Type-21 Associated Context and Type-98 Information Assurance).
Table 1: Logical Recor ds
Biometric Data Type
Transaction Information
User Defined Descriptive
Text
Fingerprint Templates
Facial, Other Body Part,
and SMT Images
Friction Ridge Latent
Images
Fingerprint Images
Palmprint Images
Iris Images
DNA Data or Image
Source Representation
Associated Context
Information Assurance
CBEFF Biometric Data
Logical Record
Type-1
Type-2
Type-9
Type-10
Type-13
Type-14
Type-15
Type-17
Type-18
Type-20
Type-21
Type-98
Type-99
Information on the DoD EBTS support for each type of biometric data is contained in this section. The
details for using these logical records for constructing transactions are described in Section 2.0.
Note that it is possible to define a new logical record in an application profile if required.
3.1.1 Finger pr int Suppor t
Fingerprints shall be contained in Type-14 records. A Type-14 record shall contain a fingerprint image
of one of:
•
500-ppi image using 15:1 Wavelet Scalar Quantization (WSQ20) compression as defined in
ITL 1-2011 and FBI EBTS v9.3 or
Page 8 of 79
Electronic Biometric Transmission Specification Version 3.0
•
DIN: BIMA-STB-STD-11-001
1,000-ppi image using 15:1 JPEG 2000 Lossless (JP2L) compression as defined in ITL 12011 and FBI EBTS v9.3.
Latent fingerprints shall be contained in Type-13 records. A Type-13 record shall contain a latent
fingerprint image of one of:
•
•
•
500-ppi image using no compression
1,000-ppi image using no compression or
1,000-ppi image using 15:1 JPEG 2000 Lossless (JP2L) compression as defined in ITL 12011 and FBI EBTS v9.3.
3.1.2 Finger pr int Template Suppor t
Fingerprint data may also be conveyed as fingerprint minutiae templates. Fingerprint template data shall
be contained in Type-9 records. Type-9 records shall choose one of the following minutiae blocks as
defined in ITL 1-2011:
• “IAFIS Features” (FBI Native-Mode) minutiae block (fields 13-30) as described in the FBI
EBTS or
• “M1-378 Features” minutiae block (fields 126-150) as described in Table 28 of ITL 1-2011.
The decision on which format to use is driven by interoperability requirements with other systems. ITL
1-2011 also identifies reserved blocks in the Type-9 record, each consisting of several fields, which are
registered and allocated for use by specific vendors. As these blocks may contain proprietary
information and do not promote interoperability across the biometrics enterprise, no detailed information
is provided in DoD EBTS v3.0 regarding the content of these vendor-defined feature sets.
3.1.3 Facial Image Suppor t
Facial images and Scar, Mark & Tattoo (SMT) images shall be contained in Type-10 records. Images
may be compressed using the requirements for algorithms identified in ITL 1-2011. When Record Type10 contains a facial image, the conditions described in ITL 1-2011 Annex E: E.6.1 Compression
algorithm applies.
3.1.4 Palmpr int Suppor t
Palmprints shall be contained in Type-15 records. A Type-15 record shall contain a palmprint image of
one of:
•
•
500-ppi image using 15:1 Wavelet Scalar Quantization (WSQ20) compression as defined in
the ITL 1-2011 and FBI EBTS v9.3
1,000-ppi image using 15:1 JPEG 2000 Lossless (JP2L) compression as defined in ITL 12011 and FBI EBTS v9.3.
Latent palmprints shall be contained in Type-13 records. A Type-13 record shall contain a latent
palmprint image of one of:
•
•
500-ppi image using no compression
1,000-ppi image using no compression or
Page 9 of 79
Electronic Biometric Transmission Specification Version 3.0
•
DIN: BIMA-STB-STD-11-001
1,000-ppi image using 15:1 JPEG 2000 Lossless (JP2L) compression as defined in ITL 12011 and FBI EBTS v9.3.
3.1.5 Ir is Image Suppor t
Iris images shall be contained in Type-17 records. It is recommended that raw images with dimensions
of 640X480 are captured and used for submission. If images are to be compressed, they shall be
compressed using JPEG lossy (JP2) or JPEG Lossless (JP2L).
The baseline JPEG algorithm (ISO/IEC 10918) shall not be used for Type-17 iris images. It has been
shown that both false non-match and false match rates increase due to the presence of tiling artifacts
introduced by JPEG's discrete cosine transform. While JPEG was allowed in prior versions of this
standard, it shall not be allowed for new images.
3.1.6 DNA Suppor t
The Type-18 record shall contain and be used to exchange DNA and related data. It was developed to
provide a basic level of interoperability with ANSI/NIST-ITL 1-2011 which adopts the concepts of the
draft format of the ISO/IEC 19794-14 DNA data interchange format.
3.1.7 Sour ce Repr esentation Suppor t
The Type-20 record shall contain the source representation(s) from which other Record Types were
derived. Typically, one Type-20 source representation is used to generate one or more representations
for use in other record types. When a source representation (in a Type-20 record) is processed and the
derived representation is to be used as the source for further derivations, then the derived representation
is contained in a Type-20 record.
In some cases, several Type-20 records may be processed to derive a single Type-20 record.
Some possible uses of the Type-20 record are:
• From a group photo stored in a Type-20 record, a subject’s face is segmented and stored in a
Type-10 record.
• From a high-resolution color image in a Type-20 record, two latent fingerprint images are
segmented, rescaled and gray-scaled for storage in separate Type-13 records.
• From a series of off-angle face images stored in separate Type-20 records, a single 2D face
image is generated (using fusion) that is stored in a Type-10 record.
3.1.8 Associated Context Suppor t
The Type-21 record shall contain an associated context image, audio / visual recording or other related
data. This record type does NOT contain information used to derive biometric information contained in
other records. Record Type-20 serves that function. Record Type-21 may be used to convey contextual
information, such as an image of the area where latent fingerprints were captured or pocket litter.
3.1.9 Infor mation Assur ance Suppor t
The Type-98 record shall contain security information that allows for the assurance of the authenticity
and/or integrity of the transaction, including such information as binary data hashes, attributes for audit
or identification purposes, and digital signatures.
3.1.10 Other Biometr ic Modality Suppor t
A BIMA-approved application profile must define any use of Type-99 to contain other biometric
modalities.
Page 10 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
3.2 Transaction Control Numbers
An identification number is assigned to a submission and carried through on the response for tracing
purposes. This Transaction Control Number (TCN) is a unique identifier generated by the system that
submits the transaction. When a transaction is sent to a system that receives and generates responses,
the Transaction Control Reference (TCR) in the response(s) will be the TCN used in the submission. A
TCN is mandatory for a submission, and a TCR is mandatory for a response. These values are contained
in the Type-1 record in an FBI EBTS or DoD EBTS transaction.
Upon submitting a transaction to a DoD repository, the submitter places his control number in the TCN
field in the Type-1 record. For submissions not requiring reference to a prior transaction, the TCR field
is omitted. When the DoD repository has completed processing the transaction and generates the
response, it places the submitter’s control number (the received TCN) into the TCR field of the response
as a reference number the submitter can use to mate the response with the original submission. The
DoD repository also places its own internal identifier for that transaction in the TCN field of the
response.
Figure 1 illustrates, as an example, the TCN and TCR in the transaction flow in the DoD ABIS.
Figur e 1: Tr ansaction Submission and Response Sequence
Page 11 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
The DoD EBTS requires a 40-byte TCN that contains:
•
•
•
•
•
the Originating Agency Identifier (ORI);
a Greenwich Mean (a.k.a. Zulu or UTC) date/time stamp;
a code for the software used at the point of collection/transmission;
an indicator of the software version used at the point of collection/transmission; and
a random or sequential alphanumeric string.
A hyphen separates each of these values. Figure 2 illustrates the makeup of the TCN.
1 2 3 4 5 6 7 8 9
- 11 12 13 14 15 16 17 18 19 20 21 22 23 24 -
Origination Identifier
(ORI)
GMT Time Stamp
Format
YYYYMMDDhhmmss
26 27 28 29 - 31 32 33 34 - 36 37 38 39 40
Software
Name or
4 Letter Unique
Code
Software
Version
Random or Sequential
Alpha-numeric
code
Figur e 2: TCN Layout
The BIMA Watch Desk will assign a unique software code to a product. Software developers must
contact the BIMA Watch Desk (see Section 1.5) to obtain a four-letter software code (Figure 2, TCN
blocks 26 – 29). This code must be used consistently in the software product.
Systems that initiate transactions must assign TCNs rather than permit operators to enter them. A TCN
shall be unique. A TCN shall not be reused. Matching a TCN to a TCR is the method used to match
DoD EBTS responses to DoD EBTS submissions. It is recommended that the filename for the Electronic
File Transaction is the TCN.
3.3 Origination Identifiers
The mandatory origination field shall contain the ORI identifying the agency or organization submitting
the transaction. For DoD EBTS purposes, this field shall be a nine-byte alphanumeric field. The BIMA
will assign an ORI code to entities that submit directly to DoD ABIS. Those DoD entities must contact
the BIMA Watch Desk to obtain an ORI.
3.4 Tagged Fields
Systems that receive transactions (submissions or responses) shall observe the following processing
rules for tagged fields.
Page 12 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
3.4.1 Inter pr etation of Tags
In the construction and interpretation of the logical record, the tag number should not be taken as having
a fixed number of digits. The format for each field consists of the logical record type number followed
by a period (.), a field number followed by a colon (:), followed by the information appropriate to that
field. The tagged-field number can be any one- to nine-digit string occurring between the period and the
colon. It shall be interpreted as an unsigned integer field number. This implies that a field number of
2.123 is equivalent to and shall be interpreted in the same manner as a field number of 2.00000123. For
example, in this version of the standard, Type-2 logical record field tags are shown as having three or
four digits between the decimal point and colon (2.NNN:data or 2.NNNN:data). The field numbers
should be parsed as all digits between the period and colon. In the construction and interpretation of the
logical record, there is no requirement that the tagged fields be present within the logical record in any
given order, with the exception of the Length (LEN) and Image Designation Character (IDC), which
must be in the first and second position in the record, respectively. However, for those record types
conveying image data (e.g., 13.999: DATA), the data field will always be the last field in the string.
3.4.2 Use of Separ ator Char acter s
Separator characters may best be understood by considering them necessary for what follows them, not
what precedes them. Thus, when a tagged field includes subfields and another subfield is still to follow,
the following subfield must be separated from the one preceding it by the unit separator character. If
what is to follow is a repetition of a field or group of subfields, a record separator must separate the
preceding field or group of subfields from the repetition to follow. If what is to follow is a new field,
then the group separator character is used. If the record is complete after the previous field, the file
separator is used.
Per ITL 1-2011, successive separator characters may be used with no intervening blank or other
character when a subfield is missing. In Type-2 records, DoD EBTS recognizes the following
sequences as meaning that a subfield is missing: , , , and
. These are needed to obviate the need for the receivers of transactions to validate each
subfield in a grouped field to see whether it contains valid data or is merely a blank.
3.5 Error Handling
Systems that receive transactions (submissions or responses) shall observe the following processing
rules for error handling.
In the interpretation of a transaction, fields that are not defined for the requested transaction are to be
ignored; their inclusion is not to be considered an error.
Fields should not be transmitted when there is no value present (e.g., ... 2.033: ...). However,
receipt of such an empty field, if the field is not mandatory, should not result in rejection of the
submission or issuance of an error message. Rejection may occur, however, when missing or incorrect
data would frustrate processing of the transaction.
Systems that receive transactions (submissions or responses) shall ignore data that are not defined in the
DoD EBTS or appropriate application profile. Table 2 defines the actions that shall be taken when
unrecognized data are received.
Page 13 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 2: Response to Unr ecognized Reception
Error Condition
Unrecognized TOT
(as indicated by field 1.004 TOT)
Unrecognized Record
(the binary or tagged-field record is
not a Type-1, Type-2, Type-9, Type10, Type-13, Type-14, Type-15,
Type-17, Type-18, Type-20, Type21, Type-98 or Type-99)
Unrecognized Field
Unrecognized Subfield
Unrecognized Data in TaggedField Record
Action
Return an “Unauthorized EBTS Transaction” transaction
error response to the submitter.
Complete transaction and return appropriate response to
the submitter. Ignore the unrecognized record and
complete the transaction with appropriate response.
Complete transaction and return appropriate response to
the submitter. Ignore the unrecognized field and
complete the transaction with appropriate response.
Complete transaction and return appropriate response if
possible. Otherwise, return an “EBTS Field Parse Error”
transaction error response to the submitter.
Complete transaction and return appropriate response if
possible. Otherwise, return an “EBTS Field Parse Error”
transaction error response to the submitter.
3.6 Image Quality and Image Sets Requirements
In the interest of maintaining an accurate and usable database of biometric data, minimum image quality
requirements must be followed for images submitted in DoD EBTS transactions.
3.6.1 Finger pr int Image Quality and Image Sets (Type-14)
Fingerprint image quality requirements are defined in Appendix F of the FBI EBTS v9.3. From an
image quality perspective only, any system certified by the FBI for use with Next Generation
Identification (NGI) meets DoD EBTS image quality requirements.
Rolled fingerprint samples shall be captured with each finger rolled from one side of the fingernail to the
other. The collection of a “complete set” of fingerprint samples shall include any of the following image
submissions:
14 Images:
•
•
•
•
•
Rolled or Flat image of each of the 10 fingers
One Four Finger Slap image of the right hand (no thumb)
One Four Finger Slap image of the left hand (no thumb)
One Flat image of the right thumb
One Flat image of the left thumb
13 Images:
•
Rolled or Flat image of each of the 10 fingers
Page 14 of 79
Electronic Biometric Transmission Specification Version 3.0
•
•
•
DIN: BIMA-STB-STD-11-001
One Four Finger Slap image of the right hand (no thumb)
One Four Finger Slap image of the left hand (no thumb)
One Two Thumb Slap Fingerprint image
10 Images:
•
Rolled or Flat image of each of the 10 fingers
An explanation for any required but missing fingerprints shall be provided in field 14.018 Amputated or
Bandaged from a plain two thumb slap or four finger slap image. Field 14.018 shall accurately represent
the reason for each missing fingerprint. This field has two subfields: Finger Position Code (FGP) and
Amputated or Bandaged Code (AMPCD). Both subfields are required if field 14.018 is present.
Subfield FGP is a two-digit code that specifies which finger is missing. Subfield AMPCD uses the
value “XX” when there is an actual amputation and the value “UP” (unable to print) for all other
situations.
DoD EBTS v3.0 recommends the use of ITL 1-2011 Field 14.018 in order to adhere to business rules
developed for this standard. However, Field 2.084 Amputated or Bandaged and its two information
items should be used to include the reason for a missing finger if a Type-14 record is not submitted or to
indicate why a slap image and/or plain thumb image is missing.
In addition, DoD EBTS v3.0 does not recommend the practice of stitching fingerprint images (e.g., the
right and left thumb images were captured separately, but combined prior to transmission to create a
single artificial two-thumb image). For devices which are not able to submit the four finger slap image
and/or two thumb slap image due to limitations on the capturing device, the AMP field shall instead be
populated to indicate the Finger Position Code and Amputated or Bandaged Code.
3.6.2 Palmpr int Image Quality and Image Sets (Type-15)
Palmprint image quality requirements shall follow the same image requirements and compression
standards as identified for fingerprint image quality. All palmprint images shall be acquired directly
from a subject using a live-scan device or approved palmprint card. Whichever method is used should be
capable of providing a set of images for each hand.
A complete palmprint set contains the following images for both hands:
•
One writer’s palm image from each hand and
•
•
•
Either one full palm image (the entire area of the full palm extending from the wrist
bracelet to the tips of the fingers) from each hand or
One upper palm image from each hand (extends from the bottom of the interdigital area
to the upper tips of the fingers) and one lower palm image (shall extend from the wrist
bracelet to the top of the interdigital area (third finger joint) from each hand or
One palm thenar area image, one palm hypothenar area image, and one palm interdigital
area image from each hand.
Page 15 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
An explanation for any missing palmprint images is optional. Field 15.018 and its associated subfields
shall be used to indicate any missing images. The Type-2 Field 2.8112 has been added to EBTS v3.0
and may be used to indicate if a Type-15 record is not able to be submitted.
3.6.3 Facial Photo Image Quality and Image Sets (Type-10)
All photographs shall be taken using a color camera. The camera lens orientation (photographer) shall
be pointed to the front of the person, aligned approximately in the center of the face, and taken from a
distance of approximately five feet. The orientation(s) of the person for facial photos shall be taken
from the following options:
•
•
•
•
•
Frontal view (also known as full-frontal pose);
90 degrees left side;
45 degrees left side;
90 degrees right side; or
45 degrees right side.
When photographed, the person shall not be allowed to wear any glasses, sunglasses, or other items
obscuring the area photographed. The person may choose to expose only the area from ear to ear and
hairline to chin (for example, to not require the removal of a headdress). There are no constraints on
cosmetics.
The full frontal pose should be captured in accordance with one of the following:
• ANSI INCITS 385-2004, “Face Recognition Format for Data Interchange”, clauses 8.2, 8.3,
and 8.4 (The Full Frontal Image Type). NOTE: this document may be retired in favor of the
ISO document below; or
• Annex A, Best Practices for Basic Face Images, of ISO/IEC 19794-5, Information
technology — Biometric data interchange formats — Part 5: Face Image Data.
3.6.4 Ir is Image Quality and Image Sets (Type-17)
An iris record shall contain an image of a single iris. Note: this does not imply that image capture
equipment must be used twice to collect two images. If a single image of both the left and right eye is
captured, further processing must result in two separate records.
Images should be captured in accordance with Annex A, Iris Image Capture, of ISO/IEC 19794-6,
Information technology — Biometric data interchange formats — Part 6: Iris image data.
Page 16 of 79
Electronic Biometric Transmission Specification Version 3.0
4.0
DIN: BIMA-STB-STD-11-001
DoD EBTS RECORDS AND FIELDS
The DoD EBTS is 100% ITL 1-2011 conformant. Any DoD EBTS ITL 1-2011 defined field may occur
in a DoD EBTS transaction in the appropriate logical record. Any field that is mandatory in ITL 1-2011
shall occur in a DoD EBTS transaction in the appropriate logical record.
This section contains any additional information not included in ITL 1-2011.
The following discussion uses the ITL 1-2011 standard definition of information separators:
• multiple occurrences of field are separated by the “RS” character (represented in this
document by ); and
• information items within a field are separated by the “US” character (represented in this
document by ).
If the following sections do not identify any subfields, none are allowed.
4.1 Type-1 Records [Transaction Information]
DoD EBTS Type-1 records are defined in ITL 1-2011. Every application profile shall define values in
the Application Profile Specifications field (1.016). The BIMA Baseline Application Profile shall be the
default value in field 1.016 if no other value is provided. The Baseline Application Profile specifies the
common transactions occurring between DoD collection devices that have direct or indirect transaction
ties to the DoD authoritative biometric repository. The Baseline Application Profile enables the user to
conform to DoD EBTS v3.0. For implementations using the Baseline Application Profile v1.0, the
values are as follows:
Field 1.016 Application Profile Specification
• Subfield 1.016_1 Application Profile Organization (APO) – BIMA.
• Subfield 1.016_2 Application Profile Name (APN) – Base Application Profile.
• Subfield 1.016_3 Application Profile Version Number (APV) – 1.0. (The version number
will be updated as necessary)
DoD EBTS v3.0 transactions do not contain Type-3 through Type-7 records, therefore the fields Native
Scanning Resolution (1.011) and Nominal Transmitting Resolution (1.012) shall be set to “00.00” as
specified in ITL 1-2011.
Page 17 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 3: Type-1 Tr ansaction Infor mation Recor d Layout
Field
Number
1.001
1.002
1.003
1.003_1
1.003_2
1.003_3
1.003_4
1.004
1.005
1.006
1.007
1.008
1.009
1.010
1.011
1.012
1.013
1.013_1
1.013_2
1.014
1.015
1.015_1
1.015_2
Field Name
RECORD HEADER
VERSION NUMBER
TRANSACTION CONTENT
- First Record Category Code 1
- Content Record Count
- Record Category Code 2
- Information Designation Character
TYPE OF TRANSACTION
DATE
PRIORITY
DESTINATION AGENCY IDENTIFIER
ORIGINATING AGENCY IDENTIFIER
TRANSACTION CONTROL NUMBER
TRANSACTION CONTROL REFERENCE NUMBER
NATIVE SCANNING RESOLUTION
NOMINAL RESOLUTION
DOMAIN NAME
- Domain Name
- Domain Version Number
GREENWICH MEAN TIME
CHARACTER ENCODING
- Character Encoding Set Index
- Character Encoding Set Name
Min
Occ.
1
1
1
1
1
1
1
1
1
0
1
1
1
0
1
1
1
1
1
0
0
1
1
Max
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Mnemonic
LEN (Used only in traditional encoding version)
VER
CNT
- FRC
- CRC
- REC
- IDC
TOT
DAT
PRY
DAI
ORI
TCN
TCR
NSR
NTR
DOM
- DNM
- DVN
GMT
DCS
- CSI
- CSN
1
The First Record Category Code and Content Record code are a single set of information items
2
The Record Category Code and Information Designation Character subfields are repeating sets of information items based on the Content Record Count
Page 18 of 79
Electronic Biometric Transmission Specification Version 3.0
Field
Number
1.015_3
1.016
1.016_1
1.016_2
1.016_3
1.017
1.017_1
1.017_2
Field Name
- Character Encoding Set Version
APPLICATION PROFILE SPECIFICATIONS
- Application Profile Organization
- Application Profile Name
- Application Profile Version Number
AGENCY NAMES
- Destination Agency Name
- Originating Agency Name
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
1
1
1
1
0
0
0
Max
Occ.
1
99
1
1
1
1
1
1
Page 19 of 79
Mnemonic
- CSV
APS
- APO
- APN
- APV
ANM
- DAN
- OAN
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.2 Type-2 Records [User-Defined Descriptive Text]
The Integrated Data Dictionary (IDD) v5.0 defines the following Type-2 fields to meet DoD
requirements. The DoD Expanded Application Profile document provides information such as whether
the field is mandatory for the associated Type of Transaction (TOT) and the minimum and maximum
occurrences. Each DoD EBTS field is associated with IDD elements as shown in the following tables.
Certain data elements in the EBTS v2.0 Type-2 record are now considered legacy FBI fields to the DoD
and those fields are derivable by specific DoD EBTS v3.0 Type-2 or ANSI/NIST ITL 1-2011 data
fields. The legacy FBI fields remain in the Base Application Profile and IDD v5.0 because they have
been identified as being mandatory to specific FBI TOTs.
Data Element States Definitions as defined by IDD v5.0
State
Active
Deprecated
Sunset
Retired
Legacy Derivable
Emerging
Definition
Currently viable and fully usable dictionary
element.
Element is still usable in current implementations,
but it should not be used going forward. It will
gradually be phased out with a new element(s)
doing the same thing. The IDD will clearly mark if
an element is deprecated. The IDD will also
provide the superseding element(s) and any qualify
condition. This helps identify the transition path
from As‐Is to To‐Be.
Used for alerting the user community that an
element may be retired in the future. An element
nominated for sunset may not be retired if the
community feels it is needed. IDD will provide
indicator to clear mark if an element is in the
sunset state and the reason why.
Appearing for the last time in the version of the
IDD as they are being retired. The IDD will clearly
mark if an element is retired. Retired element can
be reinstated with necessary requirement. At that
point, the element will be treated as a new element.
Pertains to FBI elements only. The element should
only be used in FBI TOTs. It can be derived from
DoD element(s). The IDD clearly marks if an FBI
element is derivable. The IDD will also provide
the DoD elements and any qualify condition from
which this element can be derived
A DoD Type‐2 element that can be considered for
future capability. It can be subject to change.
Page 20 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
FBI legacy fields from EBTS v2.0
•
•
•
•
•
•
•
•
•
•
Field 2.018 Name
Field 2.020 Place of Birth
Field 2.022 Date of Birth
Field 2.025 Race
Field 2.027 Height
Field 2.029 Weight
Field 2.031 Eye Color
Field 2.037 Reason Fingerprinted
Field 2.038 Date Printed
Field 2.067 Image Capture Equipment
In addition, certain data elements associated with EBTS v2.0 have been deprecated, sunset, or are now
considered as emerging due to lack of implementation and/or requirements. While these fields are not
implemented in EBTS v3.0, they will reside in the Integrated Data Dictionary v5.0. These Fields are
referenced below for convenience.
Fields with sunset status from EBTS v2.0
•
•
•
•
•
Field 2.352 Transaction Lookup
Field 2.353 Subsequent Notification
Field 2.8015 Biometric Subject Other Physical Characteristics
Field 2.8202 Verification Identifier (Was Field 2.315 in DoD EBTS v1.2)
Field 2.8204 Limit of Candidates
Fields with deprecated status from EBTS v2.0
•
•
•
•
•
•
•
Field 2.306 Geographic Coordinate Latitude/Longitude
Field 2.307 Geographic Coordinate Datum
Field 2.321 Geographic Coordinate Other
Field 2.322 Geographic Coordinate Universal Transverse Mercator
Field 2.8020 Collection Application Assigned Identification
Field 2.8101 Contextual Data Collection Date
Field 2.8200 Submission Priority
Fields with emerging status from EBTS v2.0
•
•
•
•
•
Field 2.8206 Additional Response (Mistakenly identified as Field 2.351 in DoD EBTS v2.0)
Field 2.8207 Request Secondary Search (Was Field 2.317 in DoD EBTS v2.0)
Field 2.8106 Triggering Event
Field 2.8109 Repository Candidate List
Field 2.8203 Template Extraction Algorithm
All other emerging fields are listed in the Integrated Data Dictionary v5.0.
Page 21 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Fields deprecated and restructured from EBTS v2.0
To achieve better harmonization with other agencies as well as to improve alignment with the NIEM
XML, the following fields have been renamed and/or restructured:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Field 2.8000 Biometric Subject Name (Biometric Subject Name is now Field 2.8040)
Field 2.8001 Biometric Subject Address (Biometric Subject Address is now Field 2.8031
Biometric Current Residence)
Field 2.8002 Biometric Subject Contact (Biometric Subject Contact is now Field 2.8032
Biometric Subject Contact Telephone)
Field 2.8004 Biometric Subject Birth Place (Biometric Subject Birth Place is now Field 2.8033
Biometric Subject Birth Location)
Field 2.8006 Biometric Subject Death Place (Biometric Subject Death Place is now Field 2.8034
Biometric Subject Death Location)
Field 2.8009 Biometric Subject Measurement – Height (Biometric Subject Measurement –
Height is now Field 2.8035 Biometric Subject Height Measurement)
Field 2.8010 Biometric Subject Measurement – Weight (Biometric Subject Measurement –
Weight is now Field 2.8036 Biometric Subject Weight Measurement)
Field 2.8011 Biometric Subject Eye Color Left (Biometric Subject Eye Color Left is now Field
2.8037 Biometric Subject Eye Color)
Field 2.8012 Biometric Subject Eye Color Right (Biometric Subject Eye Color Right is now
Field 2.8037 Biometric Subject Eye Color)
Field 2.8017 Biometric Subject Associated Individual (Biometric Subject Associated Individual
is now Field 2.8038)
Field 2.8018 Biometric Subject Group Membership (Biometric Subject Group Membership is
now Field 2.8039)
Field 2.8100 Collection Location ( Collection Location is now Field 2.8114; Field 2.301
Location from DoD EBTS v1.2 is also deprecated)
Field 2.8104 Operational Personnel (Operational Personnel is now Field 2.8115)
Field 2.8105 Conveyance (Conveyance is now Field 2.8116 Transportation)
ANSI/NIST-ITL 1-2011 has incorporated many data fields that were previously defined in the Type-2
record within earlier versions of both the DoD EBTS and FBI EBTS specifications. These fields include
2.038 Date Printed (DPR), 2.067 Image Capture Equipment (MMS), 2.306 Geographic Coordinate
Latitude/Longitude, 2.307 Geographic Coordinate Datum, 2.321 Geographic Coordinate Other and
2.322 Geographic Coordinate Universal Transverse Mercator.
DoD EBTS v3.0 still needed a comprehensive way of identifying both the pieces of equipment as well
as where and when the data was collected for each modality in the Type-2 Record. In order to
accomplish this, DoD EBTS v3.0 created two new fields, 2.8114 Collection Location (previously 2.301
in DoD EBTS v1.2 and 2.8100 in DoD EBTS v2.0) and 2.8118 Collection Equipment
Make/Model/Serial Number.
Field 2.8114 Collection Location shall be used to capture the geographic location and time for just the
Type-2 data and/or for the entire submission. To maintain consistency with ANSI/NIST ITL 1-2011, the
Page 22 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Collection Location field has been restructured to include all the information items from the ITL 1-2011
x.998 GEO field. In addition, City, State/Province, Country Code and Village were added. An
information item for Record Category Code Referenced has also been added to allow designation which
logical record the information pertains to, either the entire submission or just the Type-2 data only.
Field 2.8118 Collection Equipment Make/Model/Serial Number shall be used to capture the
make/model/serial number of the equipment the sample was collected for just the Type-2 data and/or for
the entire submission. An information item for Record Category Code Referenced has also been added
to allow designation which logical record the information pertains to, either the entire submission or just
the Type-2 data only.
Page 23 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 4: Type-2 User -Defined Descr iptive Text Recor d Layout
Field
Number
2.001
2.002
2.005
2.006
2.007
2.009
2.010
2.010_1
2.010_2
2.011
2.014
2.015
2.024
2.026
2.032
2.034
2.034_1
2.034_2
2.035
2.036
2.040
2.043
2.045
2.047
2.047_1
2.047_2
2.048
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
RETENTION CODE
ATTENTION INDICATOR
SEND COPY TO
ORIGINATING AGENCY CASE NUMBER
CONTRIBUTOR CASE IDENTIFIER NUMBER
- Contributor Case Identifier Prefix
- Contributor Case Identifier
CONTRIBUTOR CASE IDENTIFIER EXTENSION
FBI NUMBER
STATE IDENTIFICATION NUMBER
SEX
SCARS, MARKS AND TATTOOS
HAIR COLOR
PATTERN LEVEL CLASSIFICATIONS
- Finger Number
- Pattern Classification Code
PALM PRINTS AVAILABLE INDICATOR
PHOTO AVAILABLE INDICATOR
OCCUPATION
TYPE OF SEARCH REQUESTED
DATE OF ARREST
ARREST SEGMENT LITERAL
- Date of Offense
- Arrest Offense Literal
CIVIL SEARCH REQUESTED INDICATOR
Min
Occ.
1
1
0
0
0
0
0
1
1
0
0
0
0
0
0
0
1
1
0
0
0
0
0
0
0
1
0
Max
Occ.
1
1
1
1
9
1
5
1
1
5
5
1
1
10
1
10
1
1
1
1
1
1
1
40
1
1
1
Page 24 of 79
Mnemonic
LEN (Used only in traditional encoding version)
IDC
RET
ATN
SCO
OCA
CIN
- CIN_PRE
- CIN_ID
CIX
FBI
SID
SEX
SMT
HAI
PAT
- FGP
- PATCL
- PPA
PHT
OCP
TSR
DOA
ASL
- DOO
- AOL
CSR
Electronic Biometric Transmission Specification Version 3.0
Field
Number
2.051
2.051_1
2.051_2
2.051_3
2.054
2.055
2.056
2.057
2.059
2.060
2.061
2.064
2.064_1
2.064_2
2.070
2.071
2.073
2.074
2.075
2.076
2.079
2.083
2.084
2.084_1
2.084_2
2.085
2.086
2.087
2.088
2.089
DIN: BIMA-STB-STD-11-001
Field Name
COURT SEGMENT LITERAL
- Court Disposition Date
- Court Offense Literal
- Other Court Sentence Provision Literal
CUSTODY OR SUPERVISORY STATUS START DATE
CUSTODY OR SUPERVISORY STATUS LITERAL
IDENTIFICATION COMMENTS
FINGER NUMBER(S) REQUESTED
SEARCH RESULTS FINDINGS
STATUS/ERROR MESSAGE
CASE TITLE
CANDIDATE LIST
- FBI Number
- Name
REQUEST FOR ELECTRONIC RAP SHEET
ACTION TO BE TAKEN
CONTROLLING AGENCY IDENTIFIER
FINGER POSITION
ELECTRONIC RAP SHEET
PRIORITY
NUMBER OF CANDIDATE IMAGES RETURNED
UNSOLVED LATENT FILE
AMPUTATED OR BANDAGED
- Finger Position
- Amputated or Bandaged Code
CIVIL RECORD NUMBER
AFIS SEGMENT CONTROL NUMBER
TREAT AS ADULT
NOTE FIELD
MATCH SCORE
Min
Occ.
0
0
1
0
0
0
0
0
0
0
0
0
1
1
0
0
0
0
0
0
0
0
0
1
1
0
0
0
0
0
Max
Occ.
40
1
1
1
1
1
1
13
1
11
1
99
1
1
1
1
3
10
1
1
1
1
13
1
1
1
1
1
1
99
Page 25 of 79
Mnemonic
CSL
- CDD
- COL
- CPL
SSD
SLE
ICO
FNR
SRF
MSG
CST
CAN
- FBI
- NAM
RAP
ACN
CRI
FGP
ERS
PRI
NCR
ULF
AMP
FGP
AMPCD
CRN
SCNA
TAA
NOT
MSC
Electronic Biometric Transmission Specification Version 3.0
Field
Number
2.091
DIN: BIMA-STB-STD-11-001
Field Name
Min
Occ.
0
Max
Occ.
10
Mnemonic
1
1
0
1
1
10
FGP
RCN1
RCD2
1
1
0
0
0
0
0
0
1
1
1
10
1
1
5
1
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
10
1
1
FGP
RCN2
RFR
NDR
GUID
ISN
DOD_NO
EDI (Mnemonic was incorrectly shown as EDIPI in DoD
EBTS v2.0)
DBIDS_ID
PER_TYPE
RMS
RIS
XML
SCC
DOSSIER
ALERT
- ALERT_FUN (Mnemonic was incorrectly shown as
ALERT_FN in DoD EBTS v2.0)
- ALERT_CAT
- ALERT_VAL
- ALERT_CONTACT (Mnemonic was incorrectly shown
as ALERT_CNTCT in DoD EBTS v2.0)
- ALERT_DETAIL
EP
2.309
2.310
2.316
2.317
2.318
2.334
2.335
2.350
2.350_1
RIDGE CORE DELTA ONE FOR SUBPATTERN
CLASSIFICATION
- Finger Number
- Ridge Count Number 1
RIDGE CORE DELTA ONE FOR SUBPATTERN
CLASSIFICATION
- Finger Number
- Ridge Count Number 2
REQUEST FEATURES RECORD
NAME OF DESIGNATED REPOSITORY
BAT GLOBAL UNIQUE IDENTIFIER
INTERNMENT SERIAL NUMBER
DoD NUMBER
ELECTRONIC DATA INTERCHANGE PERSONAL
IDENTIFIER
DEFENSE BIOMETRIC IDENTIFICATION SYSTEM ID
BIOMETRIC SUBJECT PERSONNEL TYPE
REQUEST MUG SHOT
REQUEST IAFIS SEARCH
XML-BASED RAP SHEET
SUBMISSION COLOR CODE
DOSSIER NUMBER
ALERT
- Alert Function
2.350_2
2.350_3
2.350_4
- Alert Category
- Alert Value
- Alert Contact
1
1
1
1
1
1
2.350_5
2.351
- Alert Detail
ENCOUNTER PROTECTION
1
0
1
1
2.091_1
2.091_2
2.092
2.092_1
2.092_2
2.095
2.098
2.300
2.302
2.303
2.308
Page 26 of 79
RCD1
Electronic Biometric Transmission Specification Version 3.0
Field
Number
2.351_1
2.351_2
Field Name
2.8003
2.8003_1
2.8003_2
2.8003_3
2.8005
2.8005_1
2.8005_2
2.8005_3
2.8007
2.8008
BIOMETRIC SUBJECT BIRTH DATE
- Birth Date
- Date Validity
- Calendar Type
BIOMETRIC SUBJECT DEATH DATE
- Death Date
- Date Validity
- Calendar Type
BIOMETRIC SUBJECT CITIZENSHIP
BIOMETRIC SUBJECT ETHNIC/RACIAL
CHARACTERISTIC
BIOMETRIC SUBJECT BLOOD TYPE
- Blood Type Code
- Blood Type Validity
BIOMETRIC SUBJECT VITAL STATUS
- Vital Status Code
- Vital Status Validity
BIOMETRIC SUBJECT MARITAL STATUS
COLLECTED IDENTIFICATION
- Collected Identification Type
- Collected Identification Identifier
- Collected Identification Issuance Organization
- Collected Identification Issuance Date
- Collected Identification Expiration Date
- Collected Identification Issuance Office
- Comment
BIOMETRIC SUBJECT CLEARANCE
- Clearance Code
2.8013
2.8013_1
2.8013_2
2.8014
2.8014_1
2.8014_2
2.8016
2.8019
2.8019_1
2.8019_2
2.8019_3
2.8019_4
2.8019_5
2.8019_6
2.8019_7
2.8021
2.8021_1
- Encounter Protection Function
- Encounter Protection Level
DIN: BIMA-STB-STD-11-001
Min
Occ.
1
1
Max
Occ.
1
1
0
1
0
0
0
1
0
0
0
0
5
1
1
1
1
1
1
1
5
5
0
3
1
1
0
1
0
3
1
1
0
1
0
1
0
100
1
1
1
1
0
1
0
1
0
1
0
1
0
1
0
1
1
1
Page 27 of 79
Mnemonic
- EP_FUN
- EP_LEVEL (Mnemonic was incorrectly shown as
EP_LVL in DoD EBTS v2.0)
SUBJ_BIRTHDATE
- DOB
- DATEVLD
- CALTYP
SUBJ_DEATHDATE
- DOD
- DATEVLD
- CALTYP
SUBJ_CTZ
SUBJ_RAC
SUBJ_BLOOD
- BLTCD
- BLTVLD
SUBJ_VITAL
- VSCD
- VSVLD
SUBJ_MARITAL
COL_IDENT
- CITYP
- CIID
- CIISSORG
- CIISSDT
- CIEXPDT
- CIISSOFF
- CICOM
SUBJ_CLEAR
- CLRCD
Electronic Biometric Transmission Specification Version 3.0
Field
Number
2.8021_2
2.8022
2.8022_1
2.8022_2
2.8023
2.8024
2.8025
2.8026
2.8026_1
2.8026_2
2.8026_3
2.8026_4
2.8026_5
2.8026_6
2.8026_7
2.8026_8
2.8026_9
2.8028
2.8028_1
2.8028_2
2.8028_3
2.8028_4
2.8028_5
2.8028_6
2.8028_7
2.8028_8
2.8028_9
2.8028_10
2.8028_11
2.8028_12
2.8028_13
DIN: BIMA-STB-STD-11-001
Field Name
- Clearance Validity
BIOMETRIC SUBJECT COMPARTMENTS
- Compartment Description
- Compartment Validity
BIOMETRIC SUBJECT COMMENT
BIOMETRIC SUBJECT US PERSON INDICATOR
BIOMETRIC SUBJECT DEROGATORY COMMENT
BIOMETRIC SUBJECT ALTERNATE NAME
- Alternate Name Category Code
- Name – One
- Name – Two
- Name – Three
- Name – Four
- Name – Five
- Name Validity
- Transliteration Code
- Comment
EMPLOYMENT
- Employer Name
- Employee Position Name
- Address Line 1
- Address Line 2
- City
- State/Province
- Country Code
- Postal Code
- Village
- Phone Number
- Email
- Clearance Code
- Job Duties
Min
Max
Occ.
Occ.
0
1
0
50
1
1
0
1
0
1
0
1
0
1
0
10
1
1
1
1
1
1
0
1
0
1
0
1
0
1
0
1
0
1
0
5
1
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
Page 28 of 79
Mnemonic
- CLRVLD
SUBJ_COMPART
- CMPDESC
- CMPVLD
SUBJ_COM
US_IND
DEROG_COM
SUBJ_AKA
- NAMCATCD
- NAM1
- NAM2
- NAM3
- NAM4
- NAM5
- NAM_VLD
- TRANSLIT_CD
- COM
EMPLOY
- EMPNAM
- POSNAM
- ADD1
- ADD2
- CITY
- STATE
- CTRY
- POSTAL
- VLG
- PHNUM
- EMAIL
- CLRCD
- DUTY
Electronic Biometric Transmission Specification Version 3.0
Field
Number
2.8028_14
2.8028_15
2.8028_16
2.8028_17
2.8028_18
2.8029
2.8031
2.8031_1
2.8031_2
2.8031_3
2.8031_4
2.8031_5
2.8031_6
2.8031_7
2.8031_8
2.8031_9
2.8032
2.8032_1
2.8032_2
2.8032_3
2.8033
2.8033_1
2.8033_2
2.8033_3
2.8033_4
2.8033_5
2.8034
2.8034_1
2.8034_2
2.8034_3
2.8034_4
Field Name
- Job Description
- Supervisor Name
- Start Date
- End Date
- Comment
BIOMETRIC SUBJECT CONTACT EMAIL
BIOMETRIC SUBJECT CURRENT RESIDENCE
- Address Line 1
- Address Line 2
- City
- State/Province
- Country Code
- Postal Code
- Neighborhood/District
- Village
- Address Validity
BIOMETRIC SUBJECT CONTACT TELEPHONE
- Telephone Category Code
- Phone Number
- Phone Extension
BIOMETRIC SUBJECT BIRTH LOCATION
- City
- State/Province
- Country Code
- Village
- Comment
BIOMETRIC SUBJECT DEATH LOCATION
- City
- State/Province
- Country Code
- Village
DIN: BIMA-STB-STD-11-001
Min
Max
Occ.
Occ.
0
1
0
1
0
1
0
1
0
1
0
10
0
1
0
1
0
1
0
1
1
1
1
1
0
1
0
1
0
1
0
1
0
10
1
1
1
1
0
1
0
1
0
1
0
1
1
1
0
1
0
1
0
1
0
1
0
1
1
1
0
1
Page 29 of 79
Mnemonic
- JOBDESC
- SUPV
- STARTDATE
- ENDDATE
- COM
SUBJ_EMAIL
SUBJ_ADDR
- ADD1
- ADD2
- CITY
- STATE
- CTRY
- POSTAL
- NEIG
- VLG
- ADDR_VLD
SUBJ_PHONE
- PH_TYP
- PHNUM
- PHEXT
SUBJ_POB
- CITY
- STATE
- CTRY
- VLG
- COM
SUBJ_POD
- CITY
- STATE
- CTRY
- VLG
Electronic Biometric Transmission Specification Version 3.0
Field
Number
2.8034_5
2.8035
2.8035_1
2.8035_2
2.8035_3
2.8036
2.8036_1
2.8036_2
2.8036_3
2.8037
2.8037_1
2.8037_2
2.8038
2.8038_1
2.8038_2
2.8038_3
2.8038_4
2.8038_5
2.8038_6
2.8038_7
2.8038_8
2.8038_9
2.8038_10
2.8038_11
2.8038_12
2.8038_13
2.8038_14
2.8038_15
2.8038_16
2.8038_17
2.8038_18
Field Name
- Comment
BIOMETRIC SUBJECT HEIGHT MEASUREMENT
- Height Value
- Length Unit
- Height Validity
BIOMETRIC SUBJECT WEIGHT MEASUREMENT
- Weight Value
- Mass Unit
- Weight Validity
BIOMETRIC SUBJECT EYE COLOR
- Eye Position
- Eye Color
BIOMETRIC SUBJECT ASSOCIATED INDIVIDUAL
- Associated Individual Gender
- Associated Individual Role
- Name – One
- Name – Two
- Name – Three
- Name – Four
- Name – Five
- Address Line 1
- Address Line 2
- City
- State/Province
- Country Code
- Postal Code
- Village
- Phone
- Birth Date
- Occupation
- Comment
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
0
1
1
1
0
1
1
1
0
1
1
0
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Max
Occ.
1
2
1
1
1
2
1
1
1
2
1
1
100
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Page 30 of 79
Mnemonic
- COM
SUBJ_HEIGHT
- HGT
- LENUNIT
- MEASVLD
SUBG_WEIGHT
- WGT
- MASSUNIT
- MEASVLD
SUBJ_EYE
- EPOS
- ECOL
IASSOC
- IASSOC_SEX
- IASSOC_ROLE
- NAM1
- NAM2
- NAM3
- NAM4
- NAM5
- ADD1
- ADD2
- CITY
- STATE
- CTRY
- POSTAL
- VLG
- PHNUM
- DOB
- OCC
- COM
Electronic Biometric Transmission Specification Version 3.0
Field
Number
2.8039
2.8039_1
2.8039_2
2.8039_3
2.8039_4
2.8039_5
2.8039_6
2.8039_7
2.8039_8
2.8039_9
2.8039_10
2.8039_11
2.8039_12
2.8040
2.8040_1
2.8040_2
2.8040_3
2.8040_4
2.8040_5
2.8040_6
2.8040_7
2.8102
2.8103
2.8107
2.8108
2.8110
2.8111
2.8112
2.8114
2.8114_1
2.8114_2
Field Name
BIOMETRIC SUBJECT GROUP MEMBERSHIP
- Group Name
- Group Type
- Group Member Role
- Address Line 1
- Address Line 2
- City
- State/Province
- Country Code
- Postal Code
- Village
- Phone Number
- Comment
BIOMETRIC SUBJECT NAME
- Name – One
- Name – Two
- Name – Three
- Name – Four
- Name – Five
- Name Validity Code
- Transliteration Code
ENCOUNTER MISSION TYPE
COLLECTION REASON
BIOMETRIC SUBJECT PRIVACY ACT INDICATOR
ENCOUNTER COMMENT
IRIS IMAGE OMITTED REASON
COLLECTION COCOM
PALMPRINT IMAGE OMITTED REASON
COLLECTION LOCATION
- Universal Time Entry
- Latitude Degree Value
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
1
1
0
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Max
Occ.
100
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Page 31 of 79
Mnemonic
GRPMBR
- GMNAM
- GMTYP
- GMRL
- ADD1
- ADD2
- CITY
- STATE
- CTRY
- POSTAL
- VLG
- PHNUM
- COM
SUBJ_NAME
- NAM1
- NAM2
- NAM3
- NAM4
- NAM5
- NAM_VLD
- TRANSLIT_CD
ENCTR_MSN
COL_RSN
PRI_ACT
ENCTR_COM
IOMITTED
COCOM
PIOMITTED
COLL_BLO
- UTE
- LTD
Electronic Biometric Transmission Specification Version 3.0
Field
Number
2.8114_3
2.8114_4
2.8114_5
2.8114_6
2.8114_7
2.8114_8
2.8114_9
2.8114_10
2.8114_11
2.8114_12
2.8114_13
2.8114_14
2.8114_15
2.8114_16
2.8114_17
2.8114_18
2.8114_19
2.8114_20
2.8115
2.8115_1
2.8115_2
2.8115_3
2.8115_4
2.8115_5
2.8115_6
2.8115_7
2.8115_8
2.8115_9
DIN: BIMA-STB-STD-11-001
Field Name
- Latitude Minute Value
- Latitude Second Value
- Longitude Degree Value
- Longitude Minute Value
- Longitude Second Value
- Elevation
- Geodetic Datum Code
- Geographic Coordinate Universal Transverse Mercator
Zone
- Geographic Coordinate Universal Transverse Mercator
Easting
- Geographic Coordinate Universal Transverse Mercator
Northing
- Geographic Reference Text
- Geographic Coordinate Other System Identifier
- Geographic Coordinate Other System Value
- City
- State/Province
- Country Code
- Village
- Record Category Code
OPERATIONAL PERSONNEL
- Operational Personnel Unit/Organization
- Operational Personnel Role
- Rank Grade Code
- US Person Indicator
- Operational Personnel Identifier Type
- Operational Personnel Identifier
- Name – One
- Name – Two
- Name – Three
Min
Occ.
0
0
0
0
0
0
0
0
Max
Occ.
1
1
1
1
1
1
1
1
Mnemonic
0
1
- GCE
0
1
- GCN
0
0
0
0
0
1
0
1
0
0
1
0
0
0
0
1
1
0
1
1
1
1
1
1
1
1
20
1
1
1
1
1
1
1
1
1
- GRT
- OSI
- OCV
- CITY
- STATE
- CTRY
- VLG
- REC
OPER
- OPORG
- OPRL
- RANK
- USIND
- OPIDCATCD
- OPID
- NAM1
- NAM2
- NAM3
Page 32 of 79
- LTM
- LTS
- LGD
- LGM
- LGS
- ELE
- GDC
- GCM
Electronic Biometric Transmission Specification Version 3.0
Field
Number
2.8115_10
2.8115_11
2.8115_12
2.8115_13
2.8116
2.8116_1
2.8116_2
2.8116_3
2.8116_4
2.8116_5
2.8116_6
2.8116_7
2.8116_8
2.8117
2.8118
2.8118_1
2.8118_2
2.8118_3
2.8118_4
2.8399
2.8399_1
2.8399_2
2.8399_3
2.8399_4
2.8399_5
2.8399_6
DIN: BIMA-STB-STD-11-001
Field Name
- Name – Four
- Name – Five
- Phone Number
- Email Address
TRANSPORTATION
- Transport Type
- Transport Identifier Category Code
- Transport Identifier
- Transport Make
- Transport Model
- Transport Model Year
- Transport Color Description
- Comment
FACIAL IMAGE OMITTED REASON
COLLECTION EQUIPMENT MAKE/MODEL/SERIAL
NUMBER
- Make
- Model
- Serial Number
- Record Category Code
CAVEAT
- Caveat Originating Agency Country Code
- Caveat Originating Agency Name
- Caveat Originating Agency Identifier
- Caveat Date
- Caveat Category Code
- Caveat Text
Min
Occ.
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
Max
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Mnemonic
1
1
1
1
0
1
1
1
1
1
1
1
1
1
1
40
1
1
1
1
1
1
MAK
MOD
SER
REC
CAV
- CAV_CNTRY_CD
- CAV_ORI_NAME
- CAV_ORI
- CAV_DT
- CAV_CAT_CD
- CAV_TXT
Page 33 of 79
- NAME4
- NAME5
- PHNUM
- EMAIL
TRANSPORT
- TRANSPORT_TYP
- TRANSPORT_IDCATCD
- TRANSPORT_ID
- TRANSPORT_MAK
- TRANSPORT_MOD
- TRANSPORT_MODYR
- TRANSPORT_COL
- COM
FOMITTED
COLL_MMS
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.3 Type-9 Records [Minutiae Data]
DoD EBTS Type-9 records are defined in the ITL 1-2011. DoD EBTS Type-9 records shall choose one
of the following minutiae blocks as defined in ITL 1-2011, Table 27:
a. the “IAFIS Features” (FBI Native-Mode) minutiae block (fields 13-30) as described in the FBI
EBTS v9.3.
b. the “INCITS M1-378 Features” minutiae block (fields 126-150) as described in Table 28 of
ITL 1-2011.
Page 34 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 5: Type-9 Minutiae Data Recor d Layout (IAFIS Featur es)
Field
Number
9.001
9.002
9.003
9.004
9.013
9.014
9.015
9.016
9.017
9.018
9.019
9.020
9.021
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
IMPRESSION TYPE
MINUTIAE FORMAT
AFIS FEATURE VECTOR
FINGER NUMBER
NUMBER OF MINUTIAE
FINGERPRINT CHARACTERIZATION PROCESS
- Equipment
- Version Identifier
- Method
AFIS/FBI PATTERN CLASSIFICATION
- Pattern Classification
- Ridge Count Number 1
- Ridge Count Number 2
REGION OF VALUE POLYGON
COORDINATE OFFSETS
- Offset to Upper Left Corner Subimage
- Center of Rotation in Subimage
- Rotation Angle Clock Wise Degrees
- Rotation Center in Rotated Subimage
- Offset to Upper Left Corner Final Subimage
ORIENTATION UNCERTAINTY
CORE ATTRIBUTES
- Core Location
- Core Direction in Degrees
- Core Position Uncertainty
Min
Occ.
1
1
1
1
0
1
1
1
Max
Occ.
1
1
1
1
1
1
1
1
0
3
3
0
20
1
1
0
1
2
Page 35 of 79
Mnemonic
LEN (Used only in traditional encoding version)
IDC
IMP
FMT
AFV
FGN
NMN
FCP
- VEN
- VID
- MET
APC
- APAT
- RCN1
- RCN2
ROV
COF
- XYP
- XYP
- THET
- XYP
- XYP
ORN
CRA
- XYM
- DID
- PUM
Electronic Biometric Transmission Specification Version 3.0
Field
Number
9.022
9.023
9.024
9.025
9.3009.399
9.901
3
Field Name
DELTA ATTRIBUTES
- Delta Location
- Upward Flow Direction
- Leftward Flow Direction
- Rightward Flow Direction
- Delta Position Uncertainty
MINUTIA AND RIDGE COUNT DATA
- Minutia Index Number
- Location Direction
- Quality Measure
- Minutia Type
- Minutia Index and Ridge Count Octant 0
- Minutia Index and Ridge Count Octant 1
- Minutia Index and Ridge Count Octant 2
- Minutia Index and Ridge Count Octant 3
- Minutia Index and Ridge Count Octant 4
- Minutia Index and Ridge Count Octant 5
- Minutia Index and Ridge Count Octant 6
- Minutia Index and Ridge Count Octant 7
- Octant Residuals
CHARACTERIZATION QUALITY
CLASSIFIER QUALITY
EXTENDED FEATURE SET 3
UNIVERSAL LATENT ANNOTATION
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
Max
Occ.
2
Mnemonic
1
254
0
0
-
1
1
-
0
Unlimited ULA
DLA
- XYM
- DID
- DID
- DID
- PUM
MAT
- MDX
- XYT
- QMS
- MNT
- MRO
- MRO1
- MRO2
- MRO3
- MRO4
- MRO5
- MRO6
- MRO7
- RSO
CHQ
CLQ
EXTENDED FEATURE SET
Enhancements for Extended Feature Sets supported by ANSI/NIST ITL-1-2011 are being considered in future drafts of EBTS.
Page 36 of 79
Electronic Biometric Transmission Specification Version 3.0
Field
Number
9.902
9.903
9.904
Field Name
ANNOTATED INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
DEVICE UNIQUE IDENTIFIER
MAKE/MODEL/SERIAL NUMBER
- Make
- Model
- Serial Number
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
0
1
Max
Mnemonic
Occ.
Unlimited ANN
- GMT
- NAV
- OWN
- PRO
1
DUI
1
MAKE/MODEL/SERIAL NUMBER
- MAK
- MOD
- SER
Table 6: Type-9 Minutiae Data Recor d Layout (INCITS-378 Featur es)
Field
Number
9.001
9.002
9.003
9.004
9.126
9.127
9.128
9.129
9.130
9.131
Field Name
LOGICAL RECORD LENGTH
INFORMATION DESIGNATION CHARACTER
IMPRESSION TYPE
MINUTIAE FORMAT
CBEFF INFORMATION
- CBEFF Format Owner
- CBEFF Format Type
- CBEFF Product Identifier
CAPTURE EQUIPMENT IDENTIFICATION
- Capture Equipment Conformance Status
- Capture Equipment Identifier
HORIZONTAL LINE LENGTH
VERTICAL LINE LENGTH
SCALE UNITS
TRANSMITTED HORIZONTAL PIXEL SCALE
Min
Occ.
1
1
1
1
1
Max
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Page 37 of 79
Mnemonic
IDC
IMP
FMT
CBI
- CFO
- CFT
- CPI
CEI
- AFS
- CID
HLL
VLL
SLC
THPS
Electronic Biometric Transmission Specification Version 3.0
Field
Number
9.132
9.133
9.134
9.135
9.136
9.137
9.138
9.139
9.140
Field Name
TRANSMITTED VERTICAL PIXEL SCALE
FINGER VIEW
FRICTION RIDGE GENERALIZED POSITION
FRICTION RIDGE QUALITY DATA
- Quality Value
- Algorithm Vendor Identification
- Algorithm Product Identification
NUMBER OF MINUTIAE
FINGER MINUTIA DATA
- Minutia Index Number
- Minutia X Coordinate
- Minutia Y Coordinate
- Minutia Angle
- Minutia Type
- Quality of Minutia
RIDGE COUNT INFORMATION
- Ridge Count Extraction Method
- “0”
- “0”
or
- Centering Minutiae Index
- Neighboring Minutiae Index
- Number of Ridges Crossed
CORE INFORMATON
- Core X Coordinate
- Core Y Coordinate
- Angle of the Core
DELTA INFORMATON
- Delta X Coordinate
- Delta Y Coordinate
- First Angle of the Delta
DIN: BIMA-STB-STD-11-001
Min
Occ.
1
1
1
1
Max
Occ.
1
1
1
1
1
1
1
n1
0
n1
0
9
0
9
Page 38 of 79
Mnemonic
TVPS
FVW
FGP
FQD
- QVU
- QAV
- QAP
NOM
FMD
- MAN
- MXC
- MYC
- MAV
- MTY
- QOM
RCI
- REM
- “0”
- “0”
or
- CMI
- NMN
- NRC
CIN
- XCC
- YCC
- ANGC
DIN
- XCD
- YCD
- ANG1
Electronic Biometric Transmission Specification Version 3.0
Field
Number
9.141
Field Name
9.3009.399
9.901
9.902
9.903
9.904
DIN: BIMA-STB-STD-11-001
M1 DELTA INFORMATION
Min
Occ.
0
Max
Occ.
9
EXTENDED FEATURE SET 4
N/A
N/A
UNIVERSAL LATENT ANNOTATION
ANNOTATED INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
DEVICE UNIQUE IDENTIFIER
MAKE/MODEL/SERIAL NUMBER
- Make
- Model
- Serial Number
0
0
Unlimited ULA
1
ANN
- GMT
- NAV
- OWN
- PRO
1
DUI
1
MAKE/MODEL/SERIAL NUMBER
- MAK
- MOD
- SER
0
1
Mnemonic
ADA
- ANG2
- ANG3
EXTENDED FEATURE SET
Note 1: n equals the number of minutiae points
4
Enhancements for Extended Feature Sets supported by ANSI/NIST ITL-1-2011 are being considered in future drafts of EBTS.
Page 39 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.4 Type-10 Records [Facial & SMT]
DoD EBTS Type-10 records are defined in ITL 1-2011. Type-10 records shall contain face, SMT, and /
or other body part image data and related information pertaining to the specific image contained in this
record. It shall be used to exchange both grayscale and color image data in a compressed or
uncompressed form.
DoD EBTS v3.0 deprecates three user defined fields that were included in EBTS v2.0.
•
Field 10.200 Device Unique Identifier (DEV_UI) – Deprecated by Field 10.903 Device Unique
Identifier (DUI)
•
Field 10.201 Capture Device Global Identifier (DEV_GI) – Deprecated by Field 10.903 Device
Unique Identifier (DUI)
•
Field 10.202 Capture Device Information (DEV_INFO) – Deprecated by Field 10.904
Make/Model/Serial Number
Page 40 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 7: Type-10 Facial and SMT Recor d Layout
Field
Number
10.001
10.002
10.003
10.004
10.005
10.006
10.007
10.008
10.009
10.010
10.011
10.012
10.013
10.014
10.015
10.016
10.017
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
IMAGE TYPE
SOURCE AGENCY
PHOTO CAPTURE DATE
HORIZONTAL LINE LENGTH
VERTICAL LINE LENGTH
SCALE UNITS
TRANSMITTED HORIZONTAL PIXEL SCALE
TRANSMITTED VERTICAL PIXEL SCALE
COMPRESSION ALGORITHM
COLOR SPACE
SUBJECT ACQUISITION PROFILE
FACE IMAGE POSITION COORDINATES IN FULL
POSITION
- Left Horizontal Coordinate Value
- Right Horizontal Coordinate Value
- Top Vertical Coordinate Value
- Bottom Vertical Coordinate Value
- Bounding Box Head Position Code
FACE IMAGE PATH COORDINATES IN FULL IMAGE
- Boundary Code
- Number of Points
- Horizontal Point Offset
- Vertical Point Offset
SCANNED HORIZONTAL PIXEL SCALE
SCANNED VERTICLE PIXEL SCALE
Min
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
0
Max
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Mnemonic
0
1
0
0
1
1
FPFI
- BYC
- NOP
- HPO
- VPO
SHPS
SVPS
Page 41 of 79
LEN (Used only in traditional encoding version)
IDC
IMT
SRC
PHD
HLL
VLL
SLC
THPS
TVPS
CGA
CSP
SAP
FIP
- LHC
- RHC
- TVC
- BVC
- BBC
Electronic Biometric Transmission Specification Version 3.0
Field
Number
10.018
10.019
10.020
10.021
10.023
10.024
10.025
10.026
10.027
10.028
10.029
10.030
10.031
Field Name
DISTORTION
- Distortion Code
- Distortion Measurement Code
- Distortion Severity Code
LIGHTING ARTIFACTS
SUBJECT POSE
POSE OFFSET ANGLE
PHOTO ACQUISITION SOURCE
- Photo Attribute Code
- Vendor – Specific Description
SUBJECT QUALITY SCORE
- Quality Value
- Algorithm Vendor Identification
- Algorithm Product Identification
SUBJECT POSE ANGLES
- Yaw Angle
- Pitch angle
- Roll Angle
- Uncertainty in Degrees for Yaw
- Uncertainty in Degrees for Pitch
- Uncertainty in Degrees for Roll
SUBJECT FACIAL DESCRIPTION
SUBJECT EYE COLOR
SUBJECT HAIR COLOR
FACIAL FEATURE POINTS
- Feature Point Type
- Feature Point Code
- X Coordinate
- Y Coordinate
DEVICE MONITORING MODE
TIERED MARKUP COLLECTION
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
Max
Occ.
1
0
0
0
0
3
1
1
1
0
9
0
1
0
0
0
0
50
1
2
88
0
0
1
1
Page 42 of 79
Mnemonic
DIST
- IDK
- IDM
- DSC
LAF
POS
POA
PAS
- PAC
- VSD
SQS
- QVU
- QAV
- QAP
SPA
- YAW
- PIT
- ROL
- YAWU
- PITU
- ROLU
SXS
SEC
SHC
FFP
- FPT
- FPC
- HCX
- HCY
DMM
TMC
Electronic Biometric Transmission Specification Version 3.0
Field
Number
10.032
10.033
10.038
10.039
10.040
10.041
10.042
10.043
5
Field Name
3D FACIAL FEATURE POINTS
- Feature Point Type
- Feature Point Code
- X Coordinate
- Y Coordinate
- Z Coordinate
FEATURE CONTOURS
- Feature Contour Codes
- Number of Points
- Horizontal Pixel Offset 5
- Vertical Pixel Offset
COMMENT
TYPE-10 REFERENCE NUMBER
NCIC SMT CODE
SMT SIZE
- SMT Height
- SMT Width
SMT DESCRIPTORS
- SMT Code Indicator
- Tattoo Class
- Tattoo Subclass
- Tattoo Description
TATTOO COLOR
- Tattoo Color Code 1
- Tattoo Color Code 2
- Tattoo Color Code 3
- Tattoo Color Code 4
- Tattoo Color Code 5
- Tattoo Color Code 6
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
Max
Occ.
88
0
12
0
0
0
0
1
1
3
1
0
9
0
9
Mnemonic
3DF
- FPT
- FPC
- HCX
- HCY
- HCZ
FEC
- FCC
- NOP
- HPO
- VPO
COM
T10
SMT
SMS
- HGT
- WID
SMD
- SMI
- TAC
- TSC
- TDS
COL
- TC1
- TC2
- TC3
- TC4
- TC5
- TC6
Horizontal and Vertical Pixel Offsets are repeated in pairs, in order by point following the contour, up to the final point for a total Number of Point pairs
Page 43 of 79
Electronic Biometric Transmission Specification Version 3.0
Field
Number
10.044
10.045
10.200 –
10.900
10.902
10.903
10.904
10.993
10.995
10.996
10.997
Field Name
IMAGE TRANSFORM
OCCLUSIONS
- Occlusion Opacity
- Occlusion Type
- Number of Points
- Horizontal Point Offset 6
- Vertical Point Offset
USER DEFINED FIELDS
ANNOTATED INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
DEVICE UNIQUE IDENTIFIER
MAKE/MODEL/SERIAL NUMBER
- Make
- Model
- Serial Number
SOURCE AGENCY NAME
ASSOCIATED CONTEXT
- Associated Context Number
- Associated Segment Position
HASH
SOURCE REPRESENTATION
- Source Representation Number
- Reference Segment Position
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
0
Max
Occ.
1
16
N/A
N/A
0
Unlimited ANN
- GMT
- NAV
- OWN
- PRO
1
DUI
1
MMS
- MAK
- MOD
- SER
1
SAN
255
ASC
- ACN
- ASP
1
HAS
255
SOR
- SRN
- RSP
0
1
0
0
0
0
6
Mnemonic
ITX
OCC
- OCY
- OCT
- NOP
- HPO
- VPO
UDF
The Horizontal Pixel Offset and Vertical Pixel Offset are repeated as pairs, in order by point following the contour, up to the final point For a total of Number of Points (NOP) Pairs
Page 44 of 79
Electronic Biometric Transmission Specification Version 3.0
Field
Number
10.998
10.999
Field Name
GEOGRAPHIC SAMPLE ACQUISITION LOCATION
- (See ITL 1-2011 for Informational Items)
BODY PART IMAGE
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
Max
Occ.
1
1
1
Page 45 of 79
Mnemonic
GEO
- (See ITL 1-2011 for Mnemonics)
DATA
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.5 Type-13 Records [Variable-Resolution Latent Image]
DoD EBTS Type-13 records are defined in ITL 1-2011. The Type-13 record shall contain image data
acquired from latent captures of friction ridge images. These images require human intervention and
processing to extract the desired feature information from the images. Information regarding the
scanning resolution used, the image size, and other parameters required to process the image, are
recorded as fields within the record.
DoD EBTS v3.0 deprecates three user defined fields that were included in EBTS v2.0.
•
Field 13.200 Device Unique Identifier (DEV_UI) – Deprecated by Field 13.903 Device Unique
Identifier (DUI)
•
Field 13.201 Capture Device Global Identifier (DEV_GI) – Deprecated by Field 13.903 Device
Unique Identifier (DUI)
•
Field 13.202 Capture Device Information (DEV_INFO) – Deprecated by Field 13.904
Make/Model/Serial Number
•
Field 13.203 Latent Circumstances (LATENT_CIRC) – Deprecated by Field 13.020 Comment
•
Field 13.204 Latent Source Item (LATENT_ITM) – Deprecated by Type-20 or by Field 13.020
•
Field 13.205 Latent Development (LATENT_MET) – Deprecated by Field 13.902 Annotated
Information and/or Field 13.902_4 Process Description
Page 46 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 8: Type-13 Var iable-Resolution Latent Recor d Layout
Field
Number
13.001
13.002
13.003
13.004
13.005
13.006
13.007
13.008
13.009
13.010
13.011
13.012
13.013
13.014
13.015
13.016
13.017
13.020
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
IMPRESSION TYPE
SOURCE AGENCY
LATENT CAPTURE DATE
HORIZONTAL LINE LENGTH
VERTICAL LINE LENGTH
SCALE UNITS
TRANSMITTED HORIZONTAL PIXEL SCALE
TRANSMITTED VERTICAL PIXEL SCALE
COMPRESSION ALGORITHM
BITS PER PIXEL
FRICTION RIDGE GENERALIZED POSITION
SEARCH POSITION DESCRIPTORS
- Probable Decimal Finger Position Code
- Finger Image Code
PRINT POSITION COORDINATES
- Full Finger View
- Location of a Segment
- Left Horizontal Coordinate
- Right Horizontal Coordinate
- Top Vertical Coordinate
- Bottom Vertical Coordinate
SCANNED HORIZONTAL PIXEL SCALE
SCANNED VERTICAL PIXEL SCALE
COMMENT
Min
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
0
Max
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
6
9
0
12
0
0
0
1
1
1
Page 47 of 79
Mnemonic
LEN (Used only in traditional encoding version)
IDC
IMP
SRC
LCD
HLL
VLL
SLC
THPS
TVPS
CGA
BPX
FGP
SPD
- PDF
- FIC
PPC
- FVC
- LOS
- LHC
- RHC
- TVC
- BVC
SHPS
SVPS
COM
Electronic Biometric Transmission Specification Version 3.0
Field
Number
13.024
Min
Occ.
0
Max
Occ.
4
N/A
N/A
0
13.998
ANNOTATED INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
DEVICE UNIQUE IDENTIFIER
MAKE/MODEL/SERIAL NUMBER
- Make
- Model
- Serial Number
SOURCE AGENCY NAME
ASSOCIATED CONTEXT
- Associated Context Number
- Associated Segment Position
HASH
SOURCE REPRESENTATION
- Source Representation Number
- Reference Segment Position
GEOGRAPHIC SAMPLE ACQUISITION LOCATION
13.999
LATENT FRICTION RIDGE IMAGE
1
Unlimited ANN
- GMT
- NAV
- OWN
- PRO
1
DUI
1
MMS
- MAK
- MOD
- SER
1
SAN
255
ASC
- ACN
- ASP
1
HAS
255
SOR
- SRN
- RSP
1
GEO
- (See ITL 1-2011 for Informational Items)
1
DATA
13.200 –
13.900
13.902
13.903
13.904
13.993
13.995
13.996
13.997
Field Name
DIN: BIMA-STB-STD-11-001
LATENT QUALITY METRIC
- Friction Ridge Metric Position
- Quality Value
- Algorithm Vendor Identification
- Algorithm Product Identification
USER DEFINED FIELDS
0
1
0
0
0
0
0
Page 48 of 79
Mnemonic
LQM
- FRMP
- QVU
- QAV
- QAP
UDF
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.6 Type-14 Records [Var-Res Fingerprint Image]
DoD EBTS Type-14 records are defined in ITL 1-2011. The Type-14 record shall contain and be used to
exchange exemplar fingerprint image data, such as a rolled tenprint, identification flats, or other
complete friction ridge exemplar defined in Section 3.6.1.
DoD EBTS v3.0 deprecates three user defined fields that were included in EBTS v2.0.
•
Field 14.200 Device Unique Identifier (DEV_UI) – Deprecated by Field 14.903 Device Unique
Identifier (DUI)
•
Field 14.201 Capture Device Global Identifier (DEV_GI) – Deprecated by Field 14.903 Device
Unique Identifier (DUI)
•
Field 14.202 Capture Device Information (DEV_INFO) – Deprecated by Field 14.904
Make/Model/Serial Number
Page 49 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 9: Type-14 Var iable-Resolution Finger pr int Recor d Layout
Field
Number
14.001
14.002
14.003
14.004
14.005
14.006
14.007
14.008
14.009
14.010
14.011
14.012
14.013
14.014
14.015
14.016
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
IMPRESSION TYPE
SOURCE AGENCY
FINGERPRINT CAPTURE DATE
HORIZONTAL LINE LENGTH
VERTICAL LINE LENGTH
SCALE UNITS
TRANSMITTED HORIZONTAL PIXEL SCALE
TRANSMITTED VERTICAL PIXEL SCALE
COMPRESSION ALGORITHM
BITS PER PIXEL
FRICTION RIDGE GENERALIZED POSITION7
PRINT POSITION DESCRIPTORS
- Probable Decimal Finger Position Code
- Finger Image Code
PRINT POSITION COORDINATES
- Full Finger View
- Location of a Segment
- Left Horizontal Coordinate
- Right Horizontal Coordinate
- Top Vertical Coordinate
- Bottom Vertical Coordinate
SCANNED HORIZONTAL PIXEL SCALE
Min
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
0
Max
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
12
0
1
7
Mnemonic
LEN (Used only in traditional encoding version)
IDC
IMP
SRC
FCD
HLL
VLL
SLC
THPS
TVPS
CGA
BPX
FGP
PPD
- DFP
- FIC
PRINT POSITION COORDINATES
- FVC
- LOS
- LHC
- RHC
- TVC
- BVC
SHPS
In the 2007 and 2008 versions of the ITL standard, this field had a repeating subfield that could occur up to 6 times. Since only one image is sent per
record, the maximum should have been 1 to maintain backward compatibility, the subfield structure has been retained, but with a maximum occurrence of
once.
Page 50 of 79
Electronic Biometric Transmission Specification Version 3.0
Field
Number
14.017
14.018
14.020
14.021
14.022
14.023
14.024
14.025
14.026
14.027
DIN: BIMA-STB-STD-11-001
Field Name
SCANNED VERTICAL PIXEL SCALE
AMPUTATED OR BANDAGED
- Friction Ridge Generalized Amputated or Bandaged
Position
- Amputated or Bandaged Code
COMMENT
FINGERPRINT SEGMENT POSITION(S)
- Friction Ridge Generalized Position
- Left Horizontal Coordinate Value
- Right Horizontal Coordinate Value
- Top Vertical Coordinate Value
- Bottom Vertical Coordinate Value
NIST QUALITY METRIC
- Finger Position Code
- NIST Image Quality Score Quantity
SEGMENTATION QUALITY METRIC
- Friction Ridge Segment Quality Position
- Quality Value
- Algorithm Vendor Identification
- Algorithm Product Identification
FINGERPRINT QUALITY METRIC
- Friction Ridge Metric Position
- Quality Value
- Algorithm Vendor Identification
- Algorithm Product Identification
ALTERNATE FINGER SEGMENT POSITION(S)
- Friction Ridge Alternate Segment Position
- Number of Points
- Horizontal Pixel Offset
- Vertical Pixel Offset
SIMULTANEOUS CAPTURE
STITCHED IMAGE FLAG
Min
Occ.
0
0
Max
Occ.
1
4
0
0
1
1
0
5
0
5
0
5
0
5
0
1
0
1
Page 51 of 79
Mnemonic
SVPS
AMP
- FRAP
- ABC
COM
SEG
- FRSP
- LHC
- RHC
- TVC
- BVC
NQM
- FRNP
- IQS
SQM
- FRQP
- QVU
- QAV
- QAP
FQM
- FRMP
- QVU
- QAV
- QAP
ASEG
- FRAS
- NOP
- HPO
- VPO
SCF
SIF
Electronic Biometric Transmission Specification Version 3.0
Field
Number
14.030
14.031
14.200 –
14.900
14.902
14.903
14.904
14.993
14.995
14.996
14.997
14.998
14.999
DIN: BIMA-STB-STD-11-001
Field Name
Min
Occ.
0
0
N/A
Max
Occ.
1
1
N/A
ANNOTATED INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
DEVICE UNIQUE IDENTIFIER
MAKE/MODEL/SERIAL NUMBER
- Make
- Model
- Serial Number
SOURCE AGENCY NAME
ASSOCIATED CONTEXT
0
HASH
SOURCE REPRESENTATION
- Source Representation Number
- Reference Segment Position
GEOGRAPHIC SAMPLE ACQUISITION LOCATION
(See ITL 1-2011 for Informational Items)
FINGERPRINT IMAGE
0
0
0
Unlimited ANN
- GMT
- NAV
- OWN
- PRO
1
DUI
1
MMS
- MAK
- MOD
- SER
1
SAN
255
ASC
- ACN
- ASP
1
HAS
255
SOR
- SRN
- RSP
1
GEO
1
1
DEVICE MONITORING MODE
SUBJECT ACQUISITION PROFILE – FINGERPRINT
USER DEFINED FIELDS
0
1
0
0
Page 52 of 79
Mnemonic
DMM
FAP
UDF
DATA
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.7 Type-15 Records [Var-Res Palmprint Image]
DoD EBTS Type-15 records are defined in ITL 1-2011. The Type-15 record shall contain and be used to
exchange palm print image data. Information regarding the scanning resolution used, the image size, and
other parameters or comments required to process the image are recorded as fields within the record.
DoD EBTS v3.0 deprecates three user defined fields that were included in EBTS v2.0.
•
Field 15.200 Device Unique Identifier (DEV_UI) – Deprecated by Field 15.903 Device Unique
Identifier (DUI)
•
Field 15.201 Capture Device Global Identifier (DEV_GI) – Deprecated by Field 15.903 Device
Unique Identifier (DUI)
•
Field 15.202 Capture Device Information (DEV_INFO) – Deprecated by Field 15.904
Make/Model/Serial Number
Page 53 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 10: Type-15 Var iable-Resolution Palmpr int Recor d Layout
Field
Number
15.001
15.002
15.003
15.004
15.005
15.006
15.007
15.008
15.009
15.010
15.011
15.012
15.013
15.016
15.017
15.018
15.020
15.024
15.030
15.200 –
15.900
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
IMPRESSION TYPE
SOURCE AGENCY
PALMPRINT CAPTURE DATE
HORIZONTAL LINE LENGTH
VERTICAL LINE LENGTH
SCALE UNITS
TRANSMITTED HORIZONTAL PICTURE SCALE
TRANSMITTED VERTICAL PICTURE SCALE
COMPRESSION ALGORITHM
BITS PER PIXEL
FRICTION RIDGE GENERALIZED POSITION
SCANNED HORIZONTAL PIXEL SCALE
SCANNED VERTICAL PIXEL SCALE
AMPUTATED OR BANDAGED
- Friction Ridge Amputated or Bandaged Position
- Amputated or Bandaged Code
COMMENT
PALMPRINT QUALITY METRIC
- Friction Ridge Metric Position
- Quality Value
- Algorithm Vendor Identification
- Algorithm Product Identification
DEVICE MONITORING MODE
USER DEFINED FIELDS
Min
Occ.
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
Max
Occ.
1
1
1
1
1
1
1
0
0
1
9
0
N/A
1
N/A
Page 54 of 79
1
1
1
1
1
1
1
9
Mnemonic
LEN (Used only in traditional encoding version)
IDC
IMP
SRC
PCD
HLL
VLL
SLC
THPS
TVPS
CGA
BPX
FGP
SHPS
SVPS
AMP
- FRAP
- ABC
COM
PQM
- FRMP
- QVU
- QAV
- QAP
DMM
UDF
Electronic Biometric Transmission Specification Version 3.0
Field
Number
15.902
15.903
15.904
15.993
15.995
15.996
15.997
15.998
15.999
Field Name
ANNOTATED INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
DEVICE UNIQUE IDENTIFIER
MAKE/MODEL/SERIAL NUMBER
- Make
- Model
- Serial Number
SOURCE AGENCY NAME
ASSOCIATED CONTEXT
- Associated Context Number
- Associated Segment Position
HASH
SOURCE REPRESENTATION
- Source Representation Number
- Reference Segment Position
GEOGRAPHIC SAMPLE ACQUISITION LOCATION
- (See ITL-2011 for Informational Items)
PALMPRINT IMAGE
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
0
Max
Mnemonic
Occ.
Unlimited ANN
- GMT
- NAV
- OWN
- PRO
1
DUI
1
MMS
- MAK
- MOD
- SER
1
SAN
255
ASC
- ACN
- ASP
1
HAS
255
SOR
- SRN
- RSP
1
GEO
0
1
0
0
0
0
0
0
Page 55 of 79
DATA
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.8 Type-17 Records [Iris Image]
DoD EBTS Type-17 records are defined in ITL 1-2011. The Type-17 record shall contain and be used to
exchange generic iris image data using fields of this record type.
DoD EBTS v3.0 deprecates three user defined fields that were included in EBTS v2.0.
•
Field 17.200 Device Unique Identifier (DEV_UI) – Deprecated by Field 17.017 Device Unique
Identifier (DUI)
•
Field 17.201 Capture Device Global Identifier (DEV_GI) – Deprecated by Field 17.017 Device
Unique Identifier (DUI)
•
Field 17.202 Capture Device Information (DEV_INFO) – Deprecated by Field 17.019
Make/Model/Serial Number
Page 56 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 11: Type-17 Ir is Image Recor d Layout
Field
Number
17.001
17.002
17.003
17.004
17.005
17.006
17.007
17.008
17.009
17.010
17.011
17.012
17.013
17.014
17.015
17.016
17.017
17.019
17.020
17.021
17.022
17.023
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
EYE LABEL
SOURCE AGENCY
IRIS CAPTURE DATE
HORIZONTAL LINE LENGTH
VERTICAL LINE LENGTH
SCALE UNITS
TRANSMITTED HORIZONTAL PIXEL SCALE
TRANSMITTED VERTICAL PIXEL SCALE
COMPRESSION ALGORITHM
BITS PER PIXEL
COLOR SPACE
ROTATION ANGLE OF EYE
ROTATION UNCERTAINTY
IMAGE PROPERTY CODE
- Horizontal Orientation Code
- Vertical Orientation Code
- Specific Scan Type
DEVICE UNIQUE IDENTIFIER
MAKE/MODEL/SERIAL NUMBER
- Make
- Model
- Serial Number
EYE COLOR
COMMENT
SCANNED HORIZONTAL PIXEL SCALE
SCANNED VERTICAL PIXEL SCALE
Min
Occ.
1
1
1
1
0
0
0
0
0
0
0
0
0
0
0
0
Max
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0
0
1
1
0
1
0
1
0
1
0
1
Page 57 of 79
Mnemonic
LEN (Used only in traditional encoding version)
IDC
ELR
SRC
ICD
HLL
VLL
SLC
THPS
TVPS
CGA
BPX
CSP
RAE
RAU
IPC
- IHO
- IVO
- IST
DUI
MMS
- MAK
- MOD
- SER
ECL
COM
SHPS
SVPS
Electronic Biometric Transmission Specification Version 3.0
Field
Number
17.024
17.025
17.026
17.027
17.028
17.030
17.031
17.032
17.033
17.034
17.035
Field Name
IMAGE QUALITY SCORE
- Quality Value
- Algorithm Vendor Identifier
- Algorithm Product Identification
ACQUISITION LIGHTING SPECTRUM
IRIS DIAMETER
SPECIFIED SPECTRUM VALUES
- Spectrum Lower Bound
- Spectrum Upper Bound
DAMAGED OR MISSING EYE
DEVICE MONITORING MODE
SUBJECT ACQUISITION PROFILE – IRIS
IRIS STORAGE FORMAT
IRIS PUPIL BOUNDARY
- Boundary Code
- Number of Points
- Horizontal Point Offset 8
- Vertical Point Offset
IRIS SCLERA BOUNDARY
- Boundary Code
- Number of Points
- Horizontal Point Offset
- Vertical Point Offset
UPPER EYELID BOUNDARY
- Boundary Code
- Number of Points
- Horizontal Point Offset
- Vertical Point Offset
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
Max
Occ.
1
0
0
0
1
1
1
0
0
0
0
0
1
1
1
1
1
0
1
0
1
8
Mnemonic
IQS
- QVU
- QAV
- QAP
EAS
IRD
SSV
- LOW
- HIG
DME
DMM
IAP
ISF
IPB
- BYC
- NOP
- HPO
- VPO
ISB
- BYC
- NOP
- HPO
- VPO
UEB
- BYC
- NOP
- HPO
- VPO
The Horizontal Point Offset and Vertical Point Offset are repeated subfields for 17.033, 17.034, 17.035, 17.036, 17.037 – according to the total of
Number of Points pairs
Page 58 of 79
Electronic Biometric Transmission Specification Version 3.0
Field
Number
17.036
17.037
17.040
17.041
17.200 –
17.900
17.902
17.993
17.995
17.996
17.997
9
Field Name
LOWER EYELID BOUNDARY
- Boundary Code
- Number of Points
- Horizontal Point Offset
- Vertical Point Offset
NON-EYELID OCCLUSIONS
- Occlusion Opacity 9
- Occlusion Type
- Number of Points
- Horizontal Point Offset
- Vertical Point Offset
RANGE
FRONTAL GAZE
USER DEFINED FIELDS
ANNOTATED INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
SOURCE AGENCY NAME
ASSOCIATED CONTEXT
- Associated Context Number
- Associated Segment Position
HASH
SOURCE REPRESENTATION
- Source Representation Number
- Reference Segment Position
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
Max
Occ.
1
0
1
0
0
N/A
1
1
N/A
0
Unlimited ANN
- GMT
- NAV
- OWN
- PRO
1
SAN
255
ASC
- ACN
- ASP
1
HAS
255
SOR
- SRN
- RSP
0
0
0
0
The subfield allows for unlimited repeating sets of information items
Page 59 of 79
Mnemonic
LEB
- BYC
- NOP
- HPO
- VPO
NEO
- OCY
- OCT
- NOP
- HPO
- VPO
RAN
GAZ
UDF
Electronic Biometric Transmission Specification Version 3.0
Field
Number
17.998
17.999
Field Name
GEOGRAPHIC SAMPLE ACQUISITION LOCATION
- (See ITL 1-2011 for Informational Items)
IRIS IMAGE DATA
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
Max
Occ.
1
Mnemonic
0
1
DATA
Page 60 of 79
GEO
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.9 Type-18 Records [DNA Record]
DoD EBTS Type-18 records are completely defined in ITL 1-2011. New to this version of the standard,
the Type-18 record shall contain and be used to exchange DNA data. This shall be used to exchange
Autosomal Short Tandem Repeat (STR), X-Short Tandem Repeat (X-STR) Y-Short Tandem Repeat (YSTR), Mitochondrial DNA (mtDNA), Pedigree, and electropherogram images of DNA data. This record
type is based upon standardized and commonly used DNA analysis and data reporting conventions.
Page 61 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 12: Type-18 DNA Data Recor d Layout
Field
Number
18.001
18.002
18.003
18.004
18.005
18.006
18.007
18.008
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
DNA LABORATORY SETTING
- Unit Type
- Lab Type
- Accreditation Information
- Name of the Organization
- Point of Contact
- Code of Sending Country
- International Organization Name
SOURCE AGENCY IDENTIFIER
NUMBER OF ANALYSES FLAG
SAMPLE DONOR INFORMATION
- DNA Sample Donor
- Gender ID
- Date of Last Contact
- Date of Birth
- Ethnic Group
- Dental Record Available
- Sample Collection Location Description
- Sample Donor Status
CLAIMED OR PURPORTED RELATIONSHIP
VALIDATED RELATIONSHIP
Min
Occ.
1
1
1
Max
Occ.
1
1
1
1
1
1
1
1
1
0
0
1
1
Page 62 of 79
Mnemonic
LEN (Used only in traditional encoding version)
IDC
DLS
- UTY
- LTY
- ACC
- NOO
- POC
- CSC
- ION
SRC
NAL
SDI
- DSD
- GID
- DLC
- DOB
- EGP
- DRA
- LLC
- SDS
COPR
VRS
Electronic Biometric Transmission Specification Version 3.0
Field
Number
18.009
18.010
18.011
18.012
18.013
18.014
18.015
18.016
18.017
18.018
18.019
18.020
Field Name
PEDIGREE INFORMATION
- Pedigree ID
- Pedigree Member ID
- Pedigree Member Status
- Sample Identifier
- Father Identifier
- Mother Identifier
- Pedigree Comment
SAMPLE TYPE
- Sample Cellular Type
- Sample Origin
SAMPLE TYPING INFORMATION
SAMPLE COLLECTION METHOD
SAMPLE COLLECTION DATE
PROFILE STORAGE DATE
DNA PROFILE DATE
- Profile Type
- Result
- Profile ID
- Supplemental Message
- DNA Profile Comment
AUTOSOMAL STR, X-STR, AND Y-STR PROFILE
- (See ITL 1-2011 for Informational Items)
MITOCHONDRIAL DNA DATA
- (See ITL 1-2011 for Informational Items)
DNA USER-DEFINED PROFILE DATA
ELECTROPHEROGRAM DESCRIPTION
- (See ITL 1-2011 for Informational Items)
DNA GENOTYPE DISTRIBUTION
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
Max
Occ.
1
Mnemonic
0
PED
- PID
- PMI
- PMS
- SID
- FID
- MID
- PCM
1
STY
- SCT
- SMO
5
STI
1
SCM
1
SCD
1
PSD
1
DPD
- PTP
- RES
- PRF
- SUP
- DPC
Unlimited STR
0
1
DMD
0
0
Unlimited UDP
Unlimited EPD
0
1
1
1
0
1
1
1
Page 63 of 79
DGD
Electronic Biometric Transmission Specification Version 3.0
Field
Number
18.021
18.022
18.023
18.200 –
18.900
18.902
18.993
18.995
18.998
Field Name
DNA GENOTYPE ALLELE PAIR
- Genotype Locus Reference
- Allele Pair
- Genotype Numerical Weight
COMMENT
ELECTROPHEROGRAM LADDER
- Ladder Image Reference
- Ladder Storage Type
- Ladder Image Data Descriptor
- Ladder Electropherogram Data
- Ladder Electropherogram Screenshot
USER DEFINED FIELDS
ANNOTATED INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
SOURCE AGENCY NAME
ASSOCIATED CONTEXT
- Associated Context Number
- Associated Segment Position
GEOGRAPHIC SAMPLE ACQUISITION LOCATION
- (See ITL 1-2011 for Informational Items)
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
0
0
N/A
0
0
0
0
Max
Mnemonic
Occ.
Unlimited GAP
- GLR
- ALP
- GNW
1
COM
Unlimited EPL
- LIR
- LST
- LDD
- LEPD
- LES
N/A
UDF
Unlimited ANN
- GMT
- NAV
- OWN
- PRO
1
SAN
255
ASC
- ACN
- ASP
1
GEO
Page 64 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.10 Type-20 Record [Source Representation Record]
DoD EBTS Type-20 records are completely defined in ITL 1-2011. New to this version of the standard,
the Type-20 record contains the source representation(s) from which other Record Types were derived.
Examples are an image of multiple latent prints, of which one or more is of interest. Those would be
segmented and prepared for sending in a Type-13 record. An audio/visual record may provide both
facial images for Type-10 record and an audio recording to be used in a future voice logical record.
There are many more occasions when it might be appropriate to use a Type-20 record.
Page 65 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 13: Type-20 Sour ce Repr esentation Recor d Layout
Field
Number
20.001
20.002
20.003
20.004
20.005
20.006
20.007
20.008
20.009
20.010
20.011
20.012
20.013
20.014
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
SRN CARDINALITY
SOURCE AGENCY
SOURCE REPRESENTATION DATE
HORIZONTAL LINE LENGTH
VERTICAL LINE LENGTH
SCALE UNITS
TRANSMITTED HORIZONTAL PIXEL SCALE
TRANSMITTED VERTICAL PIXEL SCALE
COMPRESSION ALGORITHM
BITS PER PIXEL
COLOR SPACE
ACQUISITION SOURCE
- Acquisition Source Type
- Analog to Digital Conversion
- Radio Transmission Format Description
- Acquisition Special Characteristics
Min
Occ.
1
1
1
1
0
0
0
0
0
0
0
0
0
0
Max
Occ.
1
1
1
1
1
1
1
1
1
1
1
1
1
9
Page 66 of 79
Mnemonic
LEN (Used only in traditional encoding version)
IDC
CAR
SRC
SRD
HLL
VLL
SLC
THPS
TVPS
CGA
BPX
CSP
AQS
- AQT
- A2D
- FDN
- AQSC
Electronic Biometric Transmission Specification Version 3.0
Field
Number
20.015
20.016
20.017
20.018
20.019
20.020
20.021
20.100 –
20.900
20.902
20.903
20.904
20.993
Field Name
SOURCE REPRESENTATION FORMAT
- File Type
- Decoding Instructions
SEGMENTS
- Reference Segment Position
- Internal File Reference Pointer
- Number of Points
- Horizontal Point Offset 10
- Vertical Point Offset
SCANNED HORIZONTAL PIXEL SCALE
SCANNED VERTICAL PIXEL SCALE
TIME INDEX
- Time Index Start
- Time Index End
COMMENT
SOURCE REPRESENTATION NUMBER
USER DEFINED FIELDS
ANNOTATION INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
DEVICE UNIQUE IDENTIFIER
MAKE/MODEL/SERIAL NUMBER
- Make
- Model
- Serial Number
SOURCE AGENCY NAME
DIN: BIMA-STB-STD-11-001
Min
Occ.
1
Max
Occ.
1
0
99
0
0
0
1
1
99
0
1
N/A
1
1
N/A
0
Unlimited
0
1
1
1
0
1
10
Mnemonic
SFT
- FTY
- DEI
SEG
- RSP
- IPT
- NOP
- HPO
- VPO
SHPS
SVPS
TIX
- TIS
- TIE
COM
SRN
UDF
ANN
- GMT
- NAV
- OWN
- PRO
DUI
MMS
- MAK
- MOD
- SER
SAN
The Horizontal and Vertical Point Offset information items are repeated as pairs, in order by point following the contour, up to the final point – for a total
of NOP pairs
Page 67 of 79
Electronic Biometric Transmission Specification Version 3.0
Field
Number
20.994
20.995
20.996
20.998
20.999
DIN: BIMA-STB-STD-11-001
Field Name
EXTERNAL FILE REFERENCE
ASSOCIATED CONTEXT
- Associated Context Number
- Associated Segment Position
HASH
GEOGRAPHIC SAMPLE ACQUISITION LOCATION
- (See ITL-2011 for Informational Items)
SOURCE REPRESENTATION DATA
Min
Occ.
0
0
Max
Occ.
1
255
0
0
1
1
EFR
ASC
- ACN
- ASP
HAS
GEO
0
1
DATA
Page 68 of 79
Mnemonic
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.11 Type-21 Record [Associated Context Record]
DoD EBTS Type-21 records are completely defined in ITL 1-2011. New to this version of the standard,
the Type-21 record contains an associated context record. This information does not contain information
used to derive biometric information contained in other records. Record Type-20 serves that function.
Record Type-21 may be used to convey contextual information, such of a referenced image area where
latent fingerprints were captured.
Page 69 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 14: Type-21 Associated Context Recor d Layout
Field
Number
21.001
21.002
21.004
21.005
21.015
21.016
21.019
21.020
21.021
21.100 –
21.900
21.902
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
SOURCE AGENCY
ASSOCIATED CONTEXT DATE
ASSOCIATED CONTEXT FORMAT
- File Type
- Decoding Instructions
SEGMENTS
- Associated Segment Position
- Internal File Reference Pointer
- Number of Points
- Horizontal Point Offset 11
- Vertical Point Offset
TIME INDEX
- Time Index Start
- Time Index End
COMMENT
ASSOCIATED CONTEXT NUMBER
USER DEFINED FIELDS
ANNOTATION INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
Min
Occ.
1
1
1
0
1
Max
Occ.
1
1
1
1
1
0
99
0
99
0
1
N/A
1
1
N/A
0
Unlimited ANN
- GMT
- NAV
- OWN
- PRO
11
Mnemonic
LEN (Used only in traditional encoding version)
IDC
SRC
ACD
AFT
- FTY
- DEI
SEG
- ASP
- IPT
- NOP
- HPO
- VPO
TIX
- TIS
- TIE
COM
ACN
UDF
The Horizontal and Vertical Point Offset information items are repeated as pairs, in order by point following the contour, up to the final point – for a total
of NOP pairs
Page 70 of 79
Electronic Biometric Transmission Specification Version 3.0
Field
Number
21.993
21.994
21.996
21.998
21.999
DIN: BIMA-STB-STD-11-001
Field Name
SOURCE AGENCY NAME
EXTERNAL FILE REFERENCE
HASH
GEOGRAPHIC SAMPLE ACQUISITION LOCATION
- (See ITL 1-2011 for Informational Items)
ASSOCIATED CONTEXT DATA
Min
Occ.
0
0
0
0
Max
Occ.
1
1
1
1
Mnemonic
0
1
DATA
Page 71 of 79
SAN
EFR
HAS
GEO
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.12 Type-98 Record [Information Assurance Record]
DoD EBTS Type-98 records are completely defined in ITL 1-2011. New to this version of the standard,
the Type-98 record shall contain security information that assures the authenticity and/or integrity of the
transaction, possibly utilizing such techniques as binary data hashes, and/or digital signatures.
Page 72 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 15: Type-98 Infor mation Assur ance Recor d Layout
Field
Number
98.001
Field Name
98.002
98.003
98.004
98.005
98.006
98.200 –
98.889
98.900
98.901
98.993
RECORD HEADER
Min
Occ.
1
Max
Occ.
1
INFORMATION DESIGNATION CHARACTER
IA DATA FORMAT OWNER
SOURCE AGENCY
IA DATA FORMAT TYPE
IA DATA CREATION DATE
USER DEFINED FIELDS
1
1
1
1
1
N/A
1
1
1
1
1
N/A
AUDIT LOG
- Event
- Event Reason
- Information Identifier
- Agent
- Old Reference
AUDIT REVISION NUMBER
ORIGINATING AGENCY NAME
0
Unlimited ALF
- EVT
- EVR
- IID
- AGT
- OLD
1
ARN
1
SAN
1
0
Page 73 of 79
IDD element
RECORD HEADER
[TYPE-21]
IDC
DFO
SRC
DFT
DCD
UDF
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
4.13 Type-99 Records [CBEFF Biometric Data Record]
DoD EBTS Type-99 records are completely defined in ITL 1-2011. The Type-99 record shall contain
and be used to exchange biometric data that is not supported by other ANSI/NIST-ITL records. This
data is exchanged in a format that conforms to INCITS 398-2005, the Common Biometric Exchange
Formats Framework.
Page 74 of 79
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
Table 16: Type-99 CBEFF Biometr ic Data Recor d Layout
Field
Number
99.001
99.002
99.004
99.005
99.100
99.101
99.102
99.103
99.104
99.200 –
99.900
99.902
99.903
99.904
99.993
99.995
Field Name
RECORD HEADER
INFORMATION DESIGNATION CHARACTER
SOURCE AGENCY
BIOMETRIC CAPTURE DATE
CBEFF HEADER VERSION
BIOMETRIC TYPE
BIOMETRIC DATA QUALITY
- Quality Value
- Algorithm Vendor Identification
- Algorithm Product Identification
BDB FORMAT OWNER
BDB FORMAT TYPE
USER DEFINED FIELDS
ANNOTATED INFORMATION
- Greenwich Mean Time
- Processing Algorithm Name/Version
- Algorithm Owner
- Process Description
DEVICE UNIQUE IDENTIFIER
MAKE/MODEL/SERIAL NUMBER
- Make
- Model
- Serial Number
SOURCE AGENCY NAME
ASSOCIATED CONTEXT
- Associated Context Number
- Associated Segment Position
Min
Occ.
1
1
1
1
1
1
0
Max
Occ.
1
1
1
1
1
1
1
1
1
N/A
1
1
N/A
0
Mnemonic
IDC
SRC
BCD
HDV
BTY
BIOMETRIC DATA QUALITY
- QVU
- QAV
- QAP
BFO
BFT
UDF
Unlimited ANN
- GMT
- NAV
- OWN
- PRO
0
1
DUI
0
1
MMS
- MAK
- MOD
- SER
0
1
SAN
0
255
ASC
- ACN
- ASP
Page 75 of 79
Electronic Biometric Transmission Specification Version 3.0
Field
Number
99.996
99.997
99.998
99.999
Field Name
HASH
SOURCE REPRESENTATION
- Source Representation Number
- Reference Segment Position
GEOGRAPHIC SAMPLE ACQUISITION LOCATION
- (See ITL 1-2011 for Informational Items)
BIOMETRIC DATA BLOCK
DIN: BIMA-STB-STD-11-001
Min
Occ.
0
0
Max
Occ.
1
255
0
1
HAS
SOR
- SRN
- RSP
GEO
1
1
DATA
Page 76 of 79
Mnemonic
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
APPENDIX A: CHANGE REQUEST TEMPLATE
Department of Defense Electronic Biometric Transmission Specification Change Request (CR)
Submission Form
The following template should be used for all Change Requests submitted to the BIMA Standards
Branch regarding EBTS development (Refer to Section 1.5 for contact information). For detailed
instructions, please refer to the DoD BIMA EBTS CR Standard Operating Procedure.
Submission Date
Originator Organization
Originator Point of Contact
Originator E-mail
Originator Phone
Originator Fax (optional)
Originator Address
(optional)
CR Description of issue to
be resolved
Associated requirement,
mandate, or policy for the
change
Page 77 of 79
Electronic Biometric Transmission Specification Version 3.0
System(s) affected by the
issue
DIN: BIMA-STB-STD-11-001
CR Criticality
CR Criticality Justification
Proposed solution set
Emergency
Critical
Non-critical
CR Type
Editorial change
Minor Technical
Major Technical
New Functionality
Other
If Other, explain:
Audit Flow:
Assign Change Control
Number:
Date
Page 78 of 79
Action
Organization
Electronic Biometric Transmission Specification Version 3.0
DIN: BIMA-STB-STD-11-001
This page intentionally left blank
Page 79 of 79
| File Type | application/pdf |
| File Title | DOD Electronic Biometrics Transmission Specification |
| File Modified | 2014-05-28 |
| File Created | 2011-12-07 |