1、BSI Standards Publication BS ISO/IEC 30106-2:2016 Information technology Object oriented BioAPI Part 2: Java implementationBS ISO/IEC 30106-2:2016 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 30106-2:2016. The UK participation in its preparation was en
2、trusted to Technical Committee IST/44, Biometrics. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The Britis
3、h Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 75178 3 ICS 35.040 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 April
4、 2016. Amendments/corrigenda issued since publication Date T e x t a f f e c t e dBS ISO/IEC 30106-2:2016 Information technology Object oriented BioAPI Part 2: Java implementation Technologies de linformation Objet orient BioAPI Partie 2: Mise en oeuvre Java INTERNATIONAL STANDARD ISO/IEC 30106-2 Re
5、ference number ISO/IEC 30106-2:2016(E) First edition 2016-03-15 ISO/IEC 2016 BS ISO/IEC 30106-2:2016ii ISO/IEC 2016 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2016, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced o
6、r 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 ISOs member body in the country of the requester. ISO c
7、opyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 30106-2:2016(E)BS ISO/IEC 30106-2:2016ISO/IEC 30106-2:2016(E)Foreword vi Introduction vii 1 Scope . 1 2 Normative references 1 3 BioAPI Java
8、 package structure . 1 3.1 Package org.bioapi . 1 3.1.1 Package description 1 3.1.2 Structure . 1 3.2 Package org.bioapi.data . 2 3.2.1 Package description 2 3.2.2 Structure . 2 4 Data types and constants . 2 4.1 Class ACBioParameters 2 4.1.1 Description 2 4.1.2 Method summary 2 4.2 Class BFPListEle
9、ment . . 2 4.2.1 Description 2 4.2.2 Method summary 3 4.3 Class BFPSchema. 3 4.3.1 Description 3 4.3.2 Method summary 3 4.4 Class BIR . 4 4.4.1 Description 4 4.4.2 Method summary 4 4.5 Class BSPSchema . 9 4.5.1 Description 9 4.5.2 Method summary 9 4.6 Class candidate 12 4.6.1 Description .12 4.6.2 M
10、ethod summary .12 4.7 Class DataTypes 13 4.7.1 Description .13 4.7.2 Enumerations 14 4.8 Class date 20 4.8.1 Description .20 4.8.2 Method summary .21 4.9 Class FrameworkSchema 22 4.9.1 Description .22 4.9.2 Method summary .23 4.10 Class GUIBitmap .24 4.10.1 Description .24 4.10.2 Method summary .24
11、4.11 Class IdentifyPopulation 24 4.11.1 Description .24 4.11.2 Method summary .24 4.12 Class PopulationMember 25 4.12.1 Description .25 4.12.2 Method summary .25 4.13 Class RegistryID 25 4.13.1 Description .25 4.13.2 Method summary .25 4.14 Class SecurityProfileType .26 4.14.1 Description .26 ISO/IE
12、C 2016 All rights reserved iii Contents PageBS ISO/IEC 30106-2:2016ISO/IEC 30106-2:2016(E)4.14.2 Method summary .26 4.15 Class UnitList .27 4.15.1 Description .27 4.15.2 Method summary .27 4.16 Class UnitListElement 27 4.16.1 Description .27 4.16.2 Method summary .27 4.17 Class UnitSchema .28 4.17.1
13、 Description .28 4.17.2 Method summary .28 4.18 Class UUID 30 4.18.1 Description .30 5 Object oriented interfaces for supporting BioAPI_Units .30 5.1 General 30 5.2 Interface archive .30 5.2.1 Description .30 5.2.2 Method summary .31 5.3 Interface comparison .34 5.3.1 Description .34 5.3.2 Method su
14、mmary .34 5.4 Interface processing 36 5.4.1 Description .36 5.4.2 Method summary .36 5.5 Interface sensor .37 5.5.1 Description .37 5.5.2 Method summary .38 6 BFP level .39 6.1 Interface BFP .39 6.1.1 Description .39 6.1.2 Imported interfaces 39 6.1.3 Method summary .40 7 BSP level .42 7.1 Interface
15、 BSP 42 7.1.1 Description .42 7.1.2 Imported interfaces 42 7.1.3 Method summary .42 8 Framework level 49 8.1 Interface ComponentRegistry .49 8.1.1 Description .49 8.1.2 Method summary .50 8.2 Interface framework .51 8.2.1 Description .51 8.2.2 Inherited interfaces 51 8.2.3 Method summary .52 9 Appli
16、cation interaction .56 9.1 class BioAPIException extends Exception 56 9.1.1 Description .56 9.1.2 Constructor summary 56 9.1.3 Method summary .57 9.2 GUI callback functions .57 9.2.1 Description .57 9.2.2 Callback interface specification .58 10 BSP Interaction 61 10.1 Interface BSPEventListener 61 1
17、0.1.1 Method summary .61 iv ISO/IEC 2016 All rights reservedBS ISO/IEC 30106-2:2016ISO/IEC 30106-2:2016(E)11 BFP interaction 62 11.1 Interface BFPEnumerationListener .62 11.1.1 Method summary .62 11.2 Interface BFPEventListener 62 11.2.1 Method summary .62 11.3 Interface BFPGUIProgressEventListener
18、63 11.3.1 Method summary .63 Annex A (informative) Java requirements .64 Annex B (informative) Calling sequence examples and sample code .65 ISO/IEC 2016 All rights reserved vBS ISO/IEC 30106-2:2016ISO/IEC 30106-2:2016(E) Foreword ISO (the International Organization for Standardization) and IEC (the
19、 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 particu
20、lar 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. In the field of information technology, ISO and IEC have establi
21、shed a joint technical committee, ISO/IEC JTC 1. 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
22、 document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). 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
23、 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). Any trade name used in this document is information given for the convenience o
24、f users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Suppl
25、ementary information The committee responsible for this document is ISO/TC JTC1, Information technology, Subcommittee SC 37, Biometrics. ISO/IEC 30106 consists of the following parts, under the general title Information technology Object oriented BioAPI: Part 1: Architecture Part 2: Java implementat
26、ion Part 3: C# implementationvi ISO/IEC 2016 All rights reservedBS ISO/IEC 30106-2:2016ISO/IEC 30106-2:2016(E) Introduction In this part of ISO/IEC 30106, an application programming interface expressed in Java language is specified. Java is intended to be a simple, general-purpose, object oriented p
27、rogramming language that is aimed at enabling programmers to quickly build a wide range of applications for multiple platforms. This Java implementation allows an easy use of Java BSPs, Java-based application servers or Java applets. Therefore, it is the best way to write desktop and web application
28、s/services and this specification provides an advanced and well-designed remote framework. Although the best practices of Java programming states that variables should be written in smallcase letters, in the case of symbols, such as BSP or BFPs, it has been kept as uppercase letters. ISO/IEC 2016 Al
29、l rights reserved viiBS ISO/IEC 30106-2:2016BS ISO/IEC 30106-2:2016Information technology Object oriented BioAPI Part 2: Java implementation 1 Scope This part of ISO/IEC 30106 specifies an interface of a BioAPI Java framework and BioAPI Java BSP, which will mirror the corresponding components, speci
30、fied in ISO/IEC 30106-1. The semantic equivalent of this standard is maintained in this part of ISO/IEC 30106. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the ed
31、ition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 301061, Information technology BioAPI for object oriented programming languages Part 1: Architecture 3 BioAPI Java package structure The BioAPI Java interface will b
32、e divided into several packages. The following is the package structure: package org.bioapi: contains functionality to manage units, BSPs, BFPs, the Framework and Applications; package org.bioapi.data: contains all the data structures. 3.1 Package org.bioapi 3.1.1 Package description This package co
33、ntains all the components responsible for managing and executing the functionality of BioAPI. Component Registry interface is also defined in this package. 3.1.2 Structure The description of this namespace is given explaining a bottom-up structure. In Clause 4, the interfaces needed to be implemente
34、d for each of the Unit types are explained. It is important to note that such interfaces do not refer to an implemented class by itself, as the accessible class will either be the Biometric Service Provider (BSP) or the Biometric Function Provider (BFP), but the specifications in such clause are com
35、mon to the methods and properties to be added to the implemented BSP and/or BFP classes. This will be followed by the specification of the implementation of the BFP (Clause 5) and BSP (Clause 6) interfaces. These two interfaces provide the lower layer interoperability level, equivalent to the SPI an
36、d BFPI interfaces in ISO/IEC 19784-1. The higher layer of interoperability level is provided by the specification of the Framework (Clause 7, with the Framework Interface and the Component Registry) and the Application interaction (Clause 8, INTERNATIONAL ST ANDARD ISO/IEC 30106-2:2016(E) ISO/IEC 20
37、16 All rights reserved 1BS ISO/IEC 30106-2:2016ISO/IEC 30106-2:2016(E) with the specification of the Exceptions and Callback functions). This provides the equivalence to the API interface in ISO/IEC 19784-1. 3.2 Package org.bioapi.data 3.2.1 Package description This package contains all data structu
38、res needed for the implementation of OO BioAPI. 3.2.2 Structure Several data structures are provided to comply with the requirements specified in this part of ISO/IEC 30106. All the BioAPI.Data namespace is specified in Clause 3, where all needed classes and enumerations are defined. This has to be
39、complemented to the constants defined in ISO/IEC 30106-1. 4 Data types and constants 4.1 Class ACBioParameters 4.1.1 Description Structure that provides the information that is used to generate ACBio instances. 4.1.2 Method summary 4.1.2.1 int getChallenge() Description: Return the challenge from th
40、e validator of a biometric verification when ACBio is used. This value shall be sent to the field controlValue of type ACBioContentInfor- mation in ACBio instances. Return value: The challenge from the validator of a biometric verification when ACBio is used. 4.1.2.2 int getInitialBPUIOIndexOutput()
41、 Description: Return the initial value of BPU IO index which is to be assigned to the output from the BioAPI Unit, BFP, or BSP when the ACBio instances are generated. The range between InitialBPUIOIndexOutput and SupremumBPUIOIndexOutput shall be divided into the number of BSP Units and BFPs which a
42、re inside the BSP and assigned to the BSP Units and BSPs. Return value: The initial value of BPU IO index. 4.1.2.3 int getSupremumBPUIOIndexOutput() Description: Return the supremum of BPU IO indexes which are to be assigned to the output from the BioAPI Unit , BFP, or BSP when the ACBio instances a
43、re generated. Return value: The supremum of BPU IO index. 4.2 Class BFPListElement 4.2.1 Description Identifies a BFP by category and UUID. A list is returned by a BSP when queried for the installed BFPs that it supports.2 ISO/IEC 2016 All rights reservedBS ISO/IEC 30106-2:2016ISO/IEC 30106-2:2016(E
44、) 4.2.2 Method summary 4.2.2.1 UUID getBFPID() Description: Return the UUID assigned to the BFP. Return value: UUID assigned to the BFP. 4.2.2.2 UnitCategoryType getUnitCategory() Description: Return the category of the units. Return value: Category of the units. 4.2.2.3 void setBFPID(UUID bfpID) De
45、scription: Set the UUID assigned to the BFP. Parameters: bfpID: UUID assigned to the BFP. 4.2.2.4 void setUnitCategory(UnitCategoryType unitCategory) Description: Set the category of the units. Parameters: unitCategory: category of the units. 4.3 Class BFPSchema 4.3.1 Description Represents the reco
46、rd in the component registry that defines the properties of the BFP installed in the system. 4.3.2 Method summary 4.3.2.1 String getBFPDescription() Description: Return a string containing a text description of the BFP. Return value: A string containing a text description of the BFP. 4.3.2.2 Vector
47、getBFPSupportedFormats() Description: Return a list the data formats that are supported by the BFP. Return value: A list the data formats that are supported by the BFP. 4.3.2.3 UUID getBFPUUID() Description: Return the BFP UUID Return value: BFP UUID 4.3.2.4 Vector getFactorsMask() Description: Retu
48、rn a list of the biometric types supported by the BFP. Return value: A list of the biometric types supported by the BFP. 4.3.2.5 byte getFWProperty( Description: Return the address and length of a memory buffer containing the BFP property. The format and content of the BFP property can either be spe
49、cified by a vendor or can be specified in a related standard. Return value: The address and length of a memory buffer containing the BFP property. ISO/IEC 2016 All rights reserved 3BS ISO/IEC 30106-2:2016ISO/IEC 30106-2:2016(E) 4.3.2.6 UUID getFWPropertyID() Description: Return the UUID of the format of the following BFP property. Return value: UUID of the format of the following BFP property. 4.3.2.7 String getPath() Description: Return a pointer to a string containing
