[0050] The preferred embodiments of the present invention will be further described in detail below in conjunction with the accompanying drawings:
[0051] This example provides an automatic authentication system for faces, fingerprints and ID cards for customs clearance, including:
[0052] The device management module is used to load the device library plug-in, form the device plug-in list, and obtain the device feature data list of the existing device library;
[0053] A fingerprint module, which collects fingerprint information through a fingerprint identification device, and matches the fingerprint information through characteristic data in the device library management module;
[0054] A face module, which collects a face picture through a camera, and matches the face picture through feature data in the device library management module;
[0055] An ID card module, which collects ID card information through an ID card reader, and matches the ID card information with feature data in the device library management module;
[0056] The customs clearance authentication module is used to provide a data interface for the customs clearance system to realize the acquisition of the comparison results of fingerprint pictures, face pictures, and ID card information by the customs clearance system;
[0057] Wherein, the device management module uses a dynamic link library to implement device integration and interface calling by editing project engineering codes.
[0058] Such as figure 1 As shown, this example preferably includes a standard interface service layer, a device plug-in driver layer, and a device layer. The standard interface service layer includes a face recognition interface, an ID card recognition interface, and a fingerprint recognition interface. The device plug-in driver layer includes a camera plug-in. Driver, ID card reader plug-in driver and fingerprint recognition device plug-in driver. The device layer includes a camera, ID card reader and fingerprint recognition device. The camera is connected to the face recognition interface through the camera plug-in driver. The ID card reader is connected to the ID card recognition interface via the ID card reader plug-in driver, and the fingerprint recognition device is connected to the fingerprint recognition interface via the fingerprint recognition device plug-in driver. The feature data in the device library management module refers to the feature data included in fingerprint information, face pictures and ID card information, specifically including fingerprint feature data, face feature data, ID card feature data, etc.; the fingerprint feature The data includes fingerprint features such as patterns, pattern areas, core points, and triangle points; the facial feature data includes feature components of feature points such as mouth, nose, and eyes, and includes Euclidean distance, curvature, and angle between feature points, etc. The characteristic data of the ID card includes characteristic data such as name, ethnicity, place of origin, date of birth, home address and validity period of the ID certificate.
[0059] The device layer in this example includes data collection hardware devices such as cameras, ID card readers, and fingerprint recognition devices. The fingerprint recognition devices include fingerprint collection and recognition devices such as fingerprint recognition devices; the device plug-in driver layer is targeted at various manufacturers , Different brands and different types of device plug-ins are provided in the form of a DLL dynamic link library in the automatic authentication system. The DLL dynamic link library implements data communication and device integration operations with the acquisition hardware device; the standard interface service layer includes The face recognition interface, ID card interface and fingerprint recognition interface of the unified call interface.
[0060] The device management module described in this example automatically loads the device library plug-in, forms a device plug-in list, and obtains the device feature data list of the existing device library; automatically scans the computer USB port, collects the feature data of the hardware device external to the computer, and collects the feature data of the hardware device according to the device feature data Match the device library plug-in, and perform device initialization and self-checking work according to the general interface after successful matching.
[0061] The fingerprint module in this example matches the fingerprint image collected by the fingerprint recognition instrument with the characteristic data in the device library management module. The fingerprint module identifies the characteristic points according to the fingerprint characteristic point coordinate system, and saves the characteristic point data values. The fingerprint characteristic data corresponding to the fingerprint picture includes pattern, pattern area, core point, triangle point, etc. The fingerprint module obtains the comparison quality value by comparing the fingerprint characteristic data, and judges whether the fingerprint comparison is passed according to the preset fingerprint comparison quality value.
[0062] Fingerprint comparison includes fingerprint image processing, pattern extraction processing, feature extraction and matching recognition. Fingerprint image processing uses penetrating light to scan the finger to form a bright and dark fingerprint image, and automatically calculate adjustment parameters to obtain a fingerprint image; pattern extraction processing is to perform area detection on the fingerprint image, perform direction estimation and image binarization, And extract the pattern data of the fingerprint; feature extraction and matching recognition are to extract the image features of the fingerprint into the form of feature data, and compare them according to the stored feature data template, and judge whether the matching is successful according to the reasonable threshold of fingerprint feature data, fingerprint feature data threshold Generally, it is an empirical value obtained from a comparison test using a large amount of fingerprint data, which can be preset in advance and modified according to the actual situation.
[0063] The face module in this example matches the feature data of the device library management module with the face image collected by the camera. The face module automatically detects the quality of face image collection, locates the contour through the position of the mouth, nose and eyes, and extracts feature components, including the Euclidean distance, curvature and angle between feature points. The face module comparison is based on the similarity of feature points, and judges whether the comparison is passed according to the preset similarity threshold.
[0064] Face recognition includes: face image acquisition and detection, face image preprocessing, face image feature extraction, and matching and recognition. Face image acquisition uses a camera to capture face images; face detection is used to preprocess face images to calibrate the position and size of the face; face image preprocessing is to perform grayscale images based on the results of face detection Transformation, histogram equalization and filtering; face image feature extraction is the extraction of visual features, pixel statistical features, face image transformation coefficient features and face image algebraic features and other feature information, to perform face feature modeling; face matching and Recognition is to compare the extracted face image feature data with the feature template stored in the database, and judge whether the matching is successful according to a reasonable threshold of the face feature data. The threshold of the face feature data is generally obtained by comparing a large amount of face data. An empirical value of can be preset in advance and modified according to actual conditions.
[0065] The ID card module described in this example matches the ID card information collected by the ID card reader through the feature data of the device library management module. In this example, the facial feature data and fingerprint feature data are compared with the facial features and fingerprint features on the ID card through the matching of the personal ID, and it has been judged whether the personal ID is consistent.
[0066] The device integration provision method in this example is preferably that the device plug-in is provided to the device library in the form of a windows operating system DLL. The user can develop the device plug-in DLL that meets the interface by himself, and the device library supports the device plug-in that meets the interface requirements. The development tools for design integration are preferably developed using Visual C++2013 and Visual C++2015, and the development tools need to be installed first. Browser requirements preferably support Chrome54 and above, and support web access.
[0067] The process of editing the project engineering code described in this example to achieve device integration includes the following steps:
[0068] Step S1, open the project project, preferably also open the basic device information (such as DevBase.h) to derive a device plug-in class CDevIdentity (ie DevIdentity.cpp), in the project engineering code function (such as GetDevInfo () function, that is, get device information function) Fill in manufacturer and equipment information;
[0069] Step S2, initialize the API interface of the manufacturer's device by importing the manufacturer's device function, for example, import the function in the manufacturer's device dll in the InitDev() function for initialization;
[0070] Step S3, call the manufacturer's API interface to read the data, and format the read data;
[0071] Step S4, calling the manufacturer's API interface to end the operation, for example, calling the manufacturer's API interface in CloseDev() to end the operation.
[0072] In step S1 in this example, while filling the manufacturer and device information, the unique ID value of the device (such as dif.DevId value) is added to the device type list (such as enum DEV_TYPE) of the basic device information (such as DevBase.h) .
[0073] In step S2 in this example, when a new error code needs to be added, the error code code value (such as m_nErrCode value) is added to the device error code list (such as enum DEV_ERRCODE) of the device basic information (such as DevBase.h).
[0074] In step S3 in this example, the manufacturer API interface is called in ReadData() to read the data and formatted into JSON, TEXT and/or XML. In this example, JSON format is preferred, that is, the read data is formatted into JSON format. Sub-object, and then the main program will encapsulate the JSON format sub-object again.
[0075] The process of editing project engineering code to implement interface call in this example includes the following steps:
[0076] Step A1, when calling the device information, obtain the device name, manufacturer, model and version information;
[0077] Step A2, initialize the device when the service is turned on;
[0078] Step A3, turn off the device when the service is closed;
[0079] Step A4, obtain the last error code and error record when an error occurs;
[0080] Step A5, reading data when receiving a data reading request;
[0081] Step A6, write data when new data is received;
[0082] Step A7: When the fingerprint feature code, face feature code or ID card information is read, the feature data in the device library management module is called for matching.
[0083] That is to say, when developing the device dll, this example is developed according to the unified base class interface specification defined by common/DevBase.h. The detailed process is as follows:
[0084] //Get device name, manufacturer, model, version information, each dynamic library must provide
[0085] //Called when getting DLL device related information
[0086] virtual void GetDevInfo(DevInfo&dif)=0;
[0087] //Initialize the device
[0088] //Unified call when the service is started
[0089] virtual bool InitDev()=0;
[0090] //Close the device
[0091] //Unified call when the service is closed
[0092] virtual bool CloseDev()=0;
[0093] //Get the last error code
[0094] //Called when an error occurs
[0095] virtual int GetLastErrCode(){return m_nErrCode;};
[0096] //Function: Read data (JSON format)
[0097] //Called when the browser requests to read data
[0098] virtual int ReadData(int nType,char*pBuffer,int nBufLen,intnReadTimeOut=30000,DATA_TYPE dType=DT_JSON)=0;
[0099] //Function: write data
[0100] virtual int WriteData(int nType,char*pBuffer,int nBufLen,intnReadTimeOut=30000){return 0;};
[0101] //Function: Fingerprint comparison
[0102] //Called when reading fingerprint feature code and comparing
[0103] virtual int Match(int nType,char*pFeature,char*pTemplet,int nLevel=3){return0;};
[0104] virtual int Fun1(int,void*,int,void*){return 0;};
[0105] virtual int Fun2(int,int&,void*,void**){return 0;};
[0106] The unified interface adjustment process in this example is as follows:
[0107] => Service start
[0108] => Initialize device DLL (InitDev/GetDevInfo)
[0109] => Responding to browser requests (ReadData/WriteData/Match/GetLastErrCode)
[0110] => Close the device DLL (CloseDev)
[0111] => Close service
[0112] The device plug-in test process in this example is: copy the device plug-in to the device library, and after the device is connected, initialize the test. If the function test is passed, the device plug-in development is no problem.
[0113] In step A2 in this example, initializing the device includes the following sub-steps:
[0114] Step A21, the automatic device control plug-in loading process is used to automatically recognize and load fingerprint, face recognition and ID card devices from the device plug-in library;
[0115] Step A22, the automatic equipment state self-checking process, used to realize the automatic detection of the equipment state;
[0116] Step A23, the automatic recovery of the abnormal state of the equipment is used to realize the automatic recovery of the abnormal state of the equipment;
[0117] Step A24, the device plug-in library provides automatic plug-in matching for face recognition devices;
[0118] Step A25, the device plug-in library realizes automatic plug-in matching to the fingerprint collection device;
[0119] Step A26, the device plug-in library realizes automatic plug-in matching of the ID card collection device.
[0120] Such as figure 2 As shown, this example also provides an automatic authentication method for customs clearance face, fingerprint, and ID card, which is characterized in that it is applied to the above-mentioned customs clearance face, fingerprint, and ID card automatic authentication system, and includes the following steps:
[0121] Step B1: After opening, collect customs clearance personnel information, and perform characteristic data comparison, if the comparison passes, skip to step B2, otherwise return to continue collecting customs clearance personnel information;
[0122] Step B2: Send the ID card information, fingerprint information and face pictures of the customs clearance personnel to the customs clearance system for registration, feedback the successful authentication and end the authentication process of the customs clearance personnel.
[0123] More specific, such as image 3 As shown, in the step B1, the process of collecting customs clearance personnel information and performing feature comparison includes the following sub-steps:
[0124] Step B11, collect the ID information of the customs clearance personnel, including data such as name, ethnicity, native place, date of birth, home address and validity period of the ID certificate;
[0125] Step B12: Send the ID card information to the customs clearance system, and read the registered fingerprint feature data and face image corresponding to the ID card information of the customs clearance person;
[0126] Step B13: Collect fingerprint information of customs clearance personnel;
[0127] Step B14, perform feature matching between the collected fingerprint information and the registered fingerprint feature data, if passed, skip to step B15, otherwise return to step B11;
[0128] Step B15: Collect the face picture of the customs clearance personnel, and send the collected face picture to the customs clearance system for face comparison with the registered face image (such as face feature comparison), if the comparison is passed, jump to Step B2, otherwise return to step B11.
[0129] More specifically, the automatic authentication method for the face, fingerprint and ID card of the customs clearance in this example includes: the customs clearance system collects the ID card information of the customs clearance person, and reads the fingerprint feature data and facial features registered by the customs clearance person according to the ID card information Data (such as face images); the customs clearance system collects the fingerprint characteristics of the customs clearance personnel, and compares them with the fingerprint characteristics data registered by the customs clearance personnel. If the comparison passes, the next step is to proceed, otherwise the comparison fails to be sent to the customs clearance system, and the customs clearance The personnel’s authentication process is over; the customs clearance system collects the personnel’s face pictures and compares them with the registered face images, such as comparing the facial feature data. If the comparison is passed, the identity verification of the personnel in the customs clearance system will be reported as successful, otherwise If the verification fails to be sent to the customs clearance system, the certification process of the customs clearance personnel ends.
[0130] In the ID card reader, the request method is implemented through ReadData, and the process of responding to data is as follows:
[0131] {
[0132] "PeopleName":"***",
[0133] "PeopleSex":"Female",
[0134] "PeopleIDCode":"******************",
[0135] "PeopleNation":"Chinese",
[0136] "PeopleBirthday":"19881118",
[0137] "PeopleAddress":"***********************",
[0138] "StartDate":"20110330",
[0139] "EndDate":"20210330",
[0140] "Department":"**********",
[0141] "SexCode":"2"
[0142] "NationCode":"1"
[0143] }
[0144] In this example, the fingerprint template is generated in the fingerprint acquisition device such as the fingerprint identification device, and the request method is realized through ReadData. The process of responding to the successful data is as follows:
[0145] {
[0146] "Templet":"FAR5HBDReyAAAjpvcAAAhFKAgAARg8AA..."
[0147] }
[0148] In this example, the return value of the fingerprint acquisition device such as the fingerprint identification device is described as Templet: fingerprint template data.
[0149] In this example, the method for requesting fingerprint characteristic data collected by fingerprint acquisition devices such as fingerprint identification devices and comparison is implemented by Match, and the process of responding to successful data is as follows:
[0150] {
[0151] "Match":"success",
[0152] "Feature":"FAR5HBDReyAAAjpvcAAAhFKAgAARg8AA..."
[0153] }
[0154] In this example, the matching return value of the fingerprint acquisition device such as the fingerprint identification device is described as Match: fingerprint comparison result (success/failure); Feature: fingerprint feature code data.
[0155] To sum up, this example uses the dynamic link library to integrate face recognition, fingerprint comparison and ID card information reading into the customs clearance process by editing the project engineering code, which solves the need for customs personnel to compare the customs personnel’s eyes to the customs clearance personnel in the prior art. There are problems such as low efficiency and high error due to the identity information. Through the mode of first registration and then comparison, the use of information technology and means to compare the face, fingerprint and ID card information of customs clearance personnel has improved the information operation It can also reduce the degree of participation in the subjective judgment of customs personnel, improve its safety, reliability, integration and automation, and improve the efficiency of customs clearance certification.
[0156] The above content is a further detailed description of the present invention in conjunction with specific preferred embodiments, and it cannot be considered that the specific implementation of the present invention is limited to these descriptions. For those of ordinary skill in the technical field to which the present invention belongs, a number of simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as belonging to the protection scope of the present invention.
