|
US$1169.00 · In stock
Delivery: <= 7 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 41903.4-2025: Information technology - Object oriented BioAPI - Part 4: C++ implementation
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 41903.4-2025 | English | 1169 |
Add to Cart
|
7 days [Need to translate]
|
Information technology - Object oriented BioAPI - Part 4: C++ implementation
| Valid |
GB/T 41903.4-2025
|
PDF similar to GB/T 41903.4-2025
Basic data | Standard ID | GB/T 41903.4-2025 (GB/T41903.4-2025) | | Description (Translated English) | Information technology - Object oriented BioAPI - Part 4: C++ implementation | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L71 | | Classification of International Standard | 35.240.01 | | Word Count Estimation | 58,570 | | Date of Issue | 2025-06-30 | | Date of Implementation | 2026-01-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 41903.4-2025: Information technology - Object oriented BioAPI - Part 4: C++ implementation---This is an excerpt. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.), auto-downloaded/delivered in 9 seconds, can be purchased online: https://www.ChineseStandard.net/PDF.aspx/GBT41903.4-2025
ICS 35.240.01
CCSL71
National Standard of the People's Republic of China
Information Technology Object-Oriented Biometric Recognition
Application Programming Interface Part 4.C Implementation
(ISO /IEC 30106-4.2019, MOD)
Released on June 30, 2025
Implementation on January 1, 2026
State Administration for Market Regulation
The National Standardization Administration issued
Table of Contents
Preface III
Introduction V
1 Scope 1
2 Normative references 1
3 Terms and Definitions 1
4 Abbreviations 1
5 BioAPIC General Requirements 2
6 Data types and constants 2
6.1 Basic Data Types 2
6.2 ACBioparameters Class 9
6.3 BFPListElement Class 9
6.4 BFPSchema Class 9
6.5 BIR Class 10
6.6 BSPSchema Class 11
6.7 Candidate Class 13
6.8 FrameworkSchema Class 13
6.9 GUIBitmap Class 13
6.10 IdentifyPopulation Class 14
6.11 PopulationMember Class 14
6.12 SecurityProfileType Class 15
6.13 UnitList Class 15
6.14 UnitListElement Class 16
6.15 UnitSchema Class 16
7 Support for BioAPI_Unit object-oriented interface 17
7.1 General requirements 17
7.2 IArchive Interface 17
7.3 IComparision Interface 21
7.4 IProcessing Interface 23
7.5 ISensor Interface 25
8 BFP layer 26
8.1 IBFP Interface Description 26
8.2 Importing Interface 26
8.3 Attribute Summary 26
8.4 Event Summary 26
8.5 Method Summary 26
9 BSP layer 29
9.1 IBSP Interface Description 29
9.2 Importing Interfaces 29
9.3 Attribute Summary 29
9.4 Event Summary 29
9.5 Method Summary 29
10 frame layer 36
10.1 IComponentRegistry Interface 36
10.2 IFramework Interface 37
11 Application Interaction 41
11.1 BioAPIException class.Exception 41
11.2 Callback Function 42
Appendix A (Informative) Call Sequence Examples and Sample Code 47
A.1 Reference Implementation 47
A.2 API Architecture 47
Reference 48
Preface
This document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for standardization work Part 1.Structure and drafting rules for standardization documents"
Drafting.
This document is Part 4 of GB/T 41903 "Information technology object-oriented biometric recognition application programming interface".
GB/T 41903 has published the following parts.
--- Part 1.Architecture;
--- Part 2.Java implementation;
---Part 3.C
7.1.5.2 to 7.1.5.7 in ISO /IEC 30106-4.2019;
--- Chapter 9 corresponds to Chapter 8 of ISO /IEC 30106-4.2019, of which 9.1 corresponds to Chapter 8 of ISO /IEC 30106-4.2019
8.1, 9.2~9.5 correspond to 8.12~8.15, 9.5.2~9.5.25 in ISO /IEC 30106-4.2019
8.1.51 to 8.1.5.24 of ISO /IEC 30106-4.2019;
--- Added "8.5.1" and "9.5.1" numbering;
--- Deleted the "9.1.1" clause number.
The technical differences between this document and ISO /IEC 30106-4.2019 and their reasons are as follows.
--- Replaced ISO /IEC 30106-1 with the normative reference GB/T 41903.1 to adapt to my country's technical conditions (see Chapter 1,
6.1.1.1, 6.1.1.2, 6.5.1, 11.1.1, 11.2.1);
--- Replaced ISO /IEC 30106-2 with the normative reference GB/T 41903.2 to adapt to my country's technical conditions (see Section 5
chapter);
--- Replaced ISO /IEC 30106-3 with the normative reference GB/T 41903.3 to adapt to my country's technical conditions (see Section 5
chapter);
--- Added normative reference GB/T 13000-2025 to adapt to my country's coded character standards (see 6.4.2, 6.6.2,
6.8.2,11.2.2.2,11.2.2.3,11.2.2.4);
--- Added normative references to GB 18030 to facilitate adaptation to my country's coded character standards (see 6.4.2, 6.6.2, 6.8.2,
11.2.2.2,11.2.2.3,11.2.2.4);
--- Added the "bfpEnumeration" parameter (see 10.2.4.1);
--- Added the "notifyCalback" parameter (see 10.2.4.2).
The following editorial changes have been made to this document.
--- Corrected the name of the second enumeration constant in 6.1.1.15 to "RequestPayload";
--- Corrected "String" in 6.6.2 Property Summary to "string";
---Corrected "svector" to "vector" in 6.4.2 Attribute Summary;
---Corrected the second "intunitID" of the "BIRCreateTemplate" method in 7.4.2.2;
--- Corrected "ICandidate" to "Candidate" in 7.3.2.3, 7.3.2.4, 9.5.13, and 9.5.14;
--- Corrected the parameter "bfpNotifyCalback" in 9.5.2 to "bspNotifyCalback";
---Corrected "BFPEventCalback" in 11.2.2.1 to "BSPEventCalback", "bfpUUID" to
"bspUUID";
Please note that some of the contents of this document may involve patents. The issuing organization of this document does not assume the responsibility for identifying patents.
This document was proposed and coordinated by the National Technical Committee for Information Technology Standardization (SAC/TC28).
This document was drafted by. Hangzhou Mingguang Microelectronics Technology Co., Ltd., China Electronics Technology Standardization Institute, Zhejiang Jiuchan IoT Technology
Co., Ltd., Shenzhen Aiku Intelligent Technology Co., Ltd., Beijing Wanlihong Technology Co., Ltd., Lenovo Zhongtian Technology Co., Ltd., Beijing Institute of Technology
School, Shengdian Century Technology Co., Ltd., Guangzhou Tongda Automotive Electric Co., Ltd., Guangzhou GRG Yuntong Intelligent Technology Co., Ltd.,
Shenzhen Chuangyingxin Industrial Co., Ltd., Guangdong Chuangneng Technology Co., Ltd., Shanghai Point and Surface Intelligent Technology Co., Ltd., Hangzhou Jinglian Wenke
Technology Co., Ltd., Guangdong Jiulian Technology Co., Ltd., Shanxi Sanyouhe Smart Information Technology Co., Ltd., Rockchip Technology Group
Co., Ltd., Shenzhen Yuntian Lifei Technology Co., Ltd., Xiamen Enki Technology Co., Ltd., Jiangsu Changshu Rural Commercial Bank Co., Ltd.
Co., Ltd., China Mobile Communications Group Fujian Co., Ltd., Enbase Technology Co., Ltd., GRG Banking Group Co., Ltd., Zhejiang
Xinghan Information Technology Co., Ltd., Shenzhen Dingzhi Communication Co., Ltd., Guangdong Zhongke Zhenheng Information Technology Co., Ltd., Changchun Boli
Electronic Technology Co., Ltd., Shengshi Technology Co., Ltd., Shanghai University of Electric Power, Beijing University of Civil Engineering and Architecture, Jianxin Financial Technology Co., Ltd.
Shenzhen Xujing Digital Technology Co., Ltd., Shenzhen Yinhe Communication Technology Co., Ltd., Hangzhou Denghong Technology Co., Ltd., Shenzhen Tesu
Network Technology Service Co., Ltd., Huizhou University, Guangdong Coretech Technology Co., Ltd., Xiamen University, Shenzhen Guanqun Electronics Co., Ltd.,
East China Branch of China Electronics Standardization Institute.
The main drafters of this document are. Jin Ze, Geng Li, Su Liwei, Li Yang, Shen Zheming, Yang Chunlin, Li Qingmei, Shen Bowen, Huang Zhi, Song Jiwei, Deng Fang,
Zhong Chen, Zhang Xiaoliang, Qiao Mingming, Hu Wenmao, Lao Zhongjian, Jie Yongsheng, Dou Kai, Zeng Qingning, Pan Xiaoguang, Li Jun, Lei Yun, Shen Wenzhong, Huang Congmin, Ling Jun,
Xue Xueqin, Rao Xue, He Yuhong, Liu Weiming, Zhang Bujian, Lin Xiaoqing, Liang Erzhen, Zou Xiangyong, Yang Jingfeng, Yang Xu, Zhang Lihua, Wang Heping, Shao Jie,
Tian Qichuan, He Weiming, Zhuo Tao, Huang Chongfan, Chen Shuaibin, Ke Laman, Qiu Meilan, Xu Qitui, Li Xiaochao, Ye Weihong, and Zhou Yang.
introduction
The BioAPI described in C language is suitable for applications written in C, and also suitable for applications written in C.
However, function-based languages like C do not map easily to object-oriented programming languages.
Using the C version of the API within an application is inconvenient and requires complex programming constructs to be introduced into application development.
The object-oriented version of BioAPI is designed to improve the productivity of software practitioners, while retaining the object-oriented programming
model.
For Java, the standard object-oriented BioAPI version allows BSPs loaded into Java-based application servers to execute
In these application servers, it is more convenient to use the object-oriented BioAPI than the C++
The BioAPI version is more convenient.
Another area where the standard object-oriented BioAPI version is used is in small computing devices based on object-oriented languages.
In devices (like the large application servers mentioned above), an object-oriented BioAPI framework and object-oriented BSP will be more
Their C counterparts are more suitable.
Object-oriented application programming interface requires a unified architecture, and the implementation languages include Java, C
--- Part 1.Architecture. Specifies the general architecture of the object-oriented BioAPI, with the aim of standardizing different
The BioAP implemented in the language of the same language has the same structure and the components have conceptual equivalence.
--- Part 2.Java Implementation. Specifies the object-oriented BioAPI Java framework and various interfaces, as well as data types and constants
The purpose is to guide the implementation of interfaces in Java language.
---Part 3.C
GB/T 13000-2025 Information technology – Universal Coded Character Set (UCS) (ISO /IEC 10646.2020, MOD)
Note. There is no technical difference between the referenced content of GB/T 13000-2025 and the referenced content of ISO /IEC 10646.2020.
GB 18030 Information Technology Chinese Coded Character Set
GB/T 41903.1 Information technology - Object-oriented biometric recognition application programming interface - Part 1.Architecture
(GB/T 41903.1-2022,ISO /IEC 30106-1.2016,MOD)
GB/T 41903.2 Information technology - Object-oriented biometric recognition application programming interface - Part 2.Java implementation
(GB/T 41903.2-2022,ISO /IEC 30106-2.2020,MOD)
GB/T 41903.3 Information technology - Object-oriented biometric recognition application programming interface - Part 3.C
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 41903.4-2025_English be delivered?Answer: Upon your order, we will start to translate GB/T 41903.4-2025_English as soon as possible, and keep you informed of the progress. The lead time is typically 4 ~ 7 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 41903.4-2025_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 41903.4-2025_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.
|