ansi nist csl1-1993pdf | nist

for Information Systems -Data Formatfor the Interchangeof Fingerprint Information

•••••••••• ......-ee-IV~I American National Standards Institute

11 West 42nd StreetNew York, New York

10036

ANSI/NIST-CSl1-1993Revision of

ANSIINBS-ICST 1-1986

American National Standardfor Information Systems-

Data Format for the Interchange ofFingerprint Information

Sponsor

National Institute of Standards and Technology

Approved November 22, 1993

American National Standards Institute, Inc.

American Approval of an American National Standard requires verification by ANSIthat the requirements for due process, consensus, and other criteria for

National approval have been met by the standards developer.Consensus is established when, in the judgment of the ANSI Board of

Standard Standards Review, substantial agreement has been reached by directlyand materially affected interests. Substantial agreement means much morethan a simple majority, but not necessarily unanimity. Consensus requiresthat all views and objections be considered. and that a concerted effort bemade toward their resolution.

The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not. from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.

The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should be ad-dressed to the secretariat or sponsor whose name appears on the title pageof this standard.

CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.

Any organization interested in reproducing ANSI/NIST-CSl 1-1993. Data Format for the Interchange ofFingerprint Information, in whole or in part, is free to do so. However, all such organizations are asked to submit written reprint requests to ANSI and to include the following acknowledgment in the reprinted material:

This material is reproduced with permission from American National Standard ANSIINIST-CSL 1. DataFormat for the Interchange of Fingerprint Information, copyright 1994 by the American National StandardsInstitute. Copies of this standard may be purchased from the American National Standards Institute. 11 West42nd Street, New York, NY 10036.

Requests for reproduction permission should be directed to ANSI Publications Department, 11 West 42ndStreet. New York. NY 10036. Reproduction permission will be granted by ANSI free of charge.

American National Standards Institute11 West 42nd Street, New York, New York 10036

Copyright © 1994 by American National Standards InstituteAll rights reserved.

No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of the publisher.

-

PageForeword iii

1 Scope, purpose, and application 1

1.1 Scope 1

1.2 Purpose 1

1.3 Application 1

2 Normative references 1

3 Definitions 2

4 Transmitted data conventions 2

4.1 Byte and bit ordering 2

4.2 Grayscale data 2

4.3 Binary data 2

4.4 Scan sequence 3

5 Image resolution requirements 3

5.1 Scanner resolution requirement.. 3

5.2 Transmitting resolution requirement 3

6 File description 4

6.1 File format 4

6.2 File contents 4

6.3 Image designation character (IDC) 5

7 Record description 5

7.1 Logical record types 5

7.2 Record format. 7

8 Type-1 transaction record 8

8.1 Fields for Type-1 transaction record 8

8.2 End of Type-1 logical record 10

9 Type-2 user-defined text record 10

9.1 Fields for Type-2 logical records 10


10 Type-3 low resolution grayscale image record 10

10.1 Fields for Type-310gical record 10

10.2 End of Type-310gical record , 12

10.3 Additional low-resolution grayscale images 12

11 Type-4 high-resolution grayscale image record 12

11.1 Fields for Type-4 logical record 12

11.2 End of Type 4 logical record 13

11.3 Additional high resolution grayscale images 13

-

-

-

Type-5 low resolution binary image record 13

12.1 Fields for Type 5 logical record 13

12.2 End of Type-510gical record 14

12.3 Additional low-resolution binary images 14

13 Type-6 high-resolution binary image record 14



13.3 Additional high resolution binary images 15

14 Type-7 user-defined image record 15


14.2 End of Type 710gical record 16

14.3 Additional user defined image records 16

15 Type-8 signature image record 16

15.1 Fields for Type-8 logical record 16

15.2 End of Type 8 logical record 17

15.3 Additional sig nature 17

16 Type-9 minutiae record 18

16.1 Fingerprint information descriptors , 18


16.3 End of Type-9 logical record :0. ••••••••••••••••••••••••••••••••••••••••••••••• 21

16.4 Additional minutiae records 21

17 Another individual 21

Tables

1 Logical record types 4

2 Number of logical records per transaction 5

3 Information separators 7

4 Impression type 11

5 Finger position code and maximum size 11

6 Minutia types 18

7 Pattern classification 20

Figures

1 Byte and bit ordering 3

2 Minutia coordinate system 19

AnnexesA ANSI code for information interchange 22

8 Use of information separator characters 23

C An example of the use of the standard 24

-

-

-

-

-

-

-

-

~

-

Foreword (This foreword is not part of American National Standard ANSIINIST-CSL 1-1993.)

Federal, state, and local law enforcement and related criminal justiceagencies have procured or are in the process of procuring AutomatedFingerprint Identification Systems (AFISs), live scan fingerprint readers,and/or Image Storage and Retrieval (ISR) systems intended to facilitatethe determination of the personal identity of a subject.

AFISs scan and store digital representations of fingerprint images frominked fingerprint cards. Live-scan readers scan the fingerprint image datadirectly from the sUbject's fingers. The scanned images are then processedto extract specific types of features from the images. Features from thescanned images are then compared against a masterfile containing fea-tures extracted from previously scanned images. The result of these com-parisons is a list of potential candidate identifications. The actual identification is then made by a human examiner using images retrieved from thesystem or fingerprint cards.

To exchange fingerprint identification data effectively across jurisdictional.tines or between dissimilar systems made by different manufacturers, a stan-dard is needed to specify a common format for the data exchange. The datamay be scanned images or the processed minutiae extracted by the system.

The Computer Systems Laboratory (CSL) of the National Institute ofStandards and Technology (NIST) sponsored the development of this stan-dard using the Canvass Method to demonstrate evidence of consensus.

This standard contains three annexes. Annex A is normative and is considered part of the standard; Annexes Band C are informative and are notconsidered part of the standard.

Suggestions for the improvement of this standard will be welcome. Theyshould be sent to the attention of Fingerprint Standards, Data StorageGroup, NIST, Building 225, Room A61, Gaithersburg, MD 20899.

The follOWing organizations recognized as having an interest in the stan-dardization of the data format for the interchange of fingerprint informationwere contacted prior to the approval of this revision of the standard.Inclusion in this list does not necessarily imply that the organization con-curred with the submittal of the proposed standard to ANSI.

Abilene Police DepartmentAFR ConsortiumAIMS, Inc.Ann Arbor Police DepartmentArizona Department of Public SafetyAware, Inc.Banner, Conrad S. (Consultant)Bureau of Alcohol. Tobacco and FirearmsCAI/SISCOCalifornia Department of Motor VehiclesCalifornia State Department of JusticeCalspan CorporationCharleston Police DepartmentChicago Police DepartmentCincinnati Regional Crime Information

CenterCity of Austin (TX) Police DepartmentColorado Bureau of InvestigationComnetix Computer Systems, Inc.

Concepts, Models, & SolutionsConnecticut State PoliceDallas Police DepartmentDefense Investigative ServiceDelaware State PoliceDERMALOG AFIS GMBHDetroit Police Identification SectionDigital Biometrics. Inc.Drug Enforcement AdministrationEKTRON Applied ImagingFederal Bureau of InvestigationFederal Bureau of PrisonsFingermatrix, Inc.Florida Department of Law EnforcementGeorgia Bureau of Investigation AFIS

Oper2tionsGlendale Police DepartmentGrumm2n Data SystemsGTE Feceral Systems Division

-

-

-

-

Houston Police DepartmentHughes Information Technology CompanyIBM Federal Sector DivisionIdenticator CorporationIDENTIX, Inc.Illinois State PoliceImmigration & Naturalization ServiceInset Systems. Inc.Internal Revenue ServiceInternational Association for IdentificationIndianapolis Police DepartmentKentucky State PoliceKing County (Washington) PoliceLakewood Colorado Police DepartmentLogiconLos Angeles County Sheriff s DepartmentLos Angeles Police DepartmentManchester Missouri Police DepartmentMartin Marietta Energy SystemsMaryland State Police Crime LaboratoryMetro Toronto PoliceMiami Valley Regional Crime Laborato.ryMichigan State PoliceMinnesota Department of Public SafetyMissouri State Highway PatrolMITRE CorporationMoore AssociatesNational Conference of Appellate Court

ClerksNEC Technologies, Inc.New Jersey State PoliceNew York State Division of Criminal

Justice ServicesNorth American MORPHO Systems. Inc.North Carolina State Bureau of

Investigation

Northover, Kevin (Consultant)NoVARIS Northern VA Regional

Identification SystemOptivision, Inc.Peel Regional PolicePennsylvania State PolicePinellas County Sheriff s OfficePRC,lncPrintrak International, Inc.Productivity, Inc.ROC ConsultingRiverside Sheriff's DepartmentRobert Stock AssociatesRoyal Canadian Mounted PoliceRoyal Oman PoliceSAIC Science Applications International

CorporationSEARCH Group, Inc.Shelburne Police DepartmentSiemens Nixdorf Information Systems,

Inc.Soft Information, Inc.St. louis Regional Justice Information

ServiceState of AlaskaSunnyvale Department of Public SafetyTacoma Police DepartmentTASCTexas Department of Public SafetyTRW Systems Integration GroupU.K. Home OfficeU.S. Postal Inspection ServiceVirginia State PoliceWashington State PatrolWestern Identification NetworkXlmage Corporation

-

'

' -

American National Standardfor Information Systems-

Data Format for the Interchange ofFingerprint Information

1.1 Scope

This standard defines the content, format, andunits of measurement for the exchange ofinformation that may be used in the fingerprintidentification of a sUbject. The informationconsists of a variety of mandatory and option-al items, including related record data, digi-tized fingerprint information, and compressedor uncompressed images. This information isintended for interchange between criminal jus-tice administrations or organizations that useautomated fingerprint identification systems.

This standard does not define the characteris-tics of the software that shall be required toformat the textual information or to compressand assemble the associated digital finger-print image information. Typical applicationsfor this software might include, but are notlimited to, computer systems associated witha live-scan fingerprinting system, a worksta-tion that is part of an Automated FingerprintIdentification System (AFIS), or an ImageStorage and Retrieval system.

1.2 Purpose

Information compiled and formatted in accor-dance with this standard can be recorded onmachine-readable media and may be trans-mitted over data communications facilities inlieu of a fingerprint card or a latent fingerprint.law enforcement and criminal justice agen-cies may use it to exchange fingerprintimages and related identification data.

1.3 Application

Systems claiming conformance with this standard shall be capable of transmitting andreceiving Type-1 records and shall 'specifywhich other record types are implemented fortransmitting, or receiving, or both. Recordtypes not implemented shall be ignored.

The following standards contain provisionswhich, through reference in this text, constituteprovisions of this American National Standard.At the time of publication, the editions indicatedwere valid. All standardsare sUbjectto revision,and parties to agreements based on thisAmerican National Standard are encouraged toinvestigate the possibility of applying the mostrecent editions of the standards indicatedbelow.

ANSI X3.4-1986(R1992), Information systemsCoded character sets 7-8it American

National Standard Code for InformationInterchange (7-bit ASCII)

ANSI X3.172-1990, Information systemsDictionary for information systems

ANSI/EIA 538-1988, Facsimile codingschemes and coding control functions forgroup 4 facsimile equipment

ANSIIIAI 2-1988, Forensic identificationAutomated fingerprint identification systemsGlossary of terms and acronyms

ISO 646-1983, 7-bit coded character set forinformation interchange1)

- -

-

-

--

ISO 8601-1988, Data elements and inter-change formats Information interchangeRepresentation of dates and times1)

National Crime Information Center (NCIC)Code Manua/2)

The following definitions and those given inANSI/IAI 2 apply to this standard.

3.1 ANSI: Abbreviation for the AmericanNational Standards Institute, Inc.

3.2 logical record: A record independent ofits physical environment; portions of one logi-cal record may be located in different physicalrecords, or several logical records or parts oflogical records may be located in one physicalrecord.

3.3 native scanning resolution: The nomi-nal scanning resolution used by a specificAFIS. live-scan reader, or other image cap-ture device and supported by the originator ofthe transmission.

3.4 p/ln: Abbreviation for pixels per inch.

3.5 p/mm: Abbreviation for pixels per millimeter.

3.6 scanning resolution: The number ofpixels per unit distance at which an image iscaptured (p/mm or p/in).

3.7 transaction: A command, message, orinput record that explicitly or implicitly calls fora processing action.

3.8 transmitting resolution: The nominalnumber of pixels per unit distance (p/mm orp/in) of the transmitted image. The transmit-ting resolution may be the same as the scan-ning resolution for a particular image. On theother hand, the transmitting resolution may beless than the scanning resolution if thescanned image was subsampled, scaled, orinterpolated before transmission.

4.1 Byte and bit ordering

Each information item, subfield, field, and log-ical record will contain one or more bytes ofdata. Within a file, the order for transmissionof both the ASCII and the binary representa-tions of bytes shall be most significant bytefirst and least significant byte last. Within abyte, the order of transmission shall be themost significant bit first and the least signifi-cant bit last. Figure 1 illustrates the order oftransmission of the bytes and bits within a file.

4.2 Grayscale data

Grayscale image data may be transmitted ineither compressed or uncompressed form.

The transmission of uncompressed grayscaleimages shall consist of pixels each of whichshall be quantized to eight bits (256 gray lev-els) and shall be contained in a single byte.Each grayscale value shall be expressed asan unsigned byte. A value of 0 shall be usedto define a black pixel and a value of 255shall be used to define a white pixel.

The transmission of compressed grayscaleimages shall be the output of the appropriategrayscale compression algorithm specified.Upon decompression each pixel shall be considered as an unsigned eight-bit grayscalevalue. A black pixel shall have a value of zeroand a white pixel a value of 255.

4.3 Binary data

Binary image data may be transmitted ineither compressed or uncompressed form.

The transmission of uncompressed binaryimages shall consist of pixels, each of whichshall be quantized to two levels (binary repre-sentation). A value of 0 shall be used to rep-resent a white pixel and a value of 1 shall beused to represent a black pixel. For transmis-sion of uncompressed binary images, eightpixels shall be left-justified and packed into asingle unsigned byte. The most significant bitof the byte shall be the first of the eight pixelsscanned.

2) Available from the U.S. Department of Justice, Federal Bureau of Investigation, 10th Street andPennsylvania Avenue, NW, Washington, DC 20535.

- -

--

~ 1 F_ir_st_B_y_t_e_

MostSignificant

Bit

LeastSignificant

Bit

The transmission of compressed binaryimages shall be the output of the binary com-pression algorithm specified by ANSI/EIA 538.Upon decompression. each pixel with a valueof 0 shall be considered to be white and eachpixel with a value of one shall be consideredto be black.

4.4 Scan sequence

For each binary or grayscale image scannedand formatted, the transmitted scan sequenceshall be assumed to have been left to rightand top to bottom.

5.1 Scanner resolution requirement

Binary and grayscale fingerprint images to beexchanged shall be captured by an AFIS, Iive-scan reader, or other image capture deviceoperating at a specific nominal scanning reso-lution. The minimum scanning resolution forthis capture process shall be 19.69 p/mm± 0.20 p/mm (500 p/in ± 5 p/in). Although aminimum scanning resolution is specified. amaximum value for scanning resolution is notspecified by this standard. Scanning resolu-tions greater than this minimum value and witha tolerance of ±1% may be used.

5.2 Transmitting resolution requirement

Each image to be exchanged shall have aspecific resolution associated with the trans-

mitted data. This transmitting resolution doesnot have to be the same as the scanning res-olution. However. the transmitting resolutionshall be within the range of permissible valuesfor the high-resolution or the low-resolutionimages. When an image is captured at ascanning resolution greater than the permissible upper limit of the transmitting resolutionfor that record type, the image shall be sub-sampled. scaled, or interpolated downward.This processing to produce a resultant resolu-tion within the limits of the permissible trans-mitting resolutions for that record type shallbe accomplished before transmission occurs.

For high-resolution binary and grayscaleimages, the preferred transmitting resolutionshall be the same as the minimum scanningresolution of 19.69 p/mm ± 0.20 p/mm (500p/in ± 5 p/in). However, any transmitting reso-lution within the range from the minimumscanning resolution to a value of 20.47 p/mm± 0.20 p/mm (520 p/in ± 5 p/in) is permitted.

For low-resolution binary and grayscaleimages. the preferred transmitting resolutionshall be half of the minimum scanning resolution or 9.84 p/mm ± 0.10 p/mm (250 p/in ± 2.5p/in). However, any transmitting resolutionwithin the range from half of the minimumscanning resolution to a value of 10.24 p/mm± 0.10 p/mm (260 p/in ± 2.5 p/in) is permitted.

NOTE Although the value of the transmittingresolution for high-resolution fingerprint imagesmay range from 19.69 to 20.47 p/mm, any valueother than the preferred resolution may require

~

-

-

-

Logical record contents Type identifier

Transaction information 1

Descriptive text (user-defined) 2

Fingerprint image data 3(low-resolution grayscale)

Fingerprint image data 4(high-resolution grayscale)

Fingerprint image data 5(low-resolution binary)

Fingerprint image data 6(high-resolution binary)

Image data (user-defined) 7

Signature image data 8

Minutiae data 9

special processing for the classification andmatching tasks. Therefore. it is recommendedthat if the transm itting resolution is greater than19.69 p/mm. prior approval be obtained from therecipient agency or organization before transmis-sion of the image occurs. A similar situation existswhen low-resolution images are transmitted usinga transmitting resolution of greater than the pre-ferred transmitting resolution of 9.84 p/mm.

This standard defines the composition of a fileto be transmitted to an agency. As specified inthis standard, certain portions of the transmis-sion shall be in accordance with definitionsprovided by the receiving agency. This fileshall contain one or more logical records,each corresponding to one of the nine avail-able types of logical records. Each logicalrecord is intended to convey a specific type ofrelated information pertinent to the transactionitself or to the subject of the transaction.

Three of the logical records are designed toexchange ASCII information, while theremaining six contain binary data. The ninedifferent types of logical records together withthe identifier for each type are listed in table1, Logical record types.

6.1 File format

A file shall contain all of the logical records fora single subject. The data in Type-1, Type-2,and Type-9 records shall be recorded in vari-able-length fields using the 7-bit AmericanNational Standard Code for InformationInterchange (ASCII) as described in ANSIX3.4 and annex A. For purposes of futurecompatibility, the eighth (leftmost) bit shallhave a value of zero. Most of these variable-length fields have a specified upper limit onsize. For each Type-1, Type-2, and Type-9record that is formulated, the fields containedwithin that record shall be numericallyordered. The content and order of the fields inType-3, Type-4, Type-5. Type-G, Type-7, andType-8 records are specified by this standard.These data shall be encoded and recorded asbinary numbers.

6.2 File contents

Files to be exchanged shall always contain aType-1 logical record that shall always be thefirst logical record within the file. Dependingon the usage, the number of fingerprints avail-able for processing, and the options that areselected, one or more additional records shallbe present in the file. Table 2. Number of logical record types per transaction, lists therange or the number of records that may be

-

Type of Ten- File Imagelogical print Latent maint- Image Search requestrecord inquiry inquiry enance request response response

1 1 1 1 1 1 12 1 0-1 0-1 1 1 13 0-14 0 0-14 0 0-14 0-144 0-14 0-10 0-14 0 0-14 0 145 0-14 0 0-14 0 0-14 0-146 0-14 0-10 0-14 0 0-14 0-147 0 O-N O-N 0 O-N O-N8 0-2 0 0-2 0 0-2 0-29 0-10 0-10 0-10 0 0 0

present in a file. These record counts areshown by logical record types and by the pro-cessing functions used for search inquiries,file maintenance, image request, and imageresponses.The ranges listed specify the mini-mum and maximum number of logical recordsthat may be contained in the file. The manda-tory inclusion of a logical record is indicatedby an entry of "1" in table 2. An entry of "0"indicates the exclusion of that logical recordtype. The appearance of "O-N" in table 2 indi-cates that there are no limits on the number ofrecords of that logical record type that may becontained in the file.

6.3 Image designation character (IDC)

With the exception of the Type-1 logicalrecord, each of the remaining logical recordspresent in a file shall include a separate fieldto contain the Image Designation Character(IDC). This IDC shall be used to relate infor-mation items in the file contents field of theType-1 record to each logical record, and toproperly identify and link together logicalrecords that pertain to the same image. Thevalue of the IDC shall be a sequentiallyassigned positive integer starting from zeroand incremented by one. If two or more logi-cal records are present in a file that are differ-ent representations of the same image, eachof those logical records shall contain thesame IDC.

Althoughthere is no upper limit on the numberof logical records that may be contained in a

file, a minimumof two, and generally no morethan 18 will be transmitted. A ten-print searchinquiry may consist of a Type-1 record. aType-2 record, 14 high-resolution grayscaleimage records, and two Type-8 records. TheIDC included in each image record shall relateto a single image on the ten-print card. TheIDC shall range from "0" to "17." which wouldinclude an IDC code for the Type-2 record.Within the same file, it is also possible that thesame image may be represented by multiplelogical record types. For example. if core anddelta location information for the rolled impres-sions is requested, the transmission may alsoneed to accommodate ten Type-9 recordswithin the samefile. For each image represent-ing the ten finger positions, the same IDCwould be used in both the Type-4 and Type-9recordspresentfor that image.

Furthermore. zero or more Type-7 recordsmay also be present. Each Type-7 logicalrecord representing a unique image shallhave a unique IDC.

7.1 Logical record types

7.1.1 Type-1 transaction record

A Type-1 logical record is mandatory andshall be used with each transaction. TheType-1 record shall provide informationdescribing type and use of transaction

-

·

involved, a listing of each logical recordincluded in the file, the originator or source ofthe physical record, and other useful andrequired information items.

7.1.2 Type-2 user-defined text record

Type-2 logical records shall contain user-defined fields providing identification anddescriptive information about the subject ofthe fingerprint information.

7.1.3 Type-3 low-resolution grayscale record

Type-3 logical records shall contain, and beused to exchange low-resolution grayscale fin-gerprint image data that was scanned at noless than the minimum scanning resolution andthen subsampled, scaled, or interpolated. Theresultant transmitting resolution shall be withinthe bounds of the permissible transmitting resolutions for low resolution fingerprint images.

The low-resolution grayscale fingerprint imagedata contained in the Type-3 logical recordmay be in compressed form. There may be upto 14 of these Type-3 records in a file; tenrolled impressions of the individual fingers,two plain impressions of the thumbs and twoplain impressions of the four simultaneouslyobtained remaining fingers of each hand.

7.1.4 Type 4 high-resolution grayscale record

Type-4 logical records shall contain, and beused to exchange high-resolution grayscalefingerprint image data that was scanned at noless than the minimum scanning resolution. Ifthe scanning resolution is greater than theupper limit of the permissible transmitting res-olution, the scanned data shall be subsam-pled, scaled, or interpolated. The resultanttransmitting resolution shal.l be within thebounds of the permissible transmitting resolu-tions for high-resolution fingerprint images.

The high-resolution grayscale fingerprint imagedata contained in the Type-4 logical recordmay be in compressed form. There may be upto 14 of these Type-4 records in a file; tenrolled impressions of the individual fingers, twoplain impressions of the thumbs and two plainimpressions of the four simultaneouslyobtained remaining fingers of each hand.

7.1.5 Type-S low-resolution binary record

Type-5 logical records shall contain, and beused to exchange low-resolution binary

fingerprint image data that was scanned at noless than the minimum scanning resolution andthen subsampled, scaled. or interpolated. Theresultant transmitting resolution shall be withinthe bounds of the permissible transmitting res-olutions for low-resolution fingerprint images.

The low-resolution binary fingerprint imagedata contained in the Type-S logical recordmay be in compressed form. There may be upto 14 of these Type-S records in a file; tenrolled impressions of the individual fingers,two plain impressions of the thumbs and twoplain impressions of the four simultaneouslyobtained remaining fingers of each hand.

7.1.6 Type-6 hlg h-resolutlon binary record

Type-6 logical records shall contain, and beused to exchange high-resolution binary fin-gerprint image data that was 'scanned at noless than the minimum scanning resolution. Ifthe scanning resolution is greater than theupper limit of the permissible transmitting res-olution, the scanned data shall be subsam-pled, scaled, or interpolated. The resultanttransmitting resolution shall be within thebounds of the permissible transmitting resolutions for high resolution fingerprint images.

The high-resolution binary fingerprint imagedata contained in the Type-6 logical recordmay be in compressed form. There may be upto 14 of these Type-6 records in a file; tenrolled impressions of the individual fingers,two plain impressions of the thumbs and twoplain impressions of the four simultaneouslyobtained remaining fingers of each hand.

7.1.7 Type-7 user-defined Image record

Type-7 logical recordsshall contain user-definedimage data, pertaining to the subject, which isnot elsewhere specified or described in thisstandard. The parameters and types of imagesto be exchanged are undefined by this standardand shall be agreed upon between the senderand recipient. This record type is included tohandlemiscellaneousimages such as those per-taining to palms, wrists, toes, soles, etc.

7.1.8 Type-a signature record

Type-8 logical records shall contain, and beused to exchange scanned high-resolutionbinary or vectorized signature image data. Ifscanned. the resolution of the image datashall be no less than the minimum scanning

--

--

-

ASCII Position Description

FS 1/12 Separates logical records of a file

GS 1/13 Separates fields of a logical record

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

US 1/15 Separates individual informationitems of the field or subfield

resolution. If necessary. the scanned imagedata shall be subsampled. scaled. or interpo-lated to fall within the limits of the transmittingresolution requirement. The resultant trans-mitting resolution shall be within the boundsof the permissible transmitting resolutions forthe high-resolution fingerprint images.Vectorized signature data shall be expressedas a series of binary numbers.

There may be up to two of these Type-8 sig-nature records in a file. Each Type-8 recordshall contain image data representing the sig-nature of the person being fingerprinted or ofthe official taking the fingerprints.

7.1.9 Type-S minutiae record

Type-9 logical records shall contain, and beused to exchange geometric and topologicalminutiae-based fingerprint and related infor-mation about a single finger. Each recordshall represent the processed image datafrom which the location and orientationdescriptors of extracted minutiae characteris-tics are listed. There may be from zero to tenType-9 records in the logical file. Each ofthese Type-9 logical records shall contain theminutiae data read from a single fingerprint.

7.2 Record format

For each type of logical record, several infor-mation fields shall be present. Data entrieswithin information fields may be further subdi-vided into information items that are used toconvey different aspects of the data containedin that field.

7.2.1 Information separators

In the Type-1, Type 2, and Type-9 records,mechanisms for delimiting information itemswithin a field, fields within a logical record.

and multiple occurrences of certain of thesedata and logical records shall be implementedby use of the four ASCII information separa-tors. These information separators aredefined in ANSI X3.4, and are described inthe code table in annex A. These' charactersare used to separate and qualify informationin a logical sense. Viewed in a hierarchicalrelationship, the File Separator (FS) is themost inclusive and it is used to separate logi-cal records. This is followed by the GroupSeparator (GS). the Record Separator (RS),and finally the Unit Separator (US).

Table 3 lists these ASCII separators, the column/row position in the ASCII table shown inannex A, and a description of their use withinthis standard. These separators shall be inaddition to any other symbols, punctuation, ordelimiters as specified in this standard.

The four characters shall be used only asseparators of data items, and only one ofthem may be used between any two dataitems. A US character cannot immediatelyprecede an RS character; an RS cannotimmediately precede a GS; and a GS cannotimmediately precede an FS character.Annexes B (Use of information separatorcharacters) and C (An example of the use ofthe standard) illustrate the use of these infor-mation separator characters.

7.2.2 Record layout

For Type-1, Type-2, and Type-9 records. eachinformation field that is used shall be num-bered in accordance with this standard. Theformat of each field shall consist of a fieldnumber followed by a colon (:), followed bythe information item(s) appropriate to thatfield, For Type-1 and Type-9 logical records.

-

-

field numbers have the format T.xx, where "ris the logical record type (chosen from table 1)and "xx" is a sequentially assigned field num-ber within that record type. For the Type-2 logi-cal record, field numbers have the formatT.xxx, where "r is the logical record type(chosen from table 1) and "xxx" is a sequen-tially assigned field number within that recordtype. Subfieldswithin a field shall be separatedby the RS character. Individual informationitemswithin a field or subfield shall be separated by the UScharacter. In addition to the iden-tifying number, information fields shall be sep-arated from other information fields by theASCII control character, Group Separator, GS.Where the information for any nonmandatoryfield is unavailable, that field shall be omitted.

Type-3, Type-4, Type-5, Type-6, Type-?, andType 8 records shall be recorded as orderedbinary fields. The length of the entire recordshall be specified by the record length fieldcontained in the record itself.

In contrast to the Type-1, Type-2, and Type-9records, neither the field identifier number,nor its following colon, shall be used in Type-3through Type 8 logical records. Furthermore,as all the field lengths of these six records areeither fixed or specified, none of the four sepa-rator characters (US, RS, GS, or FS) shall beinterpreted in any Type-3, Type-4, Type 5,Type-6,Type-?,or Type-8 record.

8.1 Fields for Type-1 transaction record

The following paragraphs describe the datacontained in fields for the Type-1 logicalrecord. Each field shall begin with the numberof the record type followed by a period fol-lowed by the appropriate field number fol-lowed by a colon. Annex C contains an exam-ple of the use of the standard, which illus-trates the layout for a Type-1 logical record.

8.1.1 Field 1.01: Logical Record Length (LEN)

This mandatory ASCII field shall contain thetotal count of the number of bytes in this Type-1 logical record. Field 1.01 shall begin with"1.01:", followed by the length of the recordincluding every character of every field contained in the record and the information sepa

rators. The GS character shall separate thelength code of Field 1.01 from the next field.

NOTE Although it may not always be explicitlyrepeated in the remainder of this standard, use ofseparators within Type-1, Type-2, and Type 9records shall always be observed. Multiple infor-mation items within a field or subfield shall be sepa-rated by the US separator, multiple subfields shallbe separated by the RS separator, and informationfields shall be separated by the GS separator.

8.1.2 Field 1.02: Version Number (VER)

This mandatory four byte ASCII field shall beused to specify the version number of thestandard implementedby the software or sys-tem creating the file. The format of this fieldshall consist of four numeric characters. Thefirst two characters shall specify the majorversion number. The last two characters shallbe used to specify the minor revision number.The initial revision number for a version shallbe "00". The entry in this field for this 1993approved standard shall be "0200·. The original 1986 standard would be considered thefirst version or ·0100".

8.1.3 Field 1.03: File Content (CNT)

This mandatoryfield shall list each of the logi-cal records in the logical file by record type. Italso specifies the order in which the remaininglogical recordsshall appear in the logical file. Itshall consist of one or more subfields. Eachsubfield shall contain two information itemsdescribing a single logical record found in thecurrent logical file. The subfields shall beentered in the same order in which the logicalrecords shall be transmitted. When more thanone subfield is used, the RS separator charac-ter shall be enteredbetween the subfields.

The first subfield shall relate to this Type-1transaction record. The first information itemwithin this subfield shall be the single charac-ter indicating that this is a Type-1 record con-sisting of header information (the numeral -1"selected from table 1).

The second information item of this subfieldshall be the sum of the Type-2 plus Type-3plus Type-4 plus Type-5 plus Type-6 plusType-? plus Type-8 plus Type-9 records con-tained in this logical file. This number is alsoequal to the count of the remaining subfieldsof Field 1.03. The US separator charactershall be entered between the first and secondinformation items.

-

-

--

-

-

-

-

--

The remaining subfields of Field 1.03 pertain-ing to Type-2, Type-3, Type-4, Type-5, Type-6, Type-7, Type-8, and Type-9 records con-tained in the file shall each be comprised oftwo information items. The first informationitem shall be a single character chosen fromtable 1, which states the record type. The sec-ond information item shall be the 10C associ-ated with the logical record pertaining to thatsubfield. The IDC shalt be a positive integerequal to or greater than zero. The US charac-ter shall be used to separate the two informa-tion items.

8.1.4 Field 1.04: Type of Transaction (TOT)

This mandatory field shalt contain an identifi-er, designating the type of transaction andsubsequent processing that this logical fileshould be given.

NOTE Type of Transaction shalt be in accor-dance with definitions provided by the receivingagency.

The last character of this field shall be a GSseparator character used to separate Field1.04 from t/:le next field.

8.1.5 Field 1.05: Date (OAT)

This mandatory field shall contain the datethat the transaction was initiated. The dateshall appear as eight digits in the formatCCYYMMOO.The CCYY characters shall rep-resent the year of the transaction; the MMcharacters shall be the tens and units valuesof the month; and the 00 characters shall bethe day in the month. For example, 19920601represents June 1, 1992. The complete dateshall not exceed the current date.

8.1.6 Field 1.06: Priority (PRY)

When this field is used, it shall contain a sin-gle information character to designate theurgency with which a response is desired. Thevalues shall range from 1 to 4, with "1" denot-ing the highest priority. The default value shallbe "4" if no value is indicated.

8.1.7 Field 1.07: Destination AgencyIdentifier (OAI)

This mandatory field shall contain the identifi-er of the administration or organization desig-nated to receive the transmission. The sizeand data content of this field shall be defined

by the user and be in accordance with thereceiving agency.

8.1.8 Field 1.08: Originating AgencyIdentifier (ORI)

This mandatory field shall contain the identifier of the administration or organization origi-nating the transaction. The size and datacontent of this field shall be defined by theuser and be in accordance with the receivingagency.

8.1.9 Field 1.09: Transaction ControlNumber (TCN)

This mandatory field shall contain theTransaction Control Number as assigned bythe originating agency. A unique control num-ber shalt be assigned to each tran.saction. Forany transaction that requires a response, therespondent shall refer to this number in com-municating with the originating agency.

8.1.10 Field 1.10: Transaction ControlReference (TCR)

This field shall be used in responses to referto the Transaction Control Number of a previous transaction involving an inquiry or otheraction that required a response.

8.1.11 Field 1.11: Native ScanningResolution (NSR)

This mandatory field shall specify the nominalscanning resolution of the AFIS or otherimage capture device supported by the origi-nator of the transmission. This field permitsthe recipient of this transaction to sendresponse data at a transmitting resolution tai-lored to the NSR (if it is able to do so) or tothe minimum scanning resolution. This fieldshall contain five bytes specifying the nativescanning resolution in pixels per millimeter.The resolution shall be expressed as twonumeric characters followed by a decimalpoint and two more numeric characters (e.g.,20.00). This field is needed because the inter-change of fingerprint information betweensystems of the same manufacturer may, insome instances. be more efficiently done at atransmitting resolution equal to the nativescanning resolution of the system rather thanat the minimum scanning resolution specifiedin this standard.

-

-

-

8.1.12 Field 1.12: Nominal TransmittingResolution (NTR)

This mandatory field shall specify the nominaltransmitting resolution for the image orimages being transmitted. This field shall con-tain five bytes specifying the transmitting res-olution in pixels per millimeter. The resolutionshall be expressed as two numeric charactersfollowed by a decimal point and two morenumeric characters (e.g., 20.00). The trans-mitting resolution shall be within the rangespecified by the transmitting resolutionrequirement.

8.2 End of Type-1 logical record

Immediately following the last information fieldin the Type-1 logical record, an FS separatorcharacter shall be used to separate it from thenext logical record. This FS character shallreplace the GS character that is normallyused between information fields.

Type 2 logical records shall contain textualinformation relating to the sUbjectof the trans-action and shall be represented in an ASCIIformat.

9.1 Fields for Type-2 logical records

The first two data fields of the Type-2 recordare defined by this standard. Remaining fieldsof the record shall conform to the require-ments set forth by the agency to whom thetransmission is being sent.

9.1.1 Field 2.001: Logical Record Length(LEN)

This mandatory ASCII field shall contain thelength of the logical record specifying the totalnumber of bytes, including every character ofevery field contained in the record.

9.1.2 Field 2.002: Image DesignationCharacter (IDC)

This mandatory field shall be used to identifythe user-defined text information contained inthis record. The IDC contained in this fieldshall be the IDC of the Type 2 logical recordas found in the file content field of the Type 1record.

9.1.3 Fields 2.003-2.999: User-DefinedFields for Type-2 Logical Record

Individual fields required for given transactiontypes,including field size and content, shallconform to the specifications set forth by theagency to whom the transmission is beingsent.


Immediately following the last information fieldin the Type-2 logical record, an FS separatorshall be used to separate it from the next logi-cal record. This FS character shall replace theGS character that is normally used betweeninformation fields.

10 Type-3 low-resolution grayscaleImage record

Type-3 logical records shall contain low-resolution grayscale fingerprint image data. Thefingerprint image data shall have beenscanned at no less than the minimum scan-ning resolution and then subsampled, scaled,or interpolated. Alternatively, provided that itis no less than the minimum scanning resolu-tion, the native sampling resolution may beused' and the image processed such that theresulting transmitting resolution is within therange specified by the transmitting resolutionrequirement for low-resolution images. Whenthe image data is obtained from a live-scanreader, it shall be the grayscale subsampled,scaled, or interpolated output of the live-scanfingerprint scanner and not a rescan of a hardcopy fingerprint image.

10.1 Fields for Type-3loglcal record

When there are one or more Type-3 logicalrecords, entries shall be provided in nineordered and unnumbered fields. The first eightfields are fixed length and total 18 bytes.These fields precede the image data containedin field 9. The size of field 9 is 18 bytes lessthan the value specified in the LEN field.

10.1.1 Logical Record Length (LEN)

This mandatory four-byte binary field shalloccupy bytes one through four. It shall containthe length of the logical record specifying thetotal number of bytes, inclUding every byte ofall nine fields contained in the record.

-

-

--

10.1.2 Image Designation Character (IDC)

This mandatory one-byte binary field shalloccupy the fifth byte of a Type-3 record. Itshall be used to identify the image data con-tained in this record. The IDC contained inthis field shall be a binary representation ofthe IDC found in the file content field of theType-1 record.

10.1.3 Impression Type (IMP)

This mandatory one-byte binary field shalloccupy the sixth byte of a Type-3 record. Thecode selected from table 4, describing the man-ner by which the fingerprint image informationwas obtained, shall be entered in this field.

10.1.4 Finger Position (FGP)

This mandatory fixed-length field of 6 binarybytes shall occupy the 7th through 12th bytepositions of a Type 3 record. It shall containpossible finger positions beginning in the leftmost byte of the field (byte seven of therecord). The decimal code number corresponding to the known or most probable fin-ger position shall be taken from table 5 andentered as a binary number right justified andleft zero filled within the eight-bit byte. Table 5also lists the maximum image area that canbe transmitted for each of the 14 possible fin-ger positions. Up to five additional finger posi-tions may be referenced by entering the alter-nate finger positions in the remaining fivebytes using the same format.

If fewer than five finger position referencesare to be used, the unused bytes shall befilled with the binary equivalent of M255". Thecode MO"(for ·Unknown Finger") shall be usedto reference every finger position from onethrough ten.

10.1.5 Image Scanning Resolution (ISR)

This mandatory one-byte binary field shalloccupy the 13th byte of a Type-3 record. Itshall contain a binary value of 0 if half theminimum scanning resolution is used and 1 ifhalf the native scanning resolution is used.

10.1.6 Horizontal Line Length (HLL)

This mandatory two-byte binary field shalloccupy the 14th and 15th bytes of the Type-3record. It shall be used to specify the numberof pixels contained on a single horizontal lineof the transmitted image.

Description Code

Live-scan plain 0Live-scan rolled 1Nonlive-scan plain 2Nonlive-scan rolled 3Latent impression 4

Latent tracing 5

Latent photo 6Latent lift 7

Table 5 Finger positioncode and maximum size

Maximumimage area

Finger position Code mm2

Unknown finger 0 1845Right thumb 1 1845Right index finger 2 1640Right middle finger 3 1640Right ring finger 4 1640Right little finger 5 1640Left thumb 6 1845Left index finger 7 1640Left middle finger 8 1640Left ring finger 9 1640Left little finger 10 1640Plain right thumb 11 2400Plain left thumb 12 2400Plain right four fingers 13 6800Plain left four fingers 14 6800

10.1.7 Vertical Line Length (VLL)

This mandatory two-byte binary field shall occu-py the 16th and 17th bytes of the Type-3 record.It shall be used to specify the number of horizon-tal lines contained in the transmitted image.

10.1.8 Grayscale Compression Algorithm(GCA)

This mandatory one-byte binary field shalloccupy the 18th byte of a Type-3 record. Itshall be used to specify the type of grayscale

-

--

-

compression algorithm used (if any). A binaryzero denotes no compression. Otherwise, thecontents of this byte shall be a binary represen-tation for the number allocated to the particularcompression technique used by the interchangeparties. The Federal Bureau of Investigation(FBI) will maintain a registry relating these num-bers to the compression algorithms.

10.1.9 Image Data

This binary field shall contain all of the lowresolution grayscale image data. Each pixel ofthe uncompressed image shall be quantizedto eight bits (256 gray levels) contained in asingle byte. If compression is used, the pixeldata shall be compressed in accordance withthe compression technique specified in theGCA field. This completes the low-resolutionimage description for a single image.


Since the Type-3 logical record is a definedand specified series of binary data fields, noadditional bytes shall be transmitted to signifythe end of this logical record type.

10.3 Additional low-resolution grayscaleImages

Up to 13 more images may be described with-in the logical file. For each additional image, aType-3 logical record is required.

11 Type-4 high-resolution grayscaleImage record

Type-4 logical records shall contain high-reso-lution grayscale fingerprint image data thathas been scanned at the minimum scanningresolution. Alternatively, the native scanningresolution may be used and the image pro-cessed such that the resulting transmittingresolution is within the range specified by thetransmitting resolution requirement for high-resolution images. When the image data isobtained from a live-scan reader, it shall bethe grayscale output of the live-scan finger-print scanner and not a rescan of a hard copyfingerprint image.

11.1 Fields for Type-4 logical record

When there are one or more Type-4 logicalrecords, entries shall be provided in nineordered and unnumbered fields. The first

eight fields are fixed length and total 18 bytes.These fields precede the image data con-tained in field 9. The size of field 9 is 18 bytesless than the value specified in the LEN field.

11.1.1 Log leal Record Length (LEN)

This mandatory four-byte binary field shalloccupy bytes one through four. It shall containthe length of the logical record specifying thetotal number of bytes, including every byte ofall nine fields contained in the record.


This mandatory one-byte binary field shalloccupy the fifth byte of a Type-4 record. Itshall be used to identify the image data con-tained in this record. The IDC contained inthis field shall be a binary representation ofthe IDC found in the file content field of theType-1 record.


This mandatory one-byte binary field shalloccupy the sixth byte of a Type-4 record. Thecode selected from table 4, describing the manner by which the fingerprint image informationwas obtained, shall be entered in this field.


This mandatory fixed-length field of six binarybytes shall occupy the 7th through 12th bytepositions of a Type-4 record. It shall containpossible finger positions beginning in the left-most byte of the field (byte seven of therecord). The decimal code number for theknown or most probable finger position shallbe taken from table 5 and entered as a binarynumber right justified and left zero filled withinthe eight-bit byte. Up to five additional fingerpositions may be referenced by entering thealternate finger positions in the remaining fivebytes using the same format. If fewer than fivefinger position references are to be used, theunused bytes shall be filled with the binaryequivalent of "255". The code ·0" (for"Unknown Finger") shall be used to referenceevery finger position from one through ten.


This mandatory one-byte binary field shalloccupy the thirteenth byte of a Type-4 record.It shall contain a binary value of 0 if the mini-

-

-

-

mum scanning resolution is used and 1 if thenative scanning resolution is used.

11.1.6 Horizontal line Length (HLL)


11.1.7 V-ertlcalline Length (VLL)

This mandatory two-byte binary field shalloccupy the 16th and 17th bytes of the Type-4record. It shall be used to specify the numberof horizontal lines contained in the transmittedimage.

11.1.8 Grayscale Compression Algorithm(GCA)

This mandatory one-byte binary field shalloccupy the 18th byte of a Type-4 record. Itshall be used to specify the type of grayscalecompression algorithm used (if any). A binaryo denotes no compression. Otherwise, thecontents of this byte shall be a binary repre-sentation for the number allocated to the particular compression technique used by theinterchange parties. The FBI will maintain aregistry relating these numbers to the com-pression algorithms.

11.1.9 Image Data

This binary field shall contain all of the high-resolution grayscale image data. Each pixel ofthe uncompressed image shall be quantizedto eight bits (256 gray levels) contained in asingle byte. If compression is used, the pixeldata shall be compressed in accordance withthe compression technique specified in theGCA field. This completes the high-resolutionimage description for a single image.



11.3 Additional high-resolution grayscaleImages


12 Type-S low-resolution binary Imagerecord

Type-5 logical records shall contain low-reso-lution binary fingerprint image data. The fin-gerprint image data shall have been scannedat no less than the minimum scanning resolu-tion and then subsampled, scaled, or interpo-lated. Alternatively, provided that it is no lessthan the minimum scanning resolution, thenative scanning resolution may be used andthe image processed such that the resultingtransmitting resolution is within the rangespecified by the transmitting resolutionrequirement for low-resolution images. Whenthe image data is obtained from a live-scanreader, it shall be the binarized, subsampled,scaled, or interpolated output of the live-scanfingerprint scanner and not a re.scan of ahard-copy fingerprint image.


When there are one or more Type-S logicalrecords, entries shall be provided in nineordered and unnumbered fields. The firsteight fields are fixed length and total 18 bytes.These fields precede the image data con-tained in field 9. The size of field 9 is 18 bytesless than the value specified in the LEN field.


This mandatory four-byte binary field shalloccupy bytes one through four. It shall containthe length of the logical record specifying thetotal number of bytes, including every byte ofall nine fields contained in the record.


This mandatory one-byte binary field shalloccupy the fifth byte of a Type-S record. Itshall be used to identify the image data con-tained in this record. The IDe contained inthis field shall be a binary representation ofthe IDC found in the file content field of theType 1 record.


This mandatory one-byte binary field shalloccupy the sixth byte of a Type 5 record. Thecode selected from table 4, describing themanner by which the fingerprint image infor-mation was obtained, shall be entered in thisfield.

-

-

-


This mandatory fixed-length field of 6 binarybytes shall occupy the 7th through 12th bytepositions of a Type-5 record. It shall containpossible finger positions beginning in the left-most byte of the field (byte seven of therecord). The decimal code number for theknown or most probable finger position shallbe taken from table 5 and entered as a bina-ry number right justified and left zero filledwithin the eight-bit byte. Up to five additionalfinger positions may be referenced by enter-ing the alternate finger positions in theremaining five bytes using the same format.If fewer than five finger position referencesare to be used. the unused bytes shall befilled with the binary equivalent of "255". Thecode ·0" (for ·Unknown Finger") shall beused to reference every finger position fromone through ten.


This mandatory one-byte binary field shalloccupy the 13th byte of a Type-5 record. Itshall contain a binary value of 0 if half theminimum scanning resolution is used, and 1 ifhalf the native scanning resolution is used.



12.1.7 Vertical Line Length (VLL)

This mandatory two-byte binary field shalloccupy the 16th and 17th bytes of the Type-5record. It shall be used to specify the numberof horizontal lines contained in the transmittedimage.

12.1.8 Binary Compression Algorithm(BCA)

This mandatory one-byte binary field shalloccupy the 18th byte of a Type-5 record. Itshall be used to specify whether or not datacompression is used. A binary 0 denotesno compression. A binary 1 denotes the useof the facsimile compression standard(ANSI/EIA 538) for the loss less compressionand decompression of the image data.

12.1.9 Image Data

This field shall contain all of the low-resolutionbinary image data. Each pixel of the uncom-pressed image shall be quantized to two lev-els (binary representation). Uncompresseddata shall be packed at 8 pixels per byte. Ifcompression is used, the pixel data shall becompressed in accordance with the techniqueas specified in SeA field. This completes thelow-resolution binary image description for asingle image.

12.2 End of Type-S logical record


12.3 Additional low-reso Iutlon binaryImages


13 Type-6 high-resolution binaryimage record

Type-6 logical records shall contain high-reso-lution binary fingerprint image data that hasbeen scanned at the minimum scanning reso-lution. Alternatively, the native scanning reso-lution may be used and the image processedsuch that the resulting transmitting resolutionis within the range specified by the transmitting resolution requirement for high-resolutionimages. When the image data is obtainedfrom a live-scan reader, it shall be the bina~rized output of the live-scan fingerprint scan-ner and not a rescan of a hard-copy finger-print image.

13.1 Fields for Type-6 togical record

When there are one or more Type-6 logicalrecords, entries shall be provided in nineordered and unnumbered fields. The firsteight fields are fixed length and total 18bytes. These fields precede the image datacontained in field 9. The size of field 9 is 18bytes less than the value specified in the LENfield.

-

-

13.1.1 Log ical Record Length (LEN)

This mandatory four-byte binary field shalloccupy bytes one through four. It shall containthe length of the logical record specifying thetotal number of bytes. including every byte ofall nine fields contained in the record.


This mandatory one byte binary field shalloccupy the fifth byte of a Type-6 record. Itshall be used to identify the image data con-tained in this record. The IDC contained inthis field shall be a binary representation ofthe IDC found in the file content field of theType 1 record.


This mandatory one-byte binary field shalloccupy the sixth byte of a Type-6 record. Thecode selectedfrom table 4, describing the man-ner by which the fingerprint image informationwas obtained. shall be entered in this field.


This mandatory fixed length field of six binarybytes shall occupy the 7th through 12th bytepositions of a Type-6 record. It shall containpossible finger positions beginning in the left-most byte of the field (byte seven of therecord). The decimal code number for theknown or most probable finger position shallbe taken from table 5 and entered as a binarynumber right justified and left zero filled withinthe eight-bit byte. Up to five additional fingerpositions may be referenced by entering thealternate finger positions in the remaining fivebytes using the same format. If fewer than fivefinger position references are to be used, theunused bytes shall be filled with the binaryequivalent of ~255". The code "0" (for·Unknown Finger") shall be used to referenceevery finger position from one through ten.


This mandatory one-byte binary field shalloccupy the 13th byte of a Type-6 record. Itshall contain a binary value of 0 if the mini-mum scanning resolution is used and 1 if thenative scanning resolution is used.


This mandatory two-byte binary field shalloccupy the 14th and 15th bytes of the Type-6

record. It shall be used to specify the numberof pixels contained on a single horizontal lineof the transmitted image.

13.1.7 Vertical line Length (VLL)

This mandatorytwo-byte binary field shall occu-py the 16thand 17th bytes of the Type-6 record.It shallbe usedto specifythe number of horizon-tal linescontainedin the transmitted image.

13.1.8 Binary Compression Algorithm(BCA)

This mandatory one-byte binary field shalloccupy the 18th byte of a Type-6 record. Itshall be used to specify whether or not datacompression is used. A binary 0 denotes nocompression. A binary 1 denotes the use ofthe facsimile compression standard (ANSIIEIA538) for the lossless compression al1ddecom-pression of the image data.

13.1.9 Image Data

This field shall contain all of the high-resolu-tion binary image data. Each pixel of theuncompressed image shall be quantized totwo levels (binary representation). Uncompressed data shall be packed at eight pixelsper byte. If compression is used. pixel datashall be compressed in accordance with thetechnique as specified in SCA field. This com-pletes the high-resolution binary imagedescription for a single image.



13.3 Additional high-resolution binaryimages


Type-7 logical records shall contain userdefined image information relating to the subject of the transaction. This record type maybe used to exchange image data that is notaddressed elsewhere in this standard. Imagespertaining to palms, wrists, toes, and soles

-

-

- -

--

are examples of the usage for this recordtype. Scanned pixels may be either binary orgrayscale output. Each grayscale pixel valueshall be expressed as an unsigned byte. Avalue of 0 shall be used to define a black pixeland an unsigned value of 255 shall be used todefine a white pixel. For binary pixels. a valueof 0 shall represent a white pixel and a valueof 1 shall represent a black pixel. If compres-sion is used. the algorithm shall be the sameas that specified for Type-3, Type-4. Type-5,and Type-6 logical records.

14.1 Fields for Type-710gical record

The first two data fields of the Type-7 recordare defined by this standard. Remaining fieldsof the record shall conform to the require-ments set forth by the agency to whom thetransmission is being sent.

The first two fields are fixed length and totalfive bytes. These fields shall precede one ormore user-defined fields, including the imagedata, contained in the remainder of the record.


This mandatory four-byte binary field shalloccupy bytes one through four. It shall containthe length of the logical record specifying thetotal number of bytes, including every byte ofall the fields contained in the record.


This mandatory one-byte binary field shalloccupy the fifth byte of a Type-7 record. It shallbe used to identify the image data contained inthis record. The IDC contained in this field shallbe a binary representation of the IDC found inthe file content field of the Type-1 record.

14.1.3 User-defined fields for Type-7 logi-cal record

The remaining fields of the Type-7 logicalrecord shall be user-defined. Individual fieldsrequired for a given transaction, such as fielddescription. size, and content shall conform tothe specifications set forth by the agency towhom the transmission is being sent.


Since the Type 7 logical record is a defineda:ld specified series of binary data fields, noadditional bytes shall be transmitted to signifythe end of this logical record type.

14.3 Additional user-defined Imagerecords

Additional images may be described withinthe logical file. For each additional image. aType-7 logical record is required.

Type 8 logical records shall contain eitherscanned or vectorized signature data. EachType-8 record shall cover an area of up to1000 mm2.

If scanned. the resolution shall be the mini-mum scanning resolution or the native sam-pling resolution. and the scan sequence shallbe left to right and top to bottom. The scanneddata shall be quantized to two levels (binaryrepresentation).

If vectorized signature data is present. it shallbe expressed as a series of binary numbers.


When there are one or two Type-8 logicalrecords, entries shall be provided in sevenordered and unnumbered fields. The first sixfields are fixed length and shall total 12 bytes.These fields shall precede the image datacontained in field 7. The size of field 7 isdetermined from the LEN field of the recorditself. The image data field is 12 bytes lessthan the value specified in the LEN field.


This mandatory four-byte binary field shalloccupy bytes one through four. It shall containthe length of the logical record expressed asthe total number of bytes. including every byteof all seven fields contained in the record.


This mandatory one-byte binary field shalloccupy the fifth byte of the Type-8 record. Itshall be used to identify the image data con-tained in the Type-8 record. The IDC con-tained in this field shall be a binary represen-tation of the IDC found in the file content fieldof the Type-1 record.

15.1.3 Signature Type (SIG)

This mandatory one-byte binary field shalloccupy the sixth byte of the Type-8 record. Its

-

value shall be '0000 0000' if the image is thesubject's signature, or '0000 0001' if theimage is the fingerprinting official's signature.

15.1.4 Signature Representation Type(SRT)

This mandatory one-byte binary field shalloccupy the seventh byte of the Type-8 record.Its value shall be '0000 0000' if the image isscanned and not compressed, '0000 0001' ifthe image is scanned and compressed, and'0000 0010' if the image is vector data.


This mandatory one-byte binary field shalloccupy the eighth byte of a Type-8 record. Itshall contain a binary value of 0 if the mini-mum scanning resolution is used and 1 if thenative scanning resolution is used. A value ofo shall also be used if the image is vectordata.

15.1.6 Horizontal Line length (Hll)

This mandatory two byte binary field shalloccupy the ninth and tenth bytes of the Type-8 record. For scanned signature data, thisfield shall be used to specify the number ofpixels contained on a single horizontal line ofthe transmitted signature image. For vector-ized signature data, both bytes shall containthe value '0000 0000'.

15.1.7 Vertical Line length (Vll)

This mandatory two-byte binary field shalloccupy the 11th and 12th bytes of the Type 8record. For scanned signature data, this fieldshall be used to specify the number of horizon-tal lines contained in the transmitted signatureimage. For vectorized signature data, bothbytes shall contain the value '0000 0000'.

15.1.8 Signature Image Data

This field shall contain uncompressedscanned image signature data, compressedscanned image signature data, or vectorizedimage signature data. The entry contained inthe SRT field shall indicate which form of thesignature data is present.

15.1.8.1 Uncompressed Scanned ImageData

If the SRT field contains the value '0000 0000',then this field shall contain the uncompressedscanned image data for the signature. In

uncompressed mode, the data shall bepacked at eight pixels per byte.

15.1.8.2 Compressed Scanned Image Data

If the SRT field contains the value '0000 0001',then this field shall contain the scanned imagedata for the signature in compressed formusing the facsimile compression algorithmdescribed in ANSI/EtA 538.

15.1.8.3 Vectorlzed Image Data

If the SRT field contains the value '0000 0010',then this field shall contain a list of vectorsdescribing the pen position and pen pressureof line segments within the signature. Eachvector shall consist of five bytes.

The first two bytes of each vector shall containthe unsigned binary X coordinate of the penposition with the high order byte"containingthe most significant bits. The next two bytesshall contain the unsigned Y coordinate usingthe same convention to denote the most sig-nificant bits. Both the X and Y coordinatesshall be expressed in units of 0.0254 mm(0.001 inches) referenced from the bottomleftmost corner of the signature. Positive val-ues of X shall increase from left-to-right andpositive values of Y shall increase from bot-tom-to-top.

An unsigned binary number between a and255 contained in the fifth byte shall representthe pen pressure. This shall be a constantpressure until the next vector becomes active.A pressure of '0000 0000' shall represent a"pen-up" (or no pressure) condition. The bina-ry value '0000 000 l' shall represent the leastrecordable pressure for a particular device,while a value of '1111 1110' shall representthe maximum recordable pressure for thatdevice. To denote the end of the vector list, apressure value of '1111 1111' shall be insert-ed in this entry.



15.3 Additional signature

One more signature may be described withinthe logical file. For this additional signature, aType-8 logical record is required.

-

-

Type-9 records shall contain minutiae dataand related information about a single finger.There may be up to ten of these Type-9records in a file, each of which shall be for adifferent finger.

16.1 Fingerprint Information descriptors

16.1.1 Minutia type Identification

This standard defines four identifier charactersthat are used to describe the type of any minu-tia. These are shown in table 6. A ridge endingshall be designated Type A. It occurs when afriction ridge begins or ends within the finger-print and without splitting into two or more con-tinuing ridges. The ridge must be longer than itis wide. A bifurcation shall be designated TypeB. It occurs when a ridge divides or splits toform two ridges that continue past the point ofdivision for a distance that is at least equal tothe spacing between adjacent ridges at thepoint of bifurcation. A minutia shall be designat-ed Type C, a compound type, when it is eithera trifurcation (a single ridge that splits intothree ridges) or a crossover (two ridges thatintersect). When a minutia cannot be clearlycategorized as one of the above three types, itshall be designated as undetermined, Type O.

16.1.2 Minutia numbering

Each minutia in the fingerprint shall be identi-fied by assigning it an arbitrary index number.The numbering shall begin at one and beincremented by one for as many times asthere are minutiae. This allows each minutiato be uniquely identified.

16.1.3 Minutia ridge counts

Ridge counts may be made from each minutiain a fingerprint to certain other minutiae.When this occurs, ridge counts between des-ignated minutiae shall be associated with theapplicable index numbers so as to ensuremaintenance of the proper relationships.

16.1.4 Minutia coordinate system

The relative position of minutiae entered inType-9 records shall be expressed as positiveintegers in units of 0.01 mm (0.000 39 in) in aCartesian coordinate system located inQuadrant 1. In this coordinate system, valuesof X increase from left to right and values of Y

Type Description

A Ridge ending

B Bifurcation

C Compound (trifurcation or crossover)

0 Type undetermined

increase from bottom to top. Values of both Xand Yare equal to or greater than -0000" andare less than -5000". If the conversion to thiscoordinate system is from a system that nor-mally centers the fingerprint image during theregistration process, that center position shallbe assigned the values X 2509, Y 2500.Figure 2 illustrates the defined coordinatesystem.

The relative orientation, Theta, of a ridge end-ing, a bifurcation, a compound or a minutia ofundetermined type shall be expressed as pos-itive integers in units of degrees. Theta shallbe the angle between the horizontal axis ofthe coordinate system and the direction that aridge ending points, assuming that a ridgeending is analogous to a pointing finger. Aridge ending that is formed by a ridge lyingparallel to the X axis, and ending in the direc-tion of increasing values of X, shall have anorientation of zero degrees. Counterclockwiserotation of this ridge about the ridge endingshall cause the value of Theta to increase.

A bifurcation may be converted to a ridge end-ing by logical inversion, that is, transposing theidentity of ridges and valleys. The orientationof a bifurcation is expressed as if this inversionhad occurred. This convention causes no sig-nificant change in the orientation of a minutia ifit appears as a ridge ending in one impressionof a fingerprint and as a bifurcation in anotherimpression of the same fingerprint.

No orientation shall be assigned to compoundor undetermined type minutiae; therefore, avalue of "000" shall be entered for Theta inthe Type-9 logical record entry.

The exact features or characteristics of aminutia that are used to establish its positionand orientation are system dependent andoutside the scope of this standard.

= =

Minutia Data ,,,,//\,

", Theta

"'<heta 45 units \____~~_ ~~~~."."~t:'- _;{__ _________________ __

Units:X, V, 0.01 mmTheta 1°/unit


16.2.1 Field 9.01: Logical Record Length (LEN)

This mandatory ASCII field shall contain thelength of the logical record specifying the totalnumber of bytes. including every character ofevery field contained in the record.

16.2.2 Field 9.02: Image DesignationCharacter (IDC)

This mandatory two-byte field shall be usedfor the identification and location of the minu-tiae data. The IDC contained in this field shallmatch the IDC found in the file content field ofthe Type-1 record.

16.2.3 Field 9.03: Impression Type (IMP)

This mandatoryone-byte field shall describe themanner by which the fingerprint image informa-tion was obtained.The binary value of the propercode as selectedfrom table 4 shall be entered inthis field to signify the impressiontype.

16.2.4 Field 9.04: Minutiae Format (FMT)

This mandatory one-byte field shall be used toindicate whether the remainder of the record

adheres to the standard or is user-defined.This field shall contain an US"to indicate thatthe minutiae are formatted as specified by thestandard Type-9 logical record field descrip-tions. This field shall contain a "U" to indicatethat the minutiae are formatted in user elefinedterms. If the minutiae record is formatted inuser-defined terms, the remaining fields of thislogical record may not be applicable.

16.2.5 Field 9.05: Originating FingerprintReading System (OFR)

The originator's designation or name for theparticular fingerprint reading system that gen-erated this record shall be placed in the firstinformation item of this field. The secondinformation item of this field shall be a singlecharacter to indicate the method by which theminutiae data was read. encoded, and record-ed. The following coding shall be used: (1)"An, if the data was automatically read, encod-ed, and recorded without any possibility ofhuman editing; (2) "U", if human editing waspossible but unneeded; (3) "E", if the data wasautomatically read but manually edited beforeencoding and recording; (4) "M", if the data

~

=

=

-

manually read. The third information item isan optional, two-character, user-generatedsubsystem designator that uniquely identifiesthe originator's equipment.

16.2.6 Field 9.06: Finger Position (FGP)

This mandatory field shall contain a characterdesignating the finger position that producedinformation in this Type-9 record. If the exactfinger position cannot be determined, multiplefinger positions may be entered, separated bythe RS character. The first 11 entries of table 5list the codes that shall be used for each finger.

16.2.7 Field 9.07: Fingerprint PatternClassification (FPC)

This mandatory field shall contain the finger-print pattern classification code. It shall containtwo information items. The first information itemshall indicate the source of the specific patternclassification code. It may be one chosen fromtable 7 or may be a user-defined classificationcode. This item shall contain a ~T" to indicatethat the pattern classification code is from table7, or a ~U" to indicate that the code is userdefined. The second information item of thisfield shall contain the pattern classificationcode chosen from table 7 or a specific user-defined code. Reference finger classes shall beseparated by the RS character.

16.2.8 Field 9.08: Core Position (CRP)

If this eight-character field is used, it shallcontain the X and Y coordinate position of thecore. The X and Y values shall be coded as asingle a-digit integer number comprised of the4-digit X-coordinate concatenated with the 4-digit V-coordinate using a format ofXXXXYYYY.

16.2.9 Field 9.09: Delta(s) Position (DLT)

If this eight-character field is used, it shallcontain the X and Y positional coordinates ofeach delta that is present on the fingerprint.The X and Y values shall be recorded in thesame manner as was done for the core posi-tion coordinates. Multiple occurrences of deltapositions shall be separated by the RS sepa-rator.

16.2.10 Field 9.10: Number of Minutiae (MIN)

This mandatory single-character field shallcontain the count of the number of minutiaerecorded for this fingerprint.

Description Code

Plain arch PA

Tented arch TA

Radial loop RL

Ulnar loop UL

Plain whorl PW

Central pocket loop CP

Double loop DL

Accidental whorl AW

Whorl, type not designated WN

Right slant loop RS

Left slant loop LS

Scar SR

Amputation XX

Unknown or unclassifiable UN

16.2.11 Field 9.11: Minutiae Ridge CountIndicator (RDG)

This mandatory single-character field shall beused to indicate the presence of minutiaeridge count information. A ·0" in this field indi-cates that no ridge count information is avail-able. A ~1"indicates that ridge count informa-tion is available.

16.2.12 Field 9.12: Minutiae and RidgeCount Data (MRC)

This variable field length shall contain all ofthe individual minutiae and ridge count dataassociated with the current fingerprint impres-sion. It shall be comprised of as many sub-fields as there are minutiae stated in theminutiae count in field 9.10. Each subfieldshall be devoted to a single minutia and shallconsist of multiple information items. The firsttwo information items shall always appear; theappearance of others is system dependent.The information items are identified in theorder that they shall appear. All informationitems shall be separated from the subsequentitems by the US separator character.

16.2.12.1 Index number

The first information item shall be the indexnumber, which shall be initialized to "1" andincremented by one for each additional minu-tia in the fingerprint. This index numberserves to identify each individual minutia.

16.2.12.2 X, Y, and Theta values

The X and Y coordinates (two 4 digit valuesranging from zero upward), and the Thetavalue (a 3-digit value between 000 and 359)shall comprise the second required informa-tion item. These three values shall be codedand recorded as a single 11-digit integer num-ber corresponding to the concatenated X, Y.and Theta values, in that order. If the minutiais of Type C or Type D. the Theta value shallbe recorded as "000".

16.2.12.3 Quality measure

If present, the third information item is anoptional quality measure. Values shall rangefrom "0" to "63". The value "0" shall indicate amanually encoded minutia. The value "1" shallindicate that no method of indicating a confidence level is available. Values between "2"and "63" shall indicate decreasing levels ofconfidence, with "2" meaning the greatestconfidence.

16.2.12.4 Minutia type desig nation

The fourth information item is an optionalminutia type designation. This shall be a singlealphabetic character as chosen from table 6.

16.2.12.5 Ridge count data

The fifth information item is optional ridgecount data. It shall be formatted as a series ofsubitems, each consisting of a minutia num-

ber and a ridge count. This information shallbe conveyed by listing the identity (indexnumber) of the distant minutia followed by acomma, and the ridge count to that distantminutia. Subitems shall be separated by a UScharacter. This subitem may be repeated asmany times as required for each minutia (sub-field).

16.2.12.6 Record separator

A record separator character, RS, shall beused at the end of the information items tointroduce the first information item concerningdata for the next minutia. The process shallbe continued until all of the minutia and ridgedata have been entered into the field.


Immediately following the last information fieldin the Type-9 logical record, an FS separatorshall be used to separate it from the next logi-cal record. This FS character shall replace theGS character separator that is normally usedbetween information fields.

16.4 Additional minutiae records

Up t6 nine more fingers may be describedwithin the logical file. For each additional fin-ger, a Type-9 logical record, and an FS sepa-rator is required.

If fingerprint data for another individual is tobe recorded or transmitted, a new logical fileshall be generated for that individual using thesame format as described previously.

-

-

Annex A (normative)

ANSI code for information interchange

b7 = MSB b6

bs

~ ~ ~

0 0 0

0 0

1

0 1 0

0 1 1

1 0 0

1 0

1

1 1 0

1 1

1

B b4 .!-j

t

b3 .!-b2 J

b1 .!-COLUMN

~ ROW.!-

0 1 2 3 4 5 6 7

s

0 0 0 0 0 NUL OLE SP 0 @ P . P

0 0 0 1 1 SOH OC1 ! 1 A Q a q

0 0 1 0 2 STX OC2 " 2 B R b r

0 0 1 1 3 ETX DC3 # 3 C S c s

0 1 0 0 4 EOT DC4 $ 4 D T d t

0 1 0 1 5 ENQ NAK % 5 E U e u

0 1 1 0 6 ACK SYN & 6 F V f v

0 1 1 1 7 BEL ETB · 7 G W g w

1 0 0 0 8 BS CAN ( 8 H X h x

1 0 0 1 9 HT EM ) 9 I Y i Y

1 0 1 0 10 LF SUB · J Z j z

1 0 1 1 11 VT ESC + . K [ k {

1

1

1

1

0

0

0

1

12

13

FF

CR

FS

GS

· -

<

=

L

M

\

]

I

m

I }

1 1 1 0 14 SO RS > N 1\ n -1 1 1 1 15 SI US / ? 0 - 0 DEL

Annex B(informative)

FN is the field number of a field within a Type-1 or Type-2 or Type-9 record.

IF is the information field associated with an FN.

II is the information item belonging to an IF.

SF is the subfield used for multiple entries of an liar an IF.

The G used between fields the F between logical records:S S

F . GS FN1 • IF S

For fields with more than one information item, the U is used:S

G FS FNk S

For fields with multiple subfields, the R is used:S

FFN ... S

-

'"

Annex C(informative)

"LOGICAL RECORD LENGTH (LEN)

"VERSION NUMBER (VER)

"FILE CONTENT (CNT)

"TYPE OF TRANSACTION (TOT)

"DATE (OAT)

PRIORITY (PRY)

"DESTINATION AGENCY IDENTIFIER (DAI)

"ORIGINATING AGENCY IDENTIFIER (ORI)

·TRANSACTION CONTROL NUMBER (TCN)

TRANSACTION CONTROL REFERENCE (TCR)

·NATIVE SCANNING RESOLUTION (NSR)

"NOMINAL TRANSMITIING RESOLUTION (NTR)

·LOGICAl RECORD LENGTH (LEN)

·IMAGE DESIGNATION CHARACTER (IDC)

USER-DEFINED INFORMATION

1ST TYPE 4 RECORD

LOGICAL RECORD LENGTH (LEN)

IMAGE DESIGNATION CHARACTER (IDC)

IMPRESSION TYPE (IMP)

FINGER POSITION (FGP)

IMAGE SCANNING RESOLUTION (ISR)

HORIZONTAL LINE LENGTH (HLl)

VERTICAL LINE LENGTH (VLL)

GRAYSCALE COMPRESSION ALGORITHM (GCA)

IMAGE DATA

1.01:241~

1.02:0200~

1.03:1~17~2~0~4~01~4~02~4~03~4~04~4~OS~4~06~4~

07~4~8~~9~4~10~~11~4~12~4~13~~14~8~1S~8~16~

1.04:CA~

1.05:19920601~

1.06:1~

1.07:DCFBIWA6~

1.08:NY0303000SLAS01 OOO~

1.09:1234S6789~

1.10:234S678901~

1.11 :20.000~

1.12:20.000ifs

TYPE-2 RECORD

2.01:811~

2.02:00~

(ASCII TEXT DATA)~

00 00 78 SA (HEX)

01 (HEX)

03 (HEX)

01 FF FF FF FF FF (HEX)

01 (HEX)

0320 (HEX)

02EE (HEX)

01 (HEX)

(GRAYSCALE IMAGE DATA FOR ROLLEDIMPRESSION OF RIGHT THUMB)

- -

2ND TYPE-4 RECORD



IMPRESSION lYPE (IMP)



HORIZONTAL LINE LENGTH (HLL)



IMAGE DATA

14TH TYPE 4 RECORD



IMPRESSION lYPE (IMP)






IMAGE DATA

1ST TYPE-8 RECORD



SIGNATURE lYPE (SIG)

SIGNATURE REPRESENTATION lYPE (SRT)




SIGNATURE IMAGE DATA

00 00 75 30 (HEX)

02 (HEX)

03 (HEX)

02 FF FF FF FF FF (HEX)

01 (HEX)

0320 (HEX)

02EE (HEX)

01 (HEX)

(GRAYSCALE IMAGE DATA FOR ROLLEDIMPRESSION OF RIGHT INDEX FINGER)

00 01 03 7C (HEX)

OE (HEX)

03 (HEX)

OE FF FF FF FF FF (HEX)

01 (HEX)

060E (HEX)

0384 (HEX)

01 (HEX)

(GRAYSCALE IMAGE DATA FOR PLAINIMPRESSION OF THE FOUR FINGERS ON THELEFT HAND)

00 00 44 OE (HEX)

OF (HEX)

00 (HEX)

01 (HEX)

01 (HEX)

OSDC (HEX)

0187 (HEX)

(COMPRESSED IMAGE DATA OF THE SUBJECTSSIGNATURE)

- -

-

-

2ND TYPE-8 RECORD



SIGNATURE TYPE (SIG)

SIGNATURE REPRESENTATION TYPE (SRT)



VERTICAL LINE LENGTH (Vll)

SIGNATURE IMAGE DATA

00 00 3F A3 (HEX)

10 (HEX)

01 (HEX)

01 (HEX)

01 (HEX)

05DC (HEX)

0187 (HEX)

(COMPRESSED IMAGE DATA OF THE SIGNATUREOF THE OFFICIAL TAKING THE PRINTS)

-

ansi nist csl1-1993pdf | nist

Documents