|
US$6074.00 ยท In stock
Delivery: <= 15 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 32629-2016: Information technology -- Biometric BioAPI interworking protocol
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 32629-2016 | English | 6074 |
Add to Cart
|
15 days [Need to translate]
|
Information technology -- Biometric BioAPI interworking protocol
| Valid |
GB/T 32629-2016
|
PDF similar to GB/T 32629-2016
Basic data | Standard ID | GB/T 32629-2016 (GB/T32629-2016) | | Description (Translated English) | Information technology -- Biometric BioAPI interworking protocol | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L70 | | Classification of International Standard | 35.040 | | Word Count Estimation | 320,351 | | Date of Issue | 2016-04-25 | | Date of Implementation | 2016-11-01 | | Quoted Standard | GB/Z 15629.1-2000; GB/T 16262.1-2006; GB/T 30267.1-2013; ISO/IEC 19785-1-2006; ISO/IEC 19785-3-2007; ISO/IEC 19794-1; ISO/IEC 19794-2; ISO/IEC 19794-3; ISO/IEC 19794-4; ISO/IEC 19794-5; ISO/IEC 19794-6; ISO/IEC 19794-7; ISO/IEC 19794-8; ISO/IEC 19794-9; I | | Adopted Standard | ISO/IEC 24708-2008, IDT | | Regulation (derived from) | National Standard Announcement No | | Issuing agency(ies) | General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China | | Summary | This standard specifies the syntax, semantics, and coding of BIP messages so that BioAPI-compliant applications can request BioAPI-compliant BSPs across nodes or cross-process boundaries to perform biometric identification operations and be able to receive remote BSP primary event notifications. 1.2 This standard also specifies the architecture and behavioral extensions of the BioAPI framework to support the creation, processing, transmission and reception of BIP messages. A BioAPI framework conforming to this standard (the "BIP Enable Framework") can create, process, send, and receive BIP messages that are closely related to the BioAPI function call and callback. The outgoing BIP message can be generated and sent by the framework as part of the call to the caller or callback. | GB/T 32629-2016: Information technology -- Biometric BioAPI interworking protocol---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Information technology - Biometric BioAPI interworking protocol
ICS 35.040
L70
National Standards of People's Republic of China
Information technology biometrics application program interface
Of the interworking agreement
(ISO /IEC 24708..2008, IDT)
2016-04-25 released
2016-11-01 implementation
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China
China National Standardization Management Committee released
Directory
Preface III
Introduction IV
1 Scope 1
2 normative reference document 1
3 Terms and definitions 2
4 acronym 4
5 agreement 5
6 Compliance 5
7 BIP Architecture 7
8 Remote GUI Event Notification
9 System Configuration Example 12
10 BIR format 15
11 BIP endpoint, application and BSP logo 15
12 BIP Exchange Overview 16
General Provisions
14 BIP Message Syntax
15 BioAPI and BIP Type 26
16 Functions defined in BioAPI and corresponding BIP messages 62
17 The callback function defined in BioAPI and the corresponding BIP message 152
18 Concept Table 168
19 C pointer variable and the corresponding ASN.1 component conversion (1)
20 C pointer variable and the corresponding ASN.1 component conversion (2) 187
21 C pointer variable and the corresponding ASN.1 component conversion (3) 187
The initialization and checking of C pointer variables without the corresponding ASN.1 component
23 The UUID 188 of the host endpoint and BSP product is determined by the UUID of the BSP
24 determines the host endpoint and the original BSP handle 188 through the local BSP handle
25 Convert BSP UUID 188
26 conversion BSP handle 189
27 handles the incoming function call 189 by exchanging the request/response BIP message pair from the endpoint
28 The incoming request BIP message 189 is processed by an internal BioAPI function call
29 informs the unit of events to zero or more users
30 informs the GUI to select the event to the user 191
31 informs the user of the GUI status event
32 informs the GUI process event to the user 193
33 can not convert the C value of 195
Appendix A (normative) TCP/IP protocol binding specification
Appendix B (Normative Appendix) Discovery and Declaration of TCP/IP Protocol Binding Specification
Appendix C (normative) Specification for SOAP/HTTP protocol bindings
Appendix D (informative) Minimum requirements for simple systems
Appendix E (informative) Scenario Application Examples for BioAPI Interworking Protocols 278
Appendix F (normative) formal module of ASN.1
Reference 315
Foreword
This standard is drafted in accordance with the rules given in GB/T 1.1-2009.
This standard uses the translation method equivalent to ISO /IEC 24708..2008 "Information technology biometric identification application program interface interoperability
Agreement "(English version).
And the normative reference in this standard international documents are consistent with the relationship between China's documents are as follows.
--- GB/T 26237 (all parts) Information technology Biometric identification Data interchange format [ISO /IEC 19794 (all ministry
Minute)]
GB/T 28826.1-2012 Information technology - Public biometric identification interchange format framework - Part 1. Data element specification
Fan (ISO /IEC 19785-1..2006, MOD)
This standard has made the following editorial changes.
--- in the normative reference documents, with the equivalent of international standards GB /Z15629.1-2000 instead of ISO /IEC TR8802-
1..1997;
--- in the normative reference document, with the equivalent of international standards GB/T 16262.1-2006 instead of ISO /IEC 8824-1..2002;
--- in the normative reference document, with the equivalent of international standards GB/T 16263.2-2006 instead of ISO /IEC 8825-2..2002;
- in the normative reference document, with the equivalent of international standards GB/T 30267.1-2013 instead of ISO /IEC 19784-
1..2006;
- In the normative reference file, the following files not referenced in the standard text are deleted. ITU-TRecommendation
X.667 (2004) | ISO /IEC 9834-8..2005, ITU-TRecommendation X.681 (2002) | ISO /IEC
ISO /IEC 8824-3..2002, ITU-TREC-2,.2002, ITU-TRecommendation X.682 (2002)
ISO /IEC 8824-4..2002, ITU-TRECommendation X.693 (2001)
ISO /IEC 8825-4..2002, ITU-T Recommendation X.693 (2001) /Amd.1 (2003) |
ISO /IEC 8825-4..2002/Amd.1..2004, IETFRFC791 (1981), IETFRFC793 (1981), IETF
RFC1945 (1996), IETFRFC2616 (1999), IETFRFC2818 (2000);
--- The original data in the standard Appendix G modified as a reference.
Please note that some of the contents of this document may involve patents. The issuer of this document does not assume responsibility for the identification of these patents.
This standard is proposed and centralized by the National Information Technology Standardization Technical Committee (SAC/TC28).
This standard drafting unit. China Electronic Technology Standardization Research Institute, Zhongxing Electronics Co., Ltd., Nanjing La Corrono Information Technology
Limited company, Fuzhou Zhongxing Electronics Co., Ltd., Qingdao Star Microelectronics Co., Ltd.
The main drafters of this standard. Huo Hongwen, Zhang Yundong, Cui Guoqin, Pan Hailang, Feng Jing, Zhang Yannong, Qiu Song, Ma Wei, Pan Wang, Zhang Yuan, Qiu Yaqin.
Introduction
This standard BioAPI Interworking Protocol (BIP) specifies the syntax, semantics and coding of a set of messages (BIP messages) that conform to BioAPI
Applications can perform biometric identification at the BioAPI Biometric Services Provider (BSP) across nodes or across process boundary requests
Operation, and can receive remote BSP primary event notification. This standard also specifies support for the creation, processing, transmission and reception of BIP messages
The architecture and behavior of the BioAPI framework (see GB/T 30267.1-2013).
The BIPs set forth in this standard are designed to enable compliance with this standard to be implemented without having to support the full functionality of the BioAPI framework. This standard is defined
Several classes of varying degrees of conformance make it possible to provide support for BioAPI-compliant or BioAPI-compliant BSPs when it is not possible or desirable
In case of holding, it is possible to create a lightweight implementation that complies with this standard.
The protocol information specified in this standard adopts the ASN.1 marking method (see GB/T 16262.1-2006).
Chapters 7 through 11 provide an informative overview and provide a normative definition from Chapter 12 (including some appendices).
Chapter 7 describes the BIP architecture.
Chapter 8 describes the mechanism for remote GUI event notification.
Chapter 9 gives examples of system configuration using BIP.
Chapter 10 describes the format of biometric data converted by BIP.
Chapter 11 describes the BIP endpoint, application, and BSP identification.
Chapter 12 outlines BIP message exchange.
Chapter 13 contains general provisions for other chapter calls.
Chapter 14 specifies the general syntax of BIP messages.
Chapter 15 specifies the mapping between the BioAPI type and the corresponding ASN.1 type as the BIP message component.
Chapter 16 specifies the syntax of some BIP messages, as well as the receipt of a BioAPI function call or a call to a BioAPI function
BIP message when the operation.
Chapter 17 specifies the syntax of some BIP messages, as well as the receipt of a BioAPI function callback or a callback to the BioAPI function
BIP message when the operation.
Chapter 18 specifies the concept tables used in the implementation.
Chapters 19 through 33 contain specific provisions for other chapter calls.
Appendix A is a normative appendix that specifies the BIP TCP/IP binding.
Appendix B is a normative appendix that specifies additional specifications for BIP TCP/IP bindings.
Appendix C is a normative appendix that specifies the SOAP/HTTP binding for BIP.
Appendix D is an informative appendix that gives the minimum requirements for a simple system.
Appendix E is an informative appendix that provides examples of scenarios that may use BIP.
Appendix F is a normative appendix that contains the BIP complete ASN.1 specification.
Information technology biometrics application program interface
Of the interworking agreement
1 Scope
1.1 This standard specifies the syntax, semantics and coding of BIP messages so that BioAPI-compliant applications can be used across nodes or across process boundaries.
The BioSPI-compliant BSP performs biometric identification operations and is able to receive remote BSP primary event notifications.
Note. Local and remote nodes or processes can contain BSPs that provide the storage and retrieval, processing, or alignment of such biometric information records,
Or to collect biometric samples from one or more biometric sensors. A single node or process may contain both access to remote BSPs (one or more)
Multiple) applications, as well as BSPs that are accessed by remote applications (one or more).
1.2 This standard also specifies the architecture and behavioral extensions of the BioAPI framework to support the creation, processing, transmission and reception of BIP messages. symbol
The standard BioAPI framework (ie "BIP Enabled Framework") can be created, processed, sent and received with BioAPI function calls and callback close
Associated BIP message. The outgoing BIP message can be generated and sent by the framework as part of the handle of the incoming call or callback. pass
The incoming BIP message, like the received call or callback, can cause the framework to perform operations.
1.3 This standard explicitly allows a software entity ("General BIP Entity") that is not necessarily a "BIP Enabled Framework" to create, process, send, and
Receive BIP message.
Note. This provision makes it possible to create a case where it is not possible or required to support BioAPI-compliant or BioAPI-compliant BSPs
Lightweight implementation in accordance with this standard. BIP messages created and sent in a generic BIP entity are created and sent with a BIP enabled framework
BIP messages, the outside can not see any difference. However, the BIP-enabled framework should perform both BIP messages and BioAPI function calls comprehensively and correctly
Callback, and there is no such requirement for a generic BIP entity (see Chapter 6).
1.4 This standard specifies the use of several common transport protocols for BIP messaging between a pair of software entities ("BIP Endpoints").
1.5 Standardization of biometric data blocks (raw, intermediate state or processed biometric samples) is not standardized in this standard
Inside.
Note. The standardization of such formats is specified by ISO /IEC 19794.
1.6 biometric information records (each record contains one or more biometric data blocks and identification information and other meta information)
Standardization is not within the scope of this standard.
Note. The standardization of elements of this type of format is defined by ISO /IEC 19785-1..2006, which also includes a large number of standardized biometric information records
Type of specification.
1.7 The alignment algorithm for biometrics and verification is beyond the scope of this standard.
1.8 The definition of a security mechanism is outside the scope of this standard, but this standard specifies a number of secure transport protocol bindings to support BIP endpoints
Security exchange.
1.9 The classification, determination and performance requirements of the biometric identification system are beyond the scope of this standard.
1.10 This standard specifies the first edition of the BioAPI Interworking Protocol (BIP).
1.11 This standard only supports version 2.1 of BioAPI as defined in ISO /IEC 15507-1-2013.
2 normative reference documents
The following documents are indispensable for the application of this document. For dated references, only the dated edition applies to this article
Pieces. For undated references, the latest edition (including all modifications) applies to this document.
GB /Z15629.1-2000 Information technology - Telecommunications and information exchange between systems - Local and metropolitan area network specific requirements
Part 1. Overview of LAN Standards (ISO /IEC TR8802-1..1997, IDT)
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 32629-2016_English be delivered?Answer: Upon your order, we will start to translate GB/T 32629-2016_English as soon as possible, and keep you informed of the progress. The lead time is typically 11 ~ 15 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 32629-2016_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 32629-2016_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.
|