ANSI/NIST-ITL 1-2000/6 and EFTS

Overview and Relationship to BIAS

2

Introduction ANSI/NIST-ITL 1-2000: Data Format for the Interchange of

Fingerprint, Facial, & Scar Mark & Tattoo (SMT) Information An approved ANSI standard for describing the fingerprint data

interchange format used by Law Enforcement agencies (e.g., FBI, State and Local Police)

Currently being updated with a number of changes, including an XML representation.

This update, commonly referred to as ANSI/NIST-ITL 1-2006, has not yet been approved. A proposed draft is currently in review.

EFTS: Electronic Fingerprint Transmission Specification A specific implementation of the ANSI/NIST-ITL 1-2000 standard,

describing how to communicate with the FBI IAFIS. Will be updated to reflect changes in ANSI/NIST-ITL 1-2006 and

renamed to EBTS: Electronic Biometric Transmission Specification.

3

ANSI/NIST-ITL 1-2000 Defines 16 record types for exchanging various pieces of

information (Logical Records): Transaction itself (Type-1) Demographic/Rap sheet (Type-2) Fingerprint and Palm Print images and fingerprint minutiae

Low/High resolution grayscale fingerprint image (Type-3/4) Low/High resolution binary fingerprint image (Type-5/6) User-defined image (Type-7) Fingerprint minutiae (Type-9) Variable resolution latent image (Type-13) Variable resolution tenprint image (Type-14) Variable resolution palm print image (Type-15)

Signature images (Type-8) Facial images (Type-10) SMT images and descriptive details (Type-10)

4

ANSI/NIST-ITL 1-2000 A transaction file is composed of one or more logical records The logical records utilize either tagged fields or fixed-length binary

fields Logical records and information in the tagged-field records are delimited

by separator characters:

ASCII Character Description

FS Separates logical records of a file or is the terminating character of a transaction.

GS Separates fields of a logical record

RS Separates multiple data entries (subfields) of an information field

US Separates individual information items of the field or subfield

5

ANSI/NIST-ITL 1-2000 Type-1 RecordIdentifier Condition

CodeField

NumberField Name Character

Type

LEN Mandatory 1.001 Logical Record Length Numeric

VER Mandatory 1.002 Version Number Numeric

CNT Mandatory 1.003 File Content Numeric

TOT Mandatory 1.004 Type of Transaction Alphanumeric

DAT Mandatory 1.005 Date Numeric

PRY Optional 1.006 Priority Numeric

DAI Mandatory 1.007 Destination Agency Identifier Alphanumeric

ORI Mandatory 1.008 Originating Agency Identifier Alphanumeric

TCN Mandatory 1.009 Transaction Control Number Alphanumeric

TCR Conditional 1.010 Transaction Control Reference Alphanumeric

NSR Mandatory 1.011 Native Scanning Resolution Numeric

NTR Mandatory 1.012 Nominal Transmitting Resolution Numeric

DOM Optional 1.013 Domain Name Alphanumeric

GMT Optional 1.014 Greenwich Mean Time Alphanumeric

DCS Optional 1.015 Directory of Character Sets Alphanumeric

6

ANSI/NIST-ITL 1-2000 Type-1 Example The following example shows a Type-1 tagged-field logical

record, which describes a TEST transaction from SENDER to RECEIVER with a transaction control number of TCN001 sent on November 1, 2006

1.001:127G

S1.002:0300GS1.003:1U

S1RS2U

S00GS1.004:T

ESTGS1.005:20061101G

S1.006:1GS1.007:RECEIVERG

S1.008:SENDERG

S1.009:TCN001GS1.011:0G

S1.012:0FS

7

ANSI/NIST-ITL 1-2000 Type-2 RecordIdentifier Condition

CodeField

NumberField Name Character

Type

LEN Mandatory 2.001 Logical Record Length Numeric

IDC Mandatory 2.002 Image Designation Character Numeric

UDF Optional 2.003 – 2.999

User Defined Fields --

8

ANSI/NIST-ITL 1-2000 Type-4 RecordIdentifier Condition

CodeField

NumberField Name Character

Type

LEN Mandatory -- Logical Record Length Numeric

VER Mandatory -- Version Number Numeric

IMP Mandatory -- Impression Type Numeric

FGP Mandatory -- Finger Position Numeric

ISR Mandatory -- Image Scanning Resolution Numeric

HLL Mandatory -- Horizontal Line Length Numeric

VLL Mandatory -- Vertical Line Length Numeric

GCA Mandatory -- Grayscale Compression Algorithm Numeric

DAT Mandatory -- Image Data Binary

9

ANSI/NIST-ITL 1-2000 Type-14 RecordIdentifier Condition Code Field Number Field Name Character Type

LEN Mandatory 14.001 Logical Record Length Numeric

IDC Mandatory 14.002 Image Designation Character Numeric

IMP Mandatory 14.003 Impression Type Alphabetic

SRC Mandatory 14.004 Source Agency / ORI Alphanumeric

TCD Mandatory 14.005 Tenprint Capture Date Numeric

HLL Mandatory 14.006 Horizontal Line Length Numeric

VLL Mandatory 14.007 Vertical Line Length Numeric

SLC Mandatory 14.008 Scale Units Numeric

HPS Mandatory 14.009 Horizontal Pixel Scale Numeric

VPS Mandatory 14.010 Vertical Pixel Scale Numeric

CGA Mandatory 14.011 Compression Algorithm Alphabetic

BPX Mandatory 14.012 Bits Per Pixel Numeric

FGP Mandatory 14.013 Finger Position Numeric

COM Optional 14.020 Comment Alphanumeric

UDF Optional 14.200 – 14.998 User-Defined Fields --

DAT Mandatory 14.999 Image Data Binary

10

ANSI/NIST-ITL 1-2006 Changes Includes an XML representation of the standard

Base-64 encoding of binary image data Global Justice XML Data Model (GJXDM) objects used when

available Adds a logical record for iris images (Type-17) Adds a logical record for other biometrics [CBEFF-encoded]

(Type-99) Harmonizes minutiae record (Type-9) with INCITS 378 Substantially changes the facial record (Type-10) Provides specifications for “identification flat” data (Type-14) Adds image quality information to various logical records

11

ANSI/NIST-ITL 1-2006 Timeline Proposed draft recently posted at

http://fingerprint.nist.gov/standard Comments are due by November 27, 2006 Updated draft will be canvassed (balloted) in December Assuming approval, draft will be submitted to ANSI for

finalization in 1Q 2007 Will probably be called ANSI/NIST-ITL 1-2007

12

ANSI/NIST-ITL Relationship to BIAS Although in a different format, ANSI/NIST-ITL 1-2000/6

transaction files could be translated to BIAS services ANSI/NIST-ITL 1-2000/6 does not describe any specific transaction

types, so specific mappings cannot be provided ANSI/NIST-ITL 1-2000/6 biometric data representations can

be mapped to the proposed BIAS biometric data representation, which uses CBEFF

Format types for ANSI/NIST-ITL 1-2000 records have been defined (Reference: INCITS M1 Standing Document SD2, http://www.incits.org/tc_home/m1htm/2006docs/m1060018.htm)

The ANSI/NIST-ITL Type-99 record specifies a CBEFF patron format

13

EFTS Defines the transactions and their required logical

records/fields for communicating with the FBI IAFIS Extends/customizes/implements the ANSI/NIST-ITL 1-2000 standard Example: Criminal Ten-Print Submission (Answer Required)

Type of Transaction: CAR Logical Record Requirements: one Type-1, one Type-2, zero to four

Type-10, and fourteen Type-4

Defines Type-2 fields for use with EFTS transactions (examples follow on next slide)

Sets other requirements/specifications, such as: Minimum image quality specifications Allowed image compression techniques

14

EFTS – Example Type-2 FieldsIdentifier Field

NumberField Name Character Type

SOC 2.016 Social Security Account Number Numeric

NAM 2.018 Name Alphanumeric with Special Characters

CTZ 2.021 Country of Citizenship Alphabetic

DOB 2.022 Date of Birth Numeric

SEX 2.024 Sex Alphabetic

RAC 2.025 Race Alphabetic

HGT 2.027 Height Alphanumeric

WGT 2.029 Weight Numeric

EYE 2.031 Color Eyes Alphabetic

HAI 2.032 Hair Color Alphabetic

RES 2.041 Residence of Person Fingerprinted Alphanumeric with Special Characters

DOA 2.045 Date of Arrest Numeric

15

EFTS Relationship to BIAS EFTS transaction types can be mapped to BIAS services

(see following slide) EFTS Type-2 records (demographic data) can be utilized in

the BIAS biographic representation as-is No differences from ANSI/NIST-ITL 1-2000/6 for the

biometric data mapping

16

EFTS Transactions => BIAS ServicesEFTS Transaction Related BIAS Services

Electronic Ten-Print Submissions (CAR – Retain, CAN, DEU, MPR, AMN) Enroll

Electronic Ten-Print Submissions (CAR – Non-Retain) Identify

Electronic Ten-Print Submissions (DEK) Verify

Electronic Ten-Print Submissions (FANC, FAUF, NFAP, NFUF, MAP) Enroll or Identify, depending

Remote Ten-Print Searches (TPIS, TPFS, TPRS) Identify

Electronic Submission of Latent Prints (LFS) Enroll (ULF=“Y”)

Identify (no ULF specified)

Remote Latent Fingerprint Searches (LFIS, LFFS) Enroll (ULF=“Y”)

Identify (no ULF specified)

Remote Latent Fingerprint Searches (LPNQ) No related BIAS Service

Latent File Maintenance Requests (ULD) Delete Subject

Latent File Maintenance Requests (ULAC) Uncertain of mapping

Remote Requests for Fingerprint Images (IRQ) Retrieve Information

Electronic Requests to Upgrade Fingerprint Images (FIS) Update Biometric Data

Electronic Criminal Subject Photo Services (CPR) Retrieve Information

Electronic Criminal Subject Photo Services (CPD) No related BIAS Service

Latent Administrative Queries, Requests, and Responses (LRSQ, LSMQ) No related BIAS Service