ISO/IEC 29120-1:2022

Information technology — Machine-readable test data for biometric testing and reporting — Part 1: Test reports

This document establishes: — machine-readable records for documenting the output of a biometric test; — formats for data that ISO/IEC 19795 series tests are required to report; and — an ASN.1 syntax for test reports. This document does not: — require, prohibit, or otherwise specify the format of biometric samples or templates used in a test; — require, prohibit or otherwise specify the encapsulation of biometric samples or templates used in a test; or — regulate metrics for tests. NOTE The reportable metrics are established in ISO/IEC 19795-1.

Technologies de l'information — Données d'essai lisibles par machine pour les rapports et les essais biométriques — Partie 1: Rapports d'essai

General Information

• Status: Published
• Publication Date: 27-Oct-2022
• ICS: 35.240.15 - Identification cards. Chip cards. Biometrics
• Technical Committee: ISO/IEC JTC 1/SC 37 - Biometrics
• Drafting Committee: ISO/IEC JTC 1/SC 37/WG 5 - Biometric testing and reporting
• Current Stage: 6060 - International Standard published
• Start Date: 28-Oct-2022
• Due Date: 19-Sep-2022
• Completion Date: 28-Oct-2022

Relations

• Revises: ISO/IEC 29120-1:2015 - Information technology — Machine readable test data for biometric testing and reporting — Part 1: Test reports
• Effective Date: 23-Apr-2020

Overview

ISO/IEC 29120-1:2022 specifies a machine-readable format for biometric test reports. Part 1 of the ISO/IEC 29120 series defines the ASN.1-based syntax and encoding rules to represent the output of biometric technology and scenario tests in a standard, machine-interpretable form. The standard supports documentary evidence of testing, verification of report authenticity, product registries, and reliable remote reliance on biometric products - while explicitly not prescribing biometric sample/template formats or test metrics.

Key topics and technical requirements

• ASN.1 syntax and object identifiers: Test reports are modelled as a BiometricTestReport SEQUENCE with typed content (technology test, scenario test, or signed test report). Specific ASN.1 object identifiers are defined for each content type.
• Encoding rules: Test reports shall be encoded using ASN.1 XML Encoding Rules (XER) or Basic Encoding Rules (BER) (ISO/IEC 8825‑4 and ISO/IEC 8825‑1).
• Structured data types: Types such as TestReportTechnology, ProductInformation and TestReportInformation define fields for product/provider details, versioning, and a sequence of condition-specific test results.
• Provider and product metadata: ProductInformation includes provider name, provider type (e.g., corporation, university, government), provider role (manufacturer, reseller, integrator), product name, functions, modality and optional descriptive fields.
• Conformance: A test report is conformant only if it meets all normative requirements of ISO/IEC 29120-1.
• Integrity and signatures: The standard includes data types for signed test reports to protect report integrity and authenticity.
• Scope limitations: The standard does not mandate biometric sample/template formats, encapsulation, or define test performance metrics (those are in ISO/IEC 19795-1).

Applications

• Standardizing automated exchange of biometric test results between laboratories, certification bodies, vendors and relying systems.
• Enabling test result registries and searchable archives of evaluated biometric products.
• Supporting automated verification of a product’s test status and authenticity in deployment or procurement workflows.
• Facilitating interoperability when documenting technology and scenario evaluations for regulatory or compliance use.

Who should use this standard

• Biometric test laboratories and conformance testing organizations
• Product vendors and integrators producing test evidence
• Certification and accreditation bodies maintaining product registries
• System architects and security teams integrating biometric components and relying on standardized test metadata

Related standards

• ISO/IEC 19795-1 and ISO/IEC 19795-2 (biometric performance testing and reporting)
• ISO/IEC 19785-3 (Biometric Exchange Formats - patron format)
• ISO/IEC 8825-1 / 8825-4 (ASN.1 BER and XER encoding rules)
• ISO 8601-1 (date/time representations)

Keywords: ISO/IEC 29120-1:2022, machine-readable test data, biometric testing, test reports, ASN.1, XER, BER, biometric test report, ISO/IEC 19795.

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 29120-1
Second edition
2022-10
Information technology — Machine-
readable test data for biometric
testing and reporting —
Part 1:
Test reports
Technologies de l'information — Données d'essai lisibles par machine
pour les rapports et les essais biométriques —
Partie 1: Rapports d'essai
Reference number
© ISO/IEC 2022
© ISO/IEC 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2022 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Conformance . 2
6 ASN.1 format . 2
6.1 Encoding rules . 2
6.2 ASN.1 object identifier for test report . 3
6.3 BiometricTestReport type . 3
6.4 Data types for technology tests . 4
6.4.1 Overview . 4
6.4.2 Product information. 4
6.4.3 Information about test report . 6
6.4.4 Test report under a specific condition . 8
6.5 Data types for scenario tests .13
6.5.1 Overview . 13
6.5.2 Test report under a specific condition . 13
6.6 Data types for signed test reports . 14
Annex A (normative) ASN.1 module for machine readable biometric test reports .16
Annex B (informative) Common elements .23
Annex C (informative) Test reports .29
Bibliography .36
iii
© ISO/IEC 2022 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC
list of patent declarations received (see https://patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 37, Biometrics.
This second edition cancels and replaces the first edition (ISO/IEC 29120-1:2015), which has been
technically revised.
The main changes are as follows:
— corrections have been made to data types and syntax.
A list of all parts in the ISO/IEC 29120 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
iv
© ISO/IEC 2022 – All rights reserved

Introduction
This document is intended to enhance the utility and usability of biometric test reports and data by
providing them in a common and machine-readable form. This document is intended to provide:
— documentary evidence that a product has been tested;
— a statement of authenticity of the test report;
— an ability to maintain a registry of products;
— a clear mechanism for maintaining product availability and certification status; and
— a relying system with information that allows it to depend on a biometric product used in a remote
authentication context.
This document is not intended to replace traditional biometric test reports. Indeed, as such texts are
essential to the complete documentation of a test, they are viewed as parents of the machine-readable
content defined in the ISO/IEC 29120 series and are explicitly referenced in these reports.
Accordingly, the parts of the ISO/IEC 29120 series establish requirements for, and define formats for,
signed test reports and biometric datasets as follows.
This document establishes machine-readable records for documenting the output of a biometric test.
This supports the documentary reporting requirements of ISO/IEC 19795-1 and ISO/IEC 19795-2. This
document is primarily intended to support scenario and technology tests. Additionally, interoperability
tests may be documented by a collection of ISO/IEC 29120-1 test reports (one for each tested
combination of components). The document also includes mechanisms to protect the integrity of the
test report. This assures a receiving system that the test information (date, laboratory, accreditation
body, manner of testing, conformance, test size, accuracy) can be relied upon and used appropriately.
As the various parts of the ISO/IEC 19795 series have been published, there has been an increasing
reliance on the correct conduct of tests and their documented outputs. Although the ISO/IEC 19795 series
includes extensive disclosure and reporting requirements, it does not establish definitive data formats
for those pieces of information. Other data concerning the commissioning, accreditation and conducting
of tests can also be valuable to consumers of the test reports. In addition, this document is intended to
benefit users of biometric tests via improved:
— conformance to testing standards,
— reliability (via automation of relevant activities), and
— comparability of test results.
v
© ISO/IEC 2022 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 29120-1:2022(E)
Information technology — Machine-readable test data for
biometric testing and reporting —
Part 1:
Test reports
1 Scope
This document establishes:
— machine-readable records for documenting the output of a biometric test;
— formats for data that ISO/IEC 19795 series tests are required to report; and
— an ASN.1 syntax for test reports.
This document does not:
— require, prohibit, or otherwise specify the format of biometric samples or templates used in a test;
— require, prohibit or otherwise specify the encapsulation of biometric samples or templates used in
a test; or
— regulate metrics for tests.
NOTE The reportable metrics are established in ISO/IEC 19795-1.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 19795-1, Information technology — Biometric performance testing and reporting — Part 1:
Principles and framework
ISO/IEC 19795-2, Information technology — Biometric performance testing and reporting — Part 2:
Testing methodologies for technology and scenario evaluation
ISO/IEC 19785-3, Information technology — Common Biometric Exchange Formats Framework — Part 3:
Patron format specifications
ISO/IEC 8825-1, Information technology — ASN.1 encoding rules — Part 1: Specification of Basic Encoding
Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)
ISO/IEC 8825-4, Information technology — ASN.1 encoding rules — Part 4: XML Encoding Rules (XER)
ISO 8601-1, Date and time — Representations for information interchange — Part 1: Basic rules
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 19795-1 apply.
© ISO/IEC 2022 – All rights reserved

ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
4 Abbreviated terms
ASN abstract syntax notation
BDB biometric data block
BER Basic Encoding Rules
CDF cumulative distribution function
CMC cumulative match characteristic
DET detection error tradeoff
FAR false accept rate
FTA failure to acquire rate
FTE failure to enrol rate
FMR false match rate
FNIR false-negative identification error rate
FNMR false non-match rate
FPIR false-positive identification error rate
FRR false reject rate
GFAR generalized false accept rate
GFRR generalized false reject rate
IUT implementation under test
XER XML Encoding Rules
5 Conformance
A test report shall be conformant to this document if it meets all normative requirements of this
document.
6 ASN.1 format
6.1 Encoding rules
The test reports specified in this document shall be encoded using the XML Encoding Rules (XER)
[ISO/IEC 8825-4] or the Basic Encoding Rules (BER) [ISO/IEC 8825-1] of ASN.1.
© ISO/IEC 2022 – All rights reserved

6.2 ASN.1 object identifier for test report
The test report shall conform to the ASN.1 specification given in Annex A, excerpts of which appear in
the remaining subclauses of Clause 6.
MachineReadableBiometricTestingAndReportingTestReport {
iso(1) standard(0) mrtdbtr(29120) testReport(1) module(1) rev(0)
}
6.3 BiometricTestReport type
BiometricTestReport ::= SEQUENCE {
contentType CONTENT-TYPE.&id({ContentTypeBiometricTestReport }),
content  [0] EXPLICIT CONTENT-TYPE.&Type
({ContentTypeBiometricTestReport}{@contentType})
}
Type BiometricTestReport is composed of two components, contentType and content. The first
component contentType is an object identifier, which indicates the type of content in the second
component content. The value of contentType takes one of the following three values:
— id-estReportTechnology,
— id-testReportScenario,
— id-signedTestReport.
This is done by the following the definition of ContentTypeBiometricTestReport and those of
testReportTechnology, testReportScenario, and signedTestReport.
ContentTypeBiometricTestReport CONTENT-TYPE ::= { testReportTechnology |
testReportScenario | signedTestReport }

testReportTechnology CONTENT-TYPE ::= {
TestReportTechnology
IDENTIFIED BY id-testReportTechnology
}
testReportScenario CONTENT-TYPE ::= {
TestReportScenario
IDENTIFIED BY id-testReportScenario
}
signedTestReport CONTENT-TYPE ::= {
SignedTestReport
IDENTIFIED BY id-signedTestReport
}
Each of these content types shall correspond to the report of either the ISO/IEC 19795-2 technology,
scenario or signed test reports, repectively.
The object identifiers are defined as follows:
id-testReportTechnology OBJECT IDENTIFIER ::= {
iso(1) standard(0) mrtdbtr(29120) testReport(1) contentType(2) testReportTechnology(1)
}
id-testReportScenario OBJECT IDENTIFIER ::= {
iso(1) standard(0) mrtdbtr(29120) testReport(1) contentType(2) testReportScenario(2)
}
id-signedTestReport OBJECT IDENTIFIER ::= {
iso(1) standard(0) mrtdbtr(29120) testReport(1) contentType(2) signedTestReport(3)
}
© ISO/IEC 2022 – All rights reserved

6.4 Data types for technology tests
6.4.1 Overview
Type TestReportTechnology is a type to express results of the technology test. The first field version
is the version of this test report format of type MRTDBTRVersion. The second field targetInfo is of type
ProductInformation and gives information on the evaluated product. The third field testReportInfo
gives information about the test report of type TestReportInformation. The fourth part is a
sequence testReports of type TestReportTechnologyForOneCondition. Each element of this sequence
corresponds to a test result under a specific condition.
TestReportTechnology ::= SEQUENCE {
version    MRTDBTRVersion DEFAULT v0,
targetInfo    ProductInformation,
testReportInfo   TestReportInformation,
testReports    SEQUENCE OF TestReportTechnologyForOneCondition
}
MRTDBTRVersion ::= INTEGER { v0(0) } ( v0, . )

NOTE Annex C contains informative examples of the elements that can be encoded in the technology test
report.
6.4.2 Product information
6.4.2.1 Overview
Type ProductInformation has six fields and gives information about the tested product.
ProductInformation ::= SEQUENCE {
provider      Provider,
nameProduct   NameProduct,
description   VisibleString OPTIONAL,
functionProduct     SEQUENCE OF Function,
outputProduct   DataType OPTIONAL,
modalityProduct     Modality
}
NOTE Annex B contains an informative discussion on these and other elements.
6.4.2.2 Provider information
The first field provider is of type Provider and gives information about the provider of the tested
biometric product.
Provider ::= SEQUENCE {
nameProvider     Name,
typeProvider     TypeProvider,
roleProvider     RoleProvider,
contactInformation VisibleString OPTIONAL
}
The first field nameProvider identifies the name of the provider. Type Name for this field is specified in
ISO/IEC 9592-2.
The second field typeProvider shows the type of the provider and shall take a value chosen from the
values of type TypeProvider: non-profit, university, corporation, individual, government.
TypeProvider ::= ENUMERATED {
non-profit(1),
university(2),
corporation(3),
individual(4),
government(5)
}
© ISO/IEC 2022 – All rights reserved

The third field roleProvider shows the role of the provider and shall take a value chosen from the values
of type RoleProvider: manufacturer, reseller, integrator, other. manufacturer is for the role of the
entity responsible for the design or creation of the component. reseller is for the role of the entity
which packages or resells the component. integrator is for the role of the entity which may combine
components into a single atomic component.
RoleProvider ::= ENUMERATED {
manufacturer(1),
reseller(2),
integrator(3),
other(4)
}
The fourth field contactInformation, which is optional, shows the contact information of the provider,
such as the email address of the provider, in VisibleString.
6.4.2.3 Other information in product information
The second field nameProduct in type ProductInformation is of NameProduct and gives basic information
about the product.
NameProduct ::= SEQUENCE {
modelName   Name,
productCBEFF   Product OPTIONAL,
version   VersionProduct,
softwareVersion  VersionProduct,
firmwareVersion  VersionProduct
}
VersionProduct ::= INTEGER { v0(0) } ( v0, . )

The first field modelName in NameProduct is of type Name and identifies the product. The second field
productCBEFF is an optional field of type Product that, if used, shall conform to the requirements
given in ISO/IEC 19785-3. If the product is registered to a certain biometric organization, this field
may be used to identify the product. The third, fourth and fifth fields version, softwareVersion, and
firmwareVersion, are all of type VersionProduct and indicate the version of the product, the version of
the software of the product, the version of the firmware of the product respectively.
The third field description in type ProductInformation gives a complete unique description of
the component under the test in VisibleString. This field should be used to describe prototypes,
experimental models, use of biometric modalities not listed in ISO/IEC 19785-3, or to give additional
information about the biometric modality (e.g. for iris recognition in the visible spectrum).
The fourth field functionProduct in type ProductInformation expresses the function of the tested
product with type Function. Type Function is specified as follows:
Function ::= ENUMERATED {
acquisition(1),
enrolment(2),
verification(3),
identification(4),
...
}
The fifth field outputProduct in type ProductInformation expresses the data type of the output of
the tested product with type DataType. Type DataType consists of two fields, processedLevel and
purpose. The former takes a value which corresponds to raw data, intermediate data, processed data,
comparison score or comparison decision. The latter takes a value which corresponds to biometric
reference or biometric sample.
DataType ::= SEQUENCE {
processedLevel ProcessedLevel,
purpose  Purpose OPTIONAL
}
ProcessedLevel ::= ENUMERATED {
raw-data(1),
© ISO/IEC 2022 – All rights reserved

intermediate-data(2),
processed-data(3),
comparison-score(4),
comparison-result(5),
...
}
Purpose ::= ENUMERATED {
reference(1),
sample(2)
}
The sixth field modalityProduct in type ProductInformation indicates the modality of biometric data
which the tested product processes, with type Modality. Type Modality consists of a pair of fields,
type and subtype. type is mandatory if processedLevel in outputProduct takes neither comparison-
score nor comparison-result. The types BiometricType and BiometricSubtype are defined in
ISO/IEC 19785-3:2020, 6.2.
Modality ::= SEQUENCE {
type  BiometricType,
subtype BiometricSubtype OPTIONAL
}
6.4.3 Information about test report
Type TestReportInformation has four fields and gives information about the test report.
TestReportInformation ::= SEQUENCE {
testLabInformation   TestLabInformation,
compliantStandard   StandardDescription,
testReportIssuanceDate Date,
parentTestReport   ExternalDocument
}
The first field testLabInformation in type TestReportInformation identifies the test laboratory
conducting the test, with type TestLabInformation. Type TestLabInformation consists of two
fields: identificationTestLab of type IdentificationTestLab and accreditationStatus of type
AccreditationStatus.
TestLabInformation ::= SEQUENCE {
identificationTestLab IdentificationTestLab,
accreditationStatus AccreditationStatus
}
Type IdentificationTestLab has five fields of type VisibleString: nameLab to show the name of the
responsible laboratory, location to show location of the laboratory, optional testImplementor to show
the employee or representative who executed the test, testReportSignatory to show the employee or
representative assuring the integrity, correctness and completeness of the test, and contactInformation
to show the contact information for enquiries concerning the test report.
IdentificationTestLab ::= SEQUENCE {
nameLab    VisibleString,
location     VisibleString,
testImplementor   VisibleString OPTIONAL,
testReportSignatory  VisibleString,
contactInformation   VisibleString
}
AccreditationStatus ::= SEQUENCE {
accreditingBodies   SEQUENCE OF AccreditingBody,
scopeAccreditation   ScopeAccreditation OPTIONAL
}
AccreditingBody ::= SEQUENCE {
nameAccreditingBody VisibleString,
identifierCertificate OBJECT IDENTIFIER,
signatory      OCTET STRING
}
ScopeAccreditation ::= SEQUENCE OF AScopeAccreditation
© ISO/IEC 2022 – All rights reserved

AScopeAccreditation ::= ENUMERATED {
iso-iec19795-1:2006(1),
iso-iec19795-1:2021(2),
iso-iec19795-3(3),
iso-iec30107-4(4),
... }
The second field compliantStandard in type TestReportInformation indicates which testing
standards were used for the test with type StandardDescription. Type StandardDescription has four
fields: standardName in VisibleString to show the name of the standard, such as "Biometric Testing
and Reporting — Principles and Framework", standardNumber in VisibleString to show the series
number of the standard, such as "19795", standardPart in VisibleString to show the Part number of
the standard series, and standardPublicationDate of type Date to show the publication date of the
document.
Type Date is expressed in VisibleString with fixed length of 8 of form YYYYMMDD, in accordance with
ISO 8601-1.
StandardDescription ::= SEQUENCE {
standardName   VisibleString,
standardNumber  VisibleString,
standardPart      VisibleString,
standardPublicationDate Date
}
Date ::= VisibleString
-- conforms to ISO 8601-1
-- length = 8
-- fixed
-- YYYYMMDD
The third field testReportIssuanceDate in type TestReportInformation encodes the date on which
the test report was signed by the test laboratory official with type Date.
The fourth field parentTestReport in type TestReportInformation gives the information about
the non-machine-readable, traditional test report for complete human-readable documentation
of the test with type ExternalDocument. Type ExternalDocument consists of three mandatory fields
and five optional fields. The first field link of type URI expresses the URL where the document can
be referenced. The second field title of type VisibleString shows the title of the document. The
third and optional field authors of type SEQUENCE OF VisibleString shows the author or the group
of authors of the document. The fourth and optional field publisher of type VisibleString shows the
publisher of the document. The fifth and optional field editor of type VisibleString shows the editor
of the document. The sixth and optional field typeDocument of type TypeDocument shows the type of the
document: article, technical report, in proceedings, abstract, book, in book or collection. The seventh
and optional field publicationDate of type Date shows the publication date of the document. The eighth
field availability of type Availability shows the availability of the document: public, restricted,
unavailable or superseded.
ExternalDocument ::= SEQUENCE {
link   URI,
title   VisibleString,
authors  SEQUENCE OF VisibleString OPTIONAL,
publisher   VisibleString OPTIONAL,
editor    VisibleString OPTIONAL,
typeDocument  TypeDocument OPTIONAL,
publicationDate  Date OPTIONAL,
availability  Availability
}
TypeDocument ::= ENUMERATED {
article(1),
technical-report(2),
in-proceedings(3),
abstract(4),
book(5),
in-book(6),
collection(7)
© ISO/IEC 2022 – All rights reserved

}
Availability ::= ENUMERATED {
public(1),
restricted(2),
unavailable(3),
superseded(4)
}
6.4.4 Test report under a specific condition
6.4.4.1 Overview
Type TestReportTechnologyForOneCondition gives a set of information for a result of the technology
test under a given condition. TestReportTechnologyForOneCondition consists of four fields: corpusInfo
of type CorpusInformation, dateStarted of type Date, dateEnded of type Date, and testResult of type
SEQUENCE OF TestResult. The second and third are optional fields.
TestReportTechnologyForOneCondition ::= SEQUENCE {
corpusInfo  CorpusInformation,
dateStarted  Date OPTIONAL,
dateEnded   Date OPTIONAL,
testResult  SEQUENCE OF TestResult
}
6.4.4.2 Corpus information
Type CorpusInformation represents the information of the corpus which was used in the evaluation with
two fields: composition of type CorpusComposition and environInfo of type EnvironmentalInformation.
CorpusInformation ::= SEQUENCE {
composition   CorpusComposition,
environInfo   EnvironmentalInformation
}
In type CorpusComposition, the corpus is identified with the first field identifier of type OBJECT
IDENTIFIER. The second field nameCorpus of type VisibleString gives the name of the corpus. The third
field corpusStatistics of type CorpusStatistics gives statistical information of the corpus.
CorpusComposition ::= SEQUENCE {
identifier   OBJECT IDENTIFIER,
nameCorpus   VisibleString,
corpusStatistics  CorpusStatistics
}
Type CorpusStatistics consists of four fields. The first field corpusBasicStatistics of type
CorpusCrewBasicStatistics gives the statistical information common to corpus and crew.
The second field numSamples indicates the number of biometric samples in the test corpus. The
mean number of samples per person can be obtained by dividing this number by the number of
individuals numIndividuals in corpusBasicStatistics. The number of samples numSamples can
be used in computation of uncertainties. The third and fourth fields, samplesPerIndividualEnrol
and samplesPerIndividualProbe, are optional and indicate the number of enrolment samples per
individual and the number of probe samples per individual respectively. Both are expressed with type
SamplesPerIndividual.
CorpusStatistics ::= SEQUENCE {
corpusBasicStatistics    CorpusCrewBasicStatistics,
numSamples     INTEGER,
samplesPerIndividualEnrol SamplesPerIndividual OPTIONAL,
samplesPerIndividualProbe SamplesPerIndividual OPTIONAL
}
Type SamplesPerIndividual is used to exhaustively tabulate a value for each member of the volunteer
corpus. This type consists of four fields. The first field numSubjects indicates the number of subjects
in the sample. The second and third fields, mean and median, are computed over all subjects. These two
© ISO/IEC 2022 – All rights reserved

fields support applications that can potentially not need data on the entire distribution expressed in
distrSubjSample. The fourth field distrSubjSample is of type DistributionIntegerInteger, which
is defined as SEQUENCE OF ExpressionPointIntegerInteger. Type ExpressionPointIntegerInteger
consists of a pair of integers, subjectId and numberOfSamples. numberOfSamples expresses the number
of samples for the subjectId. For example, if 20 samples are given for subject ID 1, 30 samples for ID 2,
22 samples for ID 3, 16 samples for ID 4, 23 samples for ID 5, then distrSubjSample is ((1, 20), (2,30),
(3,22), (4, 16), (5, 23)).
SamplesPerIndividual ::= SEQUENCE {
numSubjects    INTEGER,
mean      INTEGER,
median      INTEGER,
distrSubjSample     DistributionIntegerInteger
}
DistributionIntegerInteger ::= SEQUENCE OF ExpressionPointIntegerInteger
ExpressionPointIntegerInteger ::= SEQUENCE {
subjectId      INTEGER,
numberOfSamples     INTEGER
}
Type CorpusCrewBasicStatistics is used to express corpusBasicStatistics in CorpusStatistics
and testCrewInfo in TestReportScenarioForOneCondition (see 6.4.1). This type consists of nine
fields. The former five fields, numIndividuals, numMales, numFemales, numIndividualsEnrol, and
numIndividualsVeriId, are of type INTEGER and indicate the number of unique individuals in the
test corpus/crew, that of male subjects, that of female subjects, that in the enrolment set, and that
in the verification or identification set, respectively. numIndividuals shall be equal to or greater
than numIndividualsEnrol and numIndividualsVeriId. For identification, numIndividualsVeriId
shall be the size of the population searched. The second and third fields are optional. The latter four
fields, ageDistrMale, ageDistrFemale, elapsDistr, and visitsDayDistr, are all optional and of type
InfoCumulativeDistribution. They express the table of proportions of the males whose age in years is
less than or equal to X, the table of proportions of the females whose age in years is less than or equal
to X, the table of proportions of the subjects for whom the number of the days between the visits is less
than or equal to T, and the table of proportions of the samples collected on the day less than or equal to
the n-th day, respectively.
CorpusCrewBasicStatistics ::= SEQUENCE {
numIndividuals  INTEGER,
numMales    INTEGER OPTIONAL,
numFemales  INTEGER OPTIONAL,
numOther    INTEGER OPTIONAL,
numUnknown  INTEGER OPTIONAL,
numIndividualsEnrol INTEGER,
numIndividualsVeriId INTEGER,
ageDistrMale    InfoCumulativeDistribution OPTIONAL,
ageDistrFemale  InfoCumulativeDistribution OPTIONAL,
elapsDistr  InfoCumulativeDistribution OPTIONAL,
visitsDayDistr  InfoCumulativeDistribution OPTIONAL
}
Type InfoCumulativeDistribution is used for tabulation and relevant information of the cumulative
distribution function of a random variable. The first and second fields, mean and median, are computed
over all xValues in cumulativeDistribution. These two fields support applications that do not
need data on the entire cumulative distribution expressed in cumulativeDistribution. The third
field cumulativeDistribution expresses the tabulation of the cumulative distribution with type
DistributionIntegerReal, which is defined as SEQUENCE OF ExpressionPointIntegerReal. Each
element of DistributionIntegerReal is a pair of xValue of type INTEGER and yValue of type REAL. An
element of type ExpressionPointIntegerReal expresses that the proportion of the values which are
less or equal to xValue is yValue. The elements shall appear in inceasing order in xValue. For example,
the expression of Table 1 in DistributionIntegerReal is ((0, 0), (1, 0), (2, 0.7), (3, 0.92), (4, 0.97), (5, 1)).
© ISO/IEC 2022 – All rights reserved

Table 1 — Example expression
xValue yValue
0 0
1 0
2 0.7
3 0.92
4 0.97
5 1
InfoCumulativeDistribution ::= SEQUENCE {
mean      INTEGER,
median      INTEGER,
cumulativeDistribution DistributionIntegerReal
}
DistributionIntegerReal ::= SEQUENCE OF ExpressionPointIntegerReal
ExpressionPointIntegerReal ::= SEQUENCE {
xValue INTEGER,
yValue REAL
}
To describe the environment of the corpus collection, type EnvironmentalInformation is specified. The
first field exceptionalCondition allows free text keywords indicating that the collection environment
was adverse. The second field celsiusTemp represents the temperature expressed in Celsius in which
the collection was performed. The third field dBNoise represents the ambient noise expressed in dB
in which the collection was performed. The fourth and optional field lightingInfo allows free text in
VisibleString to give the lighting information in which the collection was performed.
EnvironmentalInformation  ::= SEQUENCE {
exceptionalCondition   VisibleString,
celsiusTemp    REAL OPTIONAL, -- temperature
dBNoise     REAL OPTIONAL, -- ambient noise
lightingInfo     VisibleString OPTIONAL
}
6.4.4.3 Test result under a specific condition
To express a test result for a technology test, type TestResult is specified as follows. The component
shall be chosen according to what is tested, i.e. enrolment, acquisition, matching in verification or
matching in identification.
TestResult ::= CHOICE {
testResultEnrol    TestResultEnrol, -- enrolment
testResultAcquire TestResultAcquire, -- acquisition
testResultVerify TestResultVerify, -- verification
testResultIdentify TestResultIdentify -- identification
}
6.4.4.3.1 Test result for enrolment
If the test is on enrolment, testResultEnrol of type TestResultEnrol shall be the component. Type
TestResultEnrol consists of two fields: failureToEnrolRate and durationEnrol. The first field
failureToEnrolRate expresses FTE, the fraction of enrolment samples not converted into a template.
The second and optional field durationEnrol of type StatisticInformationSet gives statistical
information on enrolment. This type gives a fundamental set of statistical information common to
enrolment, acquisition, verification, and identification. The first field unitTime indicates the unit of time
used in the third to the eighth field, millisecond or second. The second field is optional and indicates the
number of measurements. Fields three to eight are optional and express the median, mean, minimum
value, maximum value, standard deviation and median absolute deviation of the value sets respectively.
TestResultEnrol ::= SEQUENCE {
failureToEnrolRate REAL,
© ISO/IEC 2022 – All rights reserved

durationEnrol  StatisticInformationSet OPTIONAL
}
StatisticInformationSet ::= SEQUENCE {
unitTime     UnitTime,
numberOfMeasurements INTEGER OPTIONAL,
median      REAL OPTIONAL,
mean      REAL OPTIONAL,
minimum   REAL OPTIONAL,
maximum   REAL OPTIONAL,
stdDev      REAL OPTIONAL,
medAbsDev     REAL OPTIONAL
}
UnitTime ::= ENUMERATED {
millisecond(1),
second(2)
}
6.4.4.3.2 Test result for acquisition
If the test is on acquisition, testResultAcquire of type TestResultAcquire shall be the component
in type TestResult. The type consists of failureToAcquireRate and optional durationAcquire of
StatisticInformationSet type. The first field failureToAcquireRate expresses FTA, the fraction of
acquisition samples not converted into a template.
TestResultAcquire ::= SEQUENCE {
failureToAcquireRate REAL,
durationAcquire    StatisticInformationSet OPTIONAL
}
6.4.4.3.3 Test result for verification
For the test on matching in verification, type TestResultVerify is specified. This type consists
of two fields: resultMatchVerify of type ResultMatchVerify and optional durationVerify of type
StatisticInformationSet. The first three fields of type ResultMatchVerify are all of type InfoDETCurve
and give information about three DET curves: infoDETFNMRFMR for the DET curve of FNMR and FMR;
infoDETFRRFAR for the DET curve of FRR and FAR; and infoDETGFRRGFAR for the DET curve of GFRR and
GFAR. The fourth field of type ResultMatchVerify is the distribution of comparison scores cmpScrDistr
of type DistributionRealReal.
TestResultVerify ::= SEQUENCE {
resultMatchVerify   ResultMatchVerify,
durationVerify    StatisticInformationSet OPTIONAL
}
ResultMatchVerify::= SEQUENCE {
infoDETFNMRFMR  InfoDETCurve OPTIONAL, -- pair of error types shall be fnmr-fmr
infoDETFRRFAR  InfoDETCurve OPTIONAL, -- pair of error types shall be frr-far
infoDETGFRRGFAR   InfoDETCurve OPTIONAL, -- pair of error types shall be gfrr-
gfar
cmpScrDistr  DistributionRealReal OPTIONAL
}
The first and second fields in type InfoDETCurve are the number of samples used in estimation of
Type I estimate and that of Type II estimate. The third field expressionDETCurve approximates a DET
curve with type InfoDETCurve. InfoDETCurve represents a curve with an arbitrary number of points
on the curve. Each point on the curve is expressed with ExpressionPointDETCurve, which is a triple
of the threshold threshold, the Type I error rate value typeIError, and the Type II error rate value
typeIIError.The sequence of points shall appear in increasing order in typeIError. If the threshold is
unknown, threshold shall take the value -1. If the threshold is unavailable, threshold shall take the
value 0.
InfoDETCurve ::= SEQUENCE {
numOfSamplesEstTypeIError INTEGER,
numOfSamplesEstTypeIIError INTEGER,
expressionDETCurve    ExpressionDETCurve
}
© ISO/IEC 2022 – All rights reserved

ExpressionDETCurve ::= SEQUENCE OF ExpressionPointDETCurve
ExpressionPointDETCurve ::= SEQUENCE {
threshold    REAL OPTIONAL, -- -1 for unavailable, -2 for unknown
typeIError  REAL,
typeIIError  REAL
}
Distribution of comparison score is expressed with type DistributionRealReal which is a sequence of
ExpressionPointRealReal. Each element of DistributionRealReal is a pair of xValue of type REAL and
yValue of type REAL. An element of type ExpressionPointRealReal expresses that the proportion of the
values which are less than or equal to xValue is yValue. The elements shall appear in inceasing order in
xValue.
DistributionRealReal ::= SEQUENCE OF ExpressionPointRealReal
ExpressionPointRealReal ::= SEQUENCE {
xValue REAL,
yValue REAL
}
6.4.4.3.4 Test result for identification
For the test on matching in identification, type TestResultIdentify is specified. This type
consists of two fields; the result of closed-set identification resultMatchClosedIdentify of type
ResultMatchClosedIdentify and the result of open-set identification resultMatchOpenIdentify of type
ResultMatchOpenIdentify where the latter is optional.
TestResultIdentify ::= SEQUENCE {
resultMatchClosedIdentify ResultMatchClosedIdentify,
resultMatchOpenIdentify   ResultMatchOpenIdentify OPTIONAL
}
NOTE Closed-set metrics are mandatory because, as rank-based statistics, they can always be computed.
Type ResultMatchClosedIdentify consists of three fields; cmcCurveClosed, srchExecDistr, and
durationClosedIdentify. cmcCurveClosed expresses the CMC curve of the test result with type
DistributionIntegerReal. srchExecDistr expresses the histogram of number of searches executed
in the closed-set identification. Type ExpressionHistogram represents a histogram with a sequence
of IntervalIntegerFrequency. The first and second fields, lowerLimit and upperLimit, represent
an interval, and the third field frequency represents the frequency on that interval. The elements
in ExpressionHistogram shall appear in inceasing order in lowerLimit. The last optional field
durationClosedIdentify expresses the statistics of closed-set identification search duration with type
StatisticInformationSet.
ResultMatchClosedIdentify ::= SEQUENCE {
cmcCurveClosed    DistributionIntegerReal,
srchExecDistr    ExpressionHistogram,
durationClosedIdentify StatisticInformationSet OPTIONAL
}
ExpressionHistogram ::= SEQUENCE OF IntervalIntegerFrequency
IntervalIntegerFrequency ::= SEQUENCE {
lowerLimit INTEGER,
upperLimit INTEGER,
frequency   INTEGER
}
Type ResultMatchOpenIdentify consists of five fields: the expression of the CMC curve
cmcCurveOpen, the number of searches with enroled mate srchExecDistrEnroled, the number of
searches with no enroled mate srchExecDistrNoEnroled, the information about the DET curve of
FNIR and FPIR infoDETCurveFNIRFPIR, and the statistics of open-set identification search duration
durationOpenIdentify where the fourth and fifth fields are optional. The types to express these fields
are as follows and as already defined.
ResultMatchOpenIdentify ::= SEQUENCE {
cmcCurveOpen      DistributionIntegerReal,
srchExecDistrEnroled   ExpressionHistogram,
© ISO/IEC 2022 – All rights reserved

srchExecDistrNoEnroled ExpressionHistogram,
infoDETCurveFNIRFPIR   InfoDETCurve OPTIONAL,
-- pair of error types shall be fnir-fpir
durationOpenIdentify   StatisticInformationSet OPTIONAL
}
6.5 Data types for scenario tests
6.5.1 Overview
Type TestReportScenario is the type to express the results of a scenario test. The first field version
is the version of this test report format of type MRTDBTRVersion. The second field targetInfos is a
sequence of type ProductInformation and gives information on the set of the tested products. The
third field testReportInfo gives
...