FBI Electronic Biometric Transmission Specification
FBI Electronic Biometric Transmission Specification
FBI Electronic Biometric Transmission Specification
Department of Justice Federal Bureau of Investigation Criminal Justice Information Services Division
ELECTRONIC BIOMETRIC TRANSMISSION SPECIFICATION (EBTS) NIEM Information Exchange Package Documentation
Revision 1.5 04/17/09
Prepared by: Requirements Management Unit Information Technology Management Section 1000 Custer Hollow Road Clarksburg, WV 26306
1.2
Joe Wade
04/02/2008
N/A
1.3
Joe Wade
04/28/2008
N/A
1.4
Patrice Yuh
04/13/2009
N/A
1.5
Patrice Yuh
04/17/09
N/A
03/17/09 BIO-DOC-02261-1.5
TABLE OF CONTENTS
1 2 3 4 Purpose.................................................................................................................... 1-6 Scope........................................................................................................................ 2-7 List of Artifacts ...................................................................................................... 3-8 XML Schemas ........................................................................................................ 4-9 4.1 Subset Schemas................................................................................................ 4-9 4.2 Extension XML Schema .................................................................................. 4-9 Additional Provisions........................................................................................... 5-10 5.1 Additional Property Definitions..................................................................... 5-10 5.1.1 The EBTS Transactions ............................................................................. 5-10 5.1.2 The EBTS Records .................................................................................... 5-11 5.1.3 EBTS Field Mnemonic/NIEM Definitions................................................ 5-12 5.2 Minimal Properties Set .................................................................................. 5-43 5.3 Additional Business Rules ............................................................................. 5-43 5.3.1 FIELD MNEMONIC SETS....................................................................... 5-44 5.3.2 Fingerprint Images ..................................................................................... 5-44 5.3.3 User Defined Images.................................................................................. 5-44 5.3.4 Minutiae Data............................................................................................. 5-45 5.3.5 Facial Images ............................................................................................. 5-45 5.3.6 Latent Print Images .................................................................................... 5-45 5.3.7 Major Case Print ........................................................................................ 5-45 5.3.8 Palmprint Images ....................................................................................... 5-45 5.3.9 Iris Images.................................................................................................. 5-45 5.3.10 CBEFF Biometric Data.......................................................................... 5-45 5.3.11 Messages Layout.................................................................................... 5-45 5.3.12 Inbound Messages.................................................................................. 5-45 5.3.13 Response Messages................................................................................ 5-47 Samples ................................................................................................................. 6-49 6.1 Samples XML Instances ................................................................................ 6-49 Development ......................................................................................................... 7-52 7.1 Participants..................................................................................................... 7-52 7.2 Process: .......................................................................................................... 7-52 7.3 Development Artifacts:.................................................................................. 7-53 7.3.1 Schema Model Diagram ............................................................................ 7-53 7.3.2 Transaction Model Diagram ...................................................................... 7-54 7.3.3 Detailed Transaction Model Diagram........................................................ 7-55 Testing and Conformance ................................................................................... 8-56 8.1 Testing............................................................................................................ 8-56 8.2 Conformance.................................................................................................. 8-56 Feedback ............................................................................................................... 9-57
6 7
04/17/09 BIO-DOC-02261-1.5
1-4
LIST OF TABLES
Table 5-1 XML Cross-Reference................................................................................... 5-12 Table 5-2 Field Mnemoic Reference ............................................................................. 5-44 Table 7-1 Participants .................................................................................................... 7-52
LIST OF FIGURES
Figure 7-1 EBTS Sample ............................................................................................... 7-54 Figure 7-2 EBTS Detailed Sample ................................................................................ 7-55
04/17/09 IAFIS-DOC-04277-1.0
1 PURPOSE
The Federal Bureau of Investigation Electronic Biometric Transmission Specification is the method by which the Federal Bureau of Investigation supports the exchange of biometric data used to facilitate the determination of the personal identity of a subject from fingerprint, palm, facial or other biometric information, across criminal justice agencies or organizations that use an Automated Fingerprint Identification System (AFIS) or related systems nationwide. These biometric specifications are standards for electronically encoding and transmitting biometric image, identification and arrest data. The FBI EBTS is comprised of the biometric standards entitled Data Format for the Interchange of Fingerprint, Facial, & Other Biometric Information (ANSI/NIST-ITL 1-2007), which are composed by the American National Standards Institute (ANSI) in correspondence with The Information Technology Laboratory (ITL) of the National Institute of Standards and Technology (NIST). These standards define the content, format and units of measurement for the exchange of biometric information. The FBI EBTS serves criminal justice agencies in the 50 states, the District of Columbia, Puerto Rico, and Canada. This Interface Exchange Package Documentation (IEPD) covers the FBI EBTS 8.1 XML Data Reference Model.
04/17/09 BIO-DOC-02261-1.5
1-6
2 SCOPE
Data in the Federal Bureau of Investigation (FBI) Electronic Biometric Transmission Specification (EBTS) files are exchanged with and for the official use of criminal justice officials of local, state, and federal governments in the U.S. and its possessions and in Canada.
04/17/09 BIO-DOC-02261-1.5
2-7
3 LIST OF ARTIFACTS
1. NIEM Subset schemas 2. JXDM Subset schema 3. ANSI-NIST Subset schema 4. FBI Subset schema 5. Extension schema 6. XML Document Instance 7. Data Model Diagram 8. XML Mappings 9. NIEP Documentation
04/17/09 BIO-DOC-02261-1.5
3-8
4 XML SCHEMAS
NIEM Version: 2.0 JXDM Version: 4.0 ANSI-NIST Version: 2.0 FBI Version 2.0 At the time the FBI EBTS Schema was implemented, 2.0 was the current NIEM version that was available. The FBI Advisory Policy Board had decided that the FBI will implement EBTS schema using NIEM; therefore, NIEM 2.0 that is the current release version of NIEM was used during the implementation of the FBI EBTS Information Exchange Package for purposes of information sharing. NIEM was designed to work in conjunction with schemas geared toward specific domains (e.g., Criminal Justice, Biometrics, and Law Enforcement) necessary to capture the business requirements for an EBTS transaction. These domain specific schemas were released in correspondence with NIEM 2.0.
For the purpose of this document elements utilized from these schemas will be referred to as NIEM Elements but referenced by the corresponding namespace.
04/17/09 BIO-DOC-02261-1.5
4-9
5 ADDITIONAL PROVISIONS
5.1 Additional Property Definitions
The basic requirements for EBTS messages are Logical Records Type-1, Type-2, Type-4, Type-7, Type-9, Type-10, Type 13, Type-14, Type 15, Type 16, Type 17 and Type 99 set forth in the ANSI standards which are also applicable to transmissions to the FBI. The FBI-specific requirements for the contents and format of Logical Records Type-2, Type-7, and Type-9 as well as for any special requirements for the other record types, are captured in the business requirements for an EBTS transaction. 5.1.1 The EBTS Transactions FBI CJIS Division will process the following seven types of fingerprint and four photo transactions from the four main service areas in its electronic environment. There are several types of transactions for each service area that will be accepted by the FBI, the sender must designate the Type of Transaction (TOT) in the Type-1 Record to specify the which process is to be followed. Ten-Print Services Electronic Ten-Print Submissions enable users to submit ten-prints from live-scan booking terminals or card scanners at either the federal, state or local level. Remote Ten-Print Searches allow users to search existing records by electronically transmitting fingerprint images or remotely extracted fingerprint characteristics. The user can request specific finger images, up to all 14 fingerprint images, via the Fingerprint Number(s) Requested (FNR) field. Electronic Latent Submissions enable the agency having legal jurisdiction of the case, either federal, state or local, to submit latent prints (fingerprints, palm prints, toe prints, and footprints). Remote Latent Searches allow the agency having legal jurisdiction of the case, either federal, state or local, to search existing records by transmitting latent print images or corresponding feature sets. The user can set the maximum number of candidate images to be returned via the Number of Candidates Images returned (NCR) field. Latent Image Maintenance Requests allow IAFIS users to specify transactions (delete or add confirm) related to an unsolved latent file. Remote Requests for Fingerprint Images enable users to retrieve ten-print images from the FBI Criminal Ten-print Fingerprint Image Master File. Electronic Requests to Upgrade Fingerprint Images allow users to request fingerprint images on file at the FBI or to request updates of existing images.
Latent Services
Image Services
04/17/09 BIO-DOC-02261-1.5
5-10
Photo Services Criminal Subject Photo Requests allow users to request criminal photo sets on file at the FBI or to request the deletion of existing photo sets.
5.1.2 The EBTS Records Type-1 Header Record Record required for each transaction, providing information describing the type and use or purpose for the transaction involved, a listing of each logical record included, the original source of the physical record and other useful and required information items. Records containing textual fields providing identification and descriptive information associated with the subject of the transaction. Records used to exchange high-resolution grayscale fingerprint image data that was scanned at no less than the minimum scanning resolution. Records used exchange image data that is not elsewhere specified or described in the ANSI-NIST standard, including miscellaneous images such as those pertaining to latent prints, wrists, toes, soles, etc. Records used to exchange geometric and topological minutiae templates and related information encoded from a fingerprint, palm, or latent image. Each record shall represent the processed image data from which the location and orientation descriptors of extracted minutiae characteristics are listed. Records used to exchange facial and image data from scars, marks, and tattoos (SMT) together with textual information pertinent to the digitized image. The source of the image data shall be the image captured from scanning a photograph, a live image captured with a digital camera, or a digitized freeze-frame from a video camera. Records containing and used to exchange image data acquired from latent fingerprint or palmprint images. Textual information regarding the scanning resolution, the image size and other parameters or comments required to process the image are recorded as tagged-fields within the record. Records used to exchange variable-resolution fingerprint image data, segmented flat fingerprint data or major case print data. All fingerprint impressions shall be
Type-2 Record
Type-4 Record
Type-7 Record
Type-9 Record
Type-10 Record
Type-13 Record
Type-14 Record
04/17/09 IAFIS-DOC-04277-1.0
acquired from a ten-print card, a major case print card, or from a live-scan device. Fingerprint images can be either rolled or plain (including swiped) impressions. Type-15 Record Records used to exchange variable-resolution palmprint image data. Records used to exchange test image data. Records used to exchange iris image data. Records used to exchange biometric data that is not supported by other logical record types. This record type supports and is intended to be used for exotic biometric data types. Type-16 Record Type-17 Record Type-99 Record
5.1.3 EBTS Field Mnemonic/NIEM Definitions The following table represents the association of EBTS Field Mnemonics, Field Numbers, and the NIEM XML Data elements. This table is provided to help implementers cross-reference the XML property definition. It is assumed that the data elements definitions and specifications are available in the FBI EBTS. Throughout this document, inbound refer to messages coming into the FBI Biometric System and outbound refers to messages generated by the FBI Biometric System.
Table 5-1 XML Cross-Reference Field Mnemonic ACN AFV Field Number 2.071 9.013 NIEM Element
AGR
2.023
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<nc:PersonAlternateName> <nc:PersonGivenName/>
AKA 2.019
AMP
<itl:FingerprintImageFingerMissing> <ansi-nist:FingerPositionCode/> <itl:FingerMissingCode> </itl:FingerprintImageFingerMissing> <itl:PalmprintImageQuality> <ansi-nist:PalmPositionCode/> <ansi-nist:QualityAlgorithmProductIdentification> <nc:IdentificationID/> </ansi-nist:QualityAlgorithmProductIdentification> <ansi-nist:QualityAlgorithmVendorIdentification> <nc:IdentificationID/> </ansi-nist:QualityAlgorithmVendorIdentification> <ansi-nist:QualityValue/> </itl:PalmprintImageQuality>
FGP AMPCD
APM
15.024
ASL
2.047
<j:Arrest> <nc:ActivityDate>
DOO
2.047A
<nc:Date/> </nc:ActivityDate>
AOL
2.047B
<nc:ActivityDescriptionText/> </j:Arrest>
ATN
2.006
<nc:CaveatText/>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<ansi-nist:ImageCaptureDetail> <ansi-nist:CaptureDate>
BCD 99.005
BDQ
99.102
BFO
99.103
BFT
99.104
<nc:IdentificationID/> </ansi-nist:CBEFFFormatCategoryIdentification>
<ansi-nist:ImageBitsPerPixelQuantity/>
CAN
2.064
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<nc:PersonName> <nc:PersonGivenName/>
NAM 2.064B
FNU
2.064A
CCN
2.094X
CFS
2.077
<ebts:TransactionCancelFingerprintSearchIndicator/> </ebts:RecordTransactionData>
<ansi-nist:ImageCompressionAlgorithmText/>
<ebts:MinutiaCharaterizationQualityValue/>
X Future Capability
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
CIX CLQ
2.011 9.025
<ebts:ContributorCaseIdentificationExtensionNumber/> <ebts:MinutiaClassifierQualityValue/> <ansi-nist:TransactionContentSummary> <ansi-nist:ContentFirstRecordCategoryCode/> <ansi-nist:ContentRecordCount/> <ansi-nist:ContentRecordSummary> <ansi-nist:ImageReferenceIdentification> <nc:IdentificationID/> </ansi-nist:ImageReferenceIdentification> <ansi-nist:RecordCategoryCode/> </ansi-nist:ContentRecordSummary> </ansi-nist:TransactionContentSummary> <ansi-nist:PhysicalFeatureDescriptionDetail> <ansi-nist:PhysicalFeatureColorDetail> <ansi-nist:PhysicalFeaturePrimaryColorCode/> <ansi-nist:PhysicalFeatureSecondaryColorCode/> </ansi-nist:PhysicalFeatureColorDetail> </ansi-nist:PhysicalFeatureDescriptionDetail>
CNT
1.003
COL
10.043
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
NIEM Element
COM
<ansi-nist:ImageCommentText/>
CRN
2.085
<nc:IdentificationID/> </ebts:CivilRecordIdentification>
CSF CSL
2.2006X 2.051
CDD
2.051A
CPL
2.051C
<j:ChargeDispositionOtherText/> </j:ChargeDisposition>
X Future Capability
04/17/09 IAFIS-DOC-04277-1.0
NIEM Element
<ansi-nist:ImageColorSpaceCode/>
<ebts:RecordTransactionData>
CSR 2.048
<ebts:TransactionCivilSearchRequestIndicator/> </ebts:RecordTransactionData>
CST CTZ
<ebts:CaseTitleText/> <nc:PersonCitizenshipText/>
DAT
<nc:BinaryBase64Object/>
<ansi-nist:TransactionDate>
DAT 1.005
DAI
1.007
<nc:IdentificationID/> </nc:OrganizationOtherIdentification>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
DMI
<ebts:TransactionDispositionMaintenanceCode/> <ansi-nist:ImageCaptureDetail> <ansi-nist:CaptureDescriptionCode/> </ansi-nist:ImageCaptureDetail> <ebts:BinaryCODISAvailableIndicator> <nc:PersonDNA> <nc:DNAImage> <nc:BinaryAvailableIndicator/> </nc:DNAImage> </nc:PersonDNA>
DMM
DNAC
2.2018
DNAF
2.2016
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<nc:ActivityDate>
DOA 2.045
DOB
2.022
DOM
1.013
DORI
2.2017
DOS
2.046
DPR
2.038
DUI
17.017
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<nc:LocationStreet> <nc:StreetNumberText/> <nc:StreetName/> </nc:LocationStreet> <nc:LocationCityName/> <nc:LocationPostalCode/> <nc:LocattionStateNCICLSTACode/> </nc:StructuredAddress> </nc:LocationAddress> </nc:EmploymentLocation> </ebts:PersonEmploymentAssociation>
ECL
17.020
<ansi-nist:IrisEyeColorAttributeCode/>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
ETC
2.069
EXP
2.080
EYE
2.031
<nc:PersonEyeColorCode/> <j:PersonFBIIdentification>
FBI
2.014
<nc:IdentificationID/> </j:PersonFBIIdentification>
FFN
2.003
FGN
9.014
FGP
2.074
<ansi-nist:FingerPositionCode/> </ebts:FingerprintImageFinger>
FGP FGP
<ansi-nist:MinutiaeFingerPositionCode/> <ansi-nist:FingerPositionCode/>
04/17/09 IAFIS-DOC-04277-1.0
NIEM Element
<ansi-nist:IrisEyePositionCode/> <ebts:TransactionFingerprintImagesUpdated>
FIU
2.072
<ansi-nist:FingerPositionCode/> </ebts:TransactionFingerprintImagesUpdated>
FMT FNR
9.004 2.057
FPC
2.033
FPC
9.007
<ansi-nist:FingerPatternText/> <ansi-nist:FingerPatternCode/> </ansi-nist:MinutiaeFingerPatternDetail> <itl:FingerprintImageQuality> <ansi-nist:FingerPositionCode/> <ansi-nist:QualityAlgorithmProductIdentification> <nc:IdentificationID/> </ansi-nist:QualityAlgorithmProductIdentification> <ansi-nist:QualityAlgorithmVendorIdentification> <nc:IdentificationID/> </ansi-nist:QualityAlgorithmVendorIdentification> <ansi-nist:QualityValue/> </itl:FingerprintImageQuality>
FQM
14.024
GCA GEO
7.08 2.044
<ansi-nist:ImageCompressionAlgorithmCode/> <ebts:TransactionSearchAreaCode/>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<ansi-nist:TransactionUTCDate>
GMT 1.014
GUI
17.018
HAI
2.032
<nc:PersonHairColorCode/> <ansi-nist:CBEFFVersionIdentification>
HDV
99.100
HGT
2.027
<nc:MeasurePointValue/> </nc:PersonHeightMeasure>
HLL
7.06, 10.006, 13.006, 14.006, 15.006, 16.006, 17.006 10.009, 13.009, 14.009,
<ansi-nist:ImageHorizontalLineLengthPixelQuantity/>
HPS
<ansi-nist:ImageHorizontalPixelDensityValue/>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<nc:PersonHeightMeasure> <nc:MeasureRangeValue>
HTR 2.028
ICO
2.056 2.002, 7.02, 9.002, 10.002, 13.002, 14.002, 15.002, 16.002, 17.002, 99.002
<nc:ActivityDescriptionText/>
IDC
IMG
<nc:BinaryBase64Object/>
IMP
<ansi-nist:FingerprintImageImpressionCaptureCategoryCode/>
04/17/09 IAFIS-DOC-04277-1.0
NIEM Element
IPC
17.016
IQM
14.022
IQS
17.024
IRD
17.005
04/17/09 IAFIS-DOC-04277-1.0
NIEM Element
<ansi-nist:RecordCategoryCode/> <ansi-nist:ImageCaptureDetail>
ISR
7.05
LCD
13.005, 14.005
LCN
2.012
<nc:IdentificationID/> </ebts:FBILatentCaseIdentification>
LCX MAT
2.013 9.023
MDX
9.023A
<nc:IdentificationID/> </ansi-nist:MinutiaIdentification>
1 This element does not map to any numbered EBTS tag. It preserves the record type number.
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<ansi-nist:MinutiaRidgeCount> <ansi-nist:RidgeCountReferenceIdentification>
MRO 9.023E-L
RSO
9.023M
<ebts:MinutiaOctantResidualValue/> </ebts:Minutiae> <ansi-nist:FingerprintImageMajorCasePrint> <ansi-nist:MajorCasePrintSegmentOffset> <ansi-nist:SegmentBottomVerticalCoordinateValue/> <ansi-nist:SegmentLocationCode/> <ansi-nist:SegmentFingerViewCode/> <ansi-nist:SegmentLeftHorizontalCoordinateValue/> <ansi-nist:SegmentRightHorizontalCoordinateValue/> <ansi-nist:SegmentTopVerticalCoordinateValue/> </ansi-nist:MajorCasePrintSegmentOffset> </ansi-nist:FingerprintImageMajorCasePrint> <ansi-nist:FingerprintImageMajorCasePrint>
MCS
13.015, 14.015
MCL
13.014, 14.014
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<ansi-nist:ReadingSystemSubsystemIdentification>
VID 9.016B
MIL
2.042
MMS
17.019
MNU
2.017
<nc:IdentificationID/> </nc:PersonOtherIdentification>
MRC
9.012
<itl:MinutiaDetail> <ansi-nist:MinutiaIdentification>
MDX
9.012A
<nc:IdentificationID/> </ansi-nist:MinutiaIdentification>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<ansi-nist:MinutiaRidgeCount> <ansi-nist:RidgeCountReferenceIdentification>
MCOUNT 9.012E
<nc:IdentificationID/> </ansi-nist:RidgeCountReferenceIdentification> <ansi-nist:RidgeCountValue/> </ansi-nist:MinutiaRidgeCount> </itl:MinutiaDetail> <ebts:TransactionCandidateList> <ebts:CandidateListMatchScore/> </ebts:TransactionCandidateList> <ebts:TransactionResponseData> <ebts:TransactionStatusText/> </ebts:TransactionResponseData> <nc:PersonName> <nc:PersonGivenName/>
MSC
2.089
MSG
2.060
NAM
2.018
<ebts:PersonExtendedName/>
X Future Capability
04/17/09 IAFIS-DOC-04277-1.0
NIEM Element
NSR
1.011
NTR
1.012
<ansi-nist:NominalTransmittingResolutionValue/> </ansi-nist:TransactionImageResolutionDetails>
OCA
2.009
<nc:CaseTrackingID/> <ebts:PersonEmploymentAssociation>
OCP
2.040
<nc:EmployeeOccupationText/> </ebts:PersonEmploymentAssociation>
OFR_SUBS YS
9.005C
ORI
1.008
04/17/09 IAFIS-DOC-04277-1.0
NIEM Element
<ansi-nist:PositionUncertaintyValue/> <ansi-nist:ImageCaptureDetail>
PAS
10.023
<ansi-nist:CaptureSourceCode/> <ansi-nist:ImageCaptureDetail>
PCD
15.005
PEN
2.078
PHD
10.005
PHT
2.036
<nc:BinaryAvailableIndicator/> </nc:PersonDigitalImage>
PLP POA
15.013 10.021
<ansi-nist:PalmPositionCode/> <ansi-nist:FaceImagePoseOffsetAngleMeasure/>
04/17/09 IAFIS-DOC-04277-1.0
NIEM Element
PPA
2.035
PXS
10.022
X Future Capability
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
RBRO
2.2020
REC
2.082
RDG
9.011
<ansi-nist:MinutiaeRidgeCountIndicator/>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
RSR
2.065
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<j:Arrest> <j:ArrestSequenceID>
SAN 2.099X
SAP SCNA
10.013 2.086
SCO
2.007
SDOB
2.2007X
<nc:Date/> </ebts:PersonSubmittedBirthDate>
SEAL SEC
2.2019 10.027
<ebts:ArrestSealIndicator> <ansi-nist:FaceImageEyeColorAttributeCode/>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
SEX
2.024
SFP
10.029
SHC
10.028 13.016,
SHPS
SVPS
SID
2.015
<nc:IdentificationID/> </nc:PersonStateIdentification>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
NIEM Element
SLC
<ansi-nist:ImageScaleUnitsCode/>
<j:ArrestRelease>
SLE 2.055
SMD
10.042
SMS
10.041
SMT
2.026
<nc:PhysicalFeatureCategoryCode/> </nc:PersonPhysicalFeature>
SMT
10.040
<ansi-nist:PhysicalFeatureNCICCode/>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<ebts:PersonSubmittedName> <nc:PersonGivenName/>
SNAM 2.2008X
SOC
2.016
<nc:IdentificationID/> </nc:PersonSSNIdentification> <ansi-nist:FaceImage3DPoseAngle> <ansi-nist:PosePitchAngleMeasure/> <ansi-nist:PosePitchUncertaintyValue/> <ansi-nist:PoseRollAngleMeasure/> <ansi-nist:PoseRollUncertaintyValue/> <ansi-nist:PoseYawAngleMeasure/> <ansi-nist:PoseYawUncertaintyValue/> </ansi-nist:FaceImage3DPoseAngle> <ebts:RecordSpecialPopulationCognizantFileldIdentification>
SPA
10.025
SPCN
2.093X
<nc:IdentificationID/> </ebts:RecordSpecialPopulationCognizantFileldIdentification>
X Future Capability
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
SQS
10.024
SRF
2.059
<ebts:TransactionSearchResultsCode/>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<j:ArrestRelease> <nc:ActivityDate>
SSD 2.054
SXS TAA
10.026 2.087
TCN
1.009
TCR
1.010
<nc:IdentificationID/> </ansi-nist:TransactionControlReferenceIdentification>
TOT
1.004
TSR
2.043
UCN
2.081
<nc:IdentificationID/> </ebts:PersonUCNIdentification>
UDI ULF
16.003 2.083
<nc:BinaryDescriptionText/> <ebts:TransactionUnsolvedLatientFileIndicator/>
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
<ansi-nist:ImageCaptureDetail> <ansi-nist:CaptureDate>
UTD 16.005
VER
1.002
<ansi-nist:TransactionMajorVersionValue/> <ansi-nist:TransactionMinorVersionValue/>
VLL
7.07, 10.007, 13.007, 14.007, 15.007, 16.007, 17.007 10.010, 13.010, 14.010,
<ansi-nist:ImageVerticalLineLengthPixelQuantity/>
VPS
<ansi-nist:ImageVerticalPixelDensityValue/>
<nc:PersonWeightMeasure>
WGT 2.029
WTR
2.030
04/17/09 IAFIS-DOC-04277-1.0
Field Mnemonic
Field Number
NIEM Element
2.2015
04/17/09 IAFIS-DOC-04277-1.0
The Electronic Rap Sheet (ERS 2.075) has been created in GJXDM and will not be embedded within an FBI EBTS message but rather sent as a separate transaction following the receipt of an FBI EBTS message. 5.3.1 FIELD MNEMONIC SETS Certain Field Mnemonics for the FBI EBTS transactions are sets made up of several fields. These fields have been represented in the existing set as well as individual MFCs in Section 5.1.1 The EBTS Transactions
Table 5-2 Field Mnemoic Reference Field Mnemonic AMP ASL CAN CIN CRA CRP CSL DLT DLA MAT MRC OFR PAT Field Number 2.084 2.047 2.064 2.010 9.008 9.021 2.051 9.009 9.022 9.023 9.012 9.005 2.034 SET MFCS AMPCD, FGP DOO, AOL NAM. FNU CIN_PRE, CIN_ID XYM, DID, DID, DID, PUM, DID XYM, DID, DID, DID, PUM, DID CDD, COL, CPL XYM, DID, DID, DID, PUM, DID XYM, DID, DID, DID, PUM, DID MDX, XYT, QMS, MTD, MRO, RSO MDX, MXYTHETA, MQUAL, MTD, MCOUNT OFR_METHOD, OFR_NAME, OFR_SUBSYS PATCL, FGP
5.3.2 Fingerprint Images Specifications for this image are defined in the ANSI-NIST Type 4 Record and ANSINIST Type 14 Record based on the resolution requirements. 5.3.3 User Defined Images Specifications for this image are based on the ANSI-NIST Type 7 Record. The FBI EBTS has additional requirements for this message and therefore has extended the ANSINIST User Defined Image requirements to include information specific to a Biometric Identification message.
04/17/09 IAFIS-DOC-04277-1.0
5.3.4 Minutiae Data Specifications for this data are based on the ANSI-NIST Type 9 Record. The FBI EBTS has additional requirements for this message and therefore has extended the ANSI-NIST Minutiae requirements to include information specific to a Biometric Identification message. 5.3.5 Facial Images Specifications for this image are defined in the ANSI-NIST Type 10 Record, using the fields specific for a Facial Image Record. 5.3.6 Latent Print Images Specifications for this image are defined in the ANSI-NIST Type 13 Record. 5.3.7 Major Case Print Specifications for this image are based on the ANSI-NIST Type 14 Record. 5.3.8 Palmprint Images Specifications for this image are based on the ANSI-NIST Type 15 Record. 5.3.9 Iris Images Specifications for this image are based on the ANSI-NIST Type 17 Record. 5.3.10 CBEFF Biometric Data Specifications for this data are based on the ANSI-NIST Type 99 Record. 5.3.11 Messages Layout The sample XML data instances that are included to support this package contain element representations to capture the various possible scenarios. An FBI EBTS XML message will not include all the elements defined in the samples; all the elements are represented in the sample to capture their structures and formats in a valid XML FBI EBTS message. The goal of this representation is to help guide agencies and vendors in their design of systems for FBI EBTS XML interchange. Schema instance references can be used as XML attributes in XML instance messages to enforce the constraints that have been implemented in the extension schema and in the various document schemas. 5.3.12 Inbound Messages An individual XML inbound transaction, contains at least two records: a Header Record (Type 1 Record) and a User Defined Descriptive Text Record (Type 2 Record). Inbound transactions may also contain several Image Records including: Fingerprint Images, User Defined Images, and Facial and SMT Images. Inbound transactions may also contain records pertaining to Minutiae Information.
04/17/09 IAFIS-DOC-04277-1.0
The additional record requirements for each record type are as follows: Ten-Print Criminal Justice Submissions: 14 Type 4 or Type 14 Records 10 Rolled Impressions 4 Sets of Plain Impressions 0-20 Type 14 Major Case Print Images 0-8 Type 15 Palmprint Records 0-N Type-10 Records containing photos 0-2 Type-17 Iris image Records 0-N Type-99 CBEFF Records
Ten-Print Non-Criminal Justice Submissions: 14 Type 4 or Type 14 Fingerprint Image Records 10 Rolled Impressions 4 Sets of Plain Impressions OR 3 Type 14 records (non-criminal justice purposes only) 2 Plain Simultaneous Four Finger Impressions 1 Plain Left and Right Thumb Impression OR 2-10 Type 4 or Type 14 Flat or Rolled Images AND 0-12 Type 14 Major Case Print Images AND 0-8 Type 15 Palmprint Records 0-N Type-10 Records Containing Photos 0-2 Type-17 Iris Image Records 0-N Type-99 CBEFF Records
Ten-Print Searches: 1-14 Type-4 or Type-14 Fingerprint Image Records OR 1-10 Type-9 Fingerprint Features Records
Latent Submissions: 1-14 Type-4 or Type-13 Fingerprint Image Records 1-10 for Latent Submissions 14 for Comparison Ten-print Fingerprint Submissions 14 for Major Case Submissions OR 1-n Type-7 Records
04/17/09 IAFIS-DOC-04277-1.0
Latent Searches: 1-10 Type-4 Fingerprint Image Records OR 1-10 Type-13 Fingerprint Image Records OR 1-10 Type-7 Records 1-10 Type-9 Features Records
Electronic Requests to Upgrade Fingerprint Images: 14 Type-4 or Type-14 Fingerprint Image Records.
5.3.13 Response Messages An individual XML outbound transaction contains at least two records: a Header Record and a User Defined Descriptive Text Record. Information pertaining to the actual response will be contained within the User Defined Descriptive Text Record. The response message may also contain Fingerprint Images, User Defined Images, Facial and SMT Images and Minutiae Information Records. The User Defined Descriptive Text Record of a response Message will contain a Transaction Response Data Section, which has information specific to an EBTS response transaction, including fields specifying any action or direction for the user to take upon receiving the transaction, error messages and other detailed information pertaining to the results of a search. Additional records that may be returned by the responses are as follows: Ten-Print Submission Responses: 0-1 Type-10 Photo record containing the most recent mug shot
Ten-Print Search Responses: 0-14 Type-4 or Type-14 Fingerprint Image Records (SRT only) 0-1 Type-10 Photo record containing the most recent full frontal photo (RPSR only)
Latent Submission Responses: 0-14 Type-4 or Type-14 Fingerprint Image Records (LSR only)
Remote Requests for Fingerprint Image Responses: 0-14 Type-4 or Type-14 Fingerprint Image Records (IRR only) 0-14 Type-9 Features Records 0-8 Type-15 Palmprint Images 0-2 Type-17 Iris Images
04/17/09 IAFIS-DOC-04277-1.0
04/17/09 IAFIS-DOC-04277-1.0
6 SAMPLES
To help agencies, users and vendors design and develop their XML processing system for FBI EBTS messages, the FBI has provided as part of this Interface Definition Package sample EBTS XML messages with sanitized content.
6-49
SampleLatentTransactionErrorTransaction.xml SampleMajorCaseImageSubmissionTransaction.xml SampleNotificationofActionResponseTransaction.xml SampleSearchResultsLatentTransaction.xml SampleUnsolicitedUnsolvedLatentDeleteTransaction.xml SampleUnsolvedLatentAddConfirmRequestTransaction.xml SampleUnsolvedLatentAddConfirmResponseTransaction.xml SampleUnsolvedLatentDeleteResponseTransaction.xml SampleUnsolvedLatentMatchResponseTransaction.xml SampleUnsolvedLatentRecordDeleteRequestTransaction.xml EBTS Schema Package\1.0.2\tenprint SampleAmnesiaVictimTransaction.xml SampleCriminalFingerprintCardDirectRouteTransaction.xml SampleCriminalFingerprintCardProcessingNonUrgentTransaction.xml SampleCriminalTenPrintAnswerRequiredTransaction.xml SampleCriminalTenPrintNoAnswerTransaction.xml SampleElectronicSubmissionResultsTransaction.xml SampleFederalApplicantNoChargeTransaction.xml SampleFederalApplicantUserFeeTransaction.xml SampleFederalNoChargeDirectRouteTransaction.xml SampleKnownDeceasedTransaction.xml SampleMiscellaneousApplicantCivilTransaction.xml SampleMissingPersonTransaction.xml SampleNonFederalAdvancedPaymentTransaction.xml SampleNonFederalApplicantUserFeeTransaction.xml SampleNonFederalNoChargeDirectRouteTransaction.xml SampleRapidPrintImageResponseTransaction.xml SampleRapidPrintImageSearchTransaction.xml SampleTenPrintFingerprintFeaturesSearchTransaction.xml SampleTenPrintFingerprintImageSearchTransaction.xml SampleTenPrintRapSheetTransaction.xml SampleTenPrintSearchResultsTransaction.xml
04/17/09 IAFIS-DOC-04277-1.0 UNCLASSIFIED//FOR OFFICIAL USE ONLY 6-50
04/17/09 IAFIS-DOC-04277-1.0
7 DEVELOPMENT
The EBTS IEP was developed by the Federal Bureau of Investigation (FBI) Criminal Justice Information Services (CJIS) Division. The FBI developed this IEP in conjunction with the Wisconsin Department of Justice, the Georgia Tech Research Institute, and the Joint Task Force for Rapsheet Standardization as primary reviewers.
7.1 Participants
Implementers contributed to the EBTS IEP design and implementation, and review Contributors contributed to the EBTS IEP design and review. Reviewers contributed to the EBTS IEP by reviewing the XML instances to ensure EBTS data representation and EBTS data integrity.
Table 7-1 Participants Name Ast, Terri Coleman, Gerry Wade, Joe Yuh, Patrice Organization FBI Contractor Wisconsin DOJ FBI Contractor FBI Role Implementer Contributor Implementer Implementer
7.2 Process:
Important meeting dates during the development of EBTS XML Information Exchange Package include: To design and implement our Information Exchange Package, we developed a strategy based on Unified Modeling Language recommendation including: Data discovery, an analysis phase during which we mapped EBTS elements to NIEM base elements and to augmented data Data Description, a design phase during which we organized data based on the business relation between them; during this phase, we capture the semantic and syntactic structure of data Data review, a phase during which internal review and external reviews were conducted Data implementation and schema generation, an implementation phase that also focused on validation
04/17/09 BIO-DOC-02261-1.5
7-52
Data validation phase focused on ensuring that schemas and instance documents follow NIEM rules
The EBTS XML Data Reference Model was developed by leveraging from GTRI approach of using an object-oriented framework to define elements. NIEM types were used as the based types and our augmentation data was added to them while allowing reuse of that data. The differentiation of augmentation data and base data is handled with the namespace prefix. Base data are associated with jxdm namespace while augmentation data are associated with ncic namespace or a file-specific namespace. The schema development environment of choice was XMLSpy; which enabled the efficient development and validation of schemas. XMLSpy also enabled the integration of sample XML instance data with the generated schemas and validation of business and constraint requirements. This validation also ensured that augmented data is applied to objects of the expected type and that instances follow NIEM rules. A highly consistent method for defining XML instance data was used in which messages were defined using exact cardinality and exact sequences to help users and vendors generate messages in the expected formats.
04/17/09 IAFIS-DOC-04277-1.0
1
Type 1 Record: itl:PackageInformationRecord
014
01
Type 7 Record: itl:PackageImageRecord
010
04
Type 10 Record: itl:PackageImageRecord
010
08
020
02
0
Type 99 Record:
itl:PackageImageRecord
04/17/09 IAFIS-DOC-04277-1.0
7.3.3
ebts:DomainDefinedDescriptiveTe xt Type 15 Record: itl:PackageImageRecord itl:PalmprintImage ansi-nist:RecordCategoryCode ansi-nist:ImageReferenceIdentification Type 17 Record: ebts:AlternatePalmprintQualityValue
ansi-nist:RecordCategoryCode ansi-nist:ImageReferenceIdentification
ansinist:FingerprintImage
ansinist:FaceImage
itl:PackageImageRecord
itl:IrisImage
itl:PackageImageRecord ansinist:CBEFFImage
ansi-nist:RecordCategoryCode ansinist:ImageReferenceIdentification
04/17/09 IAFIS-DOC-04277-1.0
In order to receive a meaningful EBTS message systems should be able to receive a minimum of: Ten-Print Submission Responses: Type-10 Photo Records Ten-Print Search Responses: Type-4 OR Type-14 Records. Latent Submission Responses: Type-4 OR Type-14 Records. Latent Search Responses: Type-4 OR Type-14 Records. Remote Requests for Fingerprint Image Responses: Type-4, Type-7, Type-9, Type-13, Type-14, Type-15 OR Type-17 Records. Criminal Subject Photo Request Response: Type-10 Photo Records.
Implementers may not introduce new elements or record types not supported by EBTS. All required elements and records must be present in a conforming instance document even if the implementers standards do not strictly enforce the requirement.
04/17/09 BIO-DOC-02261-1.5
8-56
9 FEEDBACK
04/17/09 BIO-DOC-02261-1.5
9-57