KR20240058625A - Access and attendance management system-connected service system established by mobile id-based face recognition edging node implementation - Google Patents

Abstract

A system for building an access and attendance management system linked service through the implementation of a mobile ID-based facial recognition edging node is launched. Hyperledger Fabric-based blockchain host server where the Hyperledger Fabric-based blockchain ledger is stored; A user mobile terminal that generates a mobile ID card, stores it in a blockchain ledger of the Hyperledger Fabric-based blockchain host server, and displays the mobile ID card; an edging node access terminal that recognizes the mobile ID displayed on the user's mobile terminal, requests authentication, and allows or denies predetermined access according to the authentication result of the displayed mobile ID; At the request of the edging node access terminal, an integrated access management server is configured to connect to the Hyperledger Fabric-based blockchain host server to authenticate the mobile ID card and feed back the mobile ID authentication result to the edging node access terminal in real time. According to the above-described configuration, the facial feature point information of the user or visitor is downloaded and stored in advance on the edging node access terminal provided at the door, etc., and is configured to immediately authenticate by comparing the facial feature point information of the visitor directly photographed on the edging node access terminal, It has the effect of reducing the enormous load occurring on the backend server and performing facial authentication of visitors quickly and accurately.

Description

Access and attendance management system linked service construction system through mobile ID-based face recognition edging node implementation {ACCESS AND ATTENDANCE MANAGEMENT SYSTEM-CONNECTED SERVICE SYSTEM ESTABLISHED BY MOBILE ID-BASED FACE RECOGNITION EDGING NODE IMPLEMENTATION}

The present invention relates to a system for building access and attendance management system linked services. Specifically, it relates to a system for building access and attendance management system linked services through the implementation of a face recognition edging node. More specifically, it relates to mobile ID-based facial recognition edging. This is about a system for building access and attendance management system linked services through node implementation.

Previously, separate ID cards or certificates were issued offline to prove identity or various qualifications.

Recently, various identification cards have been implemented online, but there are limitations such as complex authentication technology being applied, difficulty linking with existing services, applicability only to specific terminals, and applicability only to certain limited user groups.

In particular, these ID cards have the problem that it is difficult to easily apply authentication methods and prove identity to immediately implement and provide various additional benefits and services to members of a specific organization.

The most effective way to prove the authenticity of an ID holder is the user's biometric information, and among them, facial recognition technology is the most intuitive, allowing ID holders as well as those requiring identification to work or transact with each other very conveniently and safely. In addition, various benefits provided to ID holders will be easily available.

Meanwhile, when authenticating an entrant through facial recognition, the face of the entrant is photographed at a terminal installed at the entrance. Previously, the terminal only took pictures of the visitor's facial information, and the captured facial information of the visitor was transmitted to the backend server in real time each time, and the backend server compared the face for authentication. In this case, the back-end server must carry a huge load because it must perform the facial recognition/authentication process of numerous visitors at the same time, so there is a problem in that the authentication speed is very slow and the accuracy is low.

In particular, in the case of facial recognition/authentication of users from multiple organizations or institutions, it can be considered virtually impossible to handle all of them on a single back-end server. Accordingly, a method must be found to perform the facial recognition/authentication process with maximum efficiency while maintaining security.

Public Patent Publication 10-2021-0141281 Public Patent Publication 10-2021-0090800

The purpose of the present invention is to provide a system for building access and attendance management system linkage services by implementing a mobile ID-based facial recognition edging node.

The system for building an access and attendance management system linked service through the implementation of a mobile ID-based facial recognition edging node according to the purpose of the present invention described above extracts the user's facial feature point information, recognizes the user's face, authenticates it, and based on the authentication result. It may be configured to include an edging node access terminal that directly allows or denies access, or allows or denies predetermined access by a command of the integrated access management server.

At this time, the edging node access terminal can be configured to complement the completeness of the unique user ID value by linking the extracted user's facial recognition biometric information with the blockchain host server.

And further includes an integrated access management server that connects to the Hyperledger Fabric-based blockchain host server at the request of the edging node access terminal, authenticates the mobile ID card, and feeds back the mobile ID authentication result to the edging node access terminal in real time. It can be configured to do so.

Additionally, a Hyperledger Fabric-based blockchain host server where the Hyperledger Fabric-based blockchain ledger is stored; It may be configured to further include a user mobile terminal that generates a mobile identification card, stores it in the blockchain ledger of the Hyperledger Fabric-based blockchain host server, and displays the mobile identification card.

According to the system for establishing an access and attendance management system linked service through the implementation of the mobile ID-based facial recognition edging node described above, facial feature point information of users or visitors is extracted in advance, downloaded, and stored on the edging node access terminal provided at the entrance door, etc., and stored in the edging node. By being configured to directly authenticate the visitor's facial feature point information captured directly on the access terminal, there is an effect of reducing the enormous load generated on the backend server and performing facial authentication of the visitor quickly and accurately.

Meanwhile, as long as the user takes a self-portrait on his or her smartphone, the mobile ID card of the affiliated organization is automatically generated and registered, allowing the user to conveniently obtain a mobile ID card at any time, and the affiliated organization can issue a mobile ID card separately. It has the effect of reducing the amount of work and costs.

In addition, the identity information through AI facial recognition-based biometric information is automatically changed every unit time to prevent the risk of hacking when accessing or connecting to a specific service, and a virtual QR is provided based on OTAC, which generates and provides a one-way random code. By generating a code or random number code and displaying it on the smartphone, identity verification can be performed using an OTAC-based QR code or an OTAC-based random number code that changes every unit time, and the risk of theft of these codes is eliminated. There is an effect that can be done.

In particular, even if primary access to the service system is provided using a user ID generated from the biometric characteristic value of the user terminal and an actual ID file stored only on the blockchain, additional secondary authentication using an OTAC-based code is required. Afterwards, by analyzing and constructing OTAC, it has the effect of reducing the possibility of forgery or falsification due to leakage or hacking of mobile ID cards.

Figure 1 is a block diagram of a system for establishing an access and attendance management system linked service through the implementation of a mobile ID card-based facial recognition edging node according to an embodiment of the present invention.
Figures 2 to 6 are detailed configuration diagrams of a system for establishing an access and attendance management system linked service through the implementation of a mobile ID card-based facial recognition edging node according to an embodiment of the present invention.
Figure 7 is an example diagram of an OTAC-based mobile identification card according to an embodiment of the present invention.

Since the present invention can be modified in various ways and can have various embodiments, specific embodiments will be illustrated in the drawings and detailed descriptions will be given for carrying out the invention. However, this is not intended to limit the present invention to specific embodiments, and should be understood to include all changes, equivalents, and substitutes included in the spirit and technical scope of the present invention. While describing each drawing, similar reference numerals are used for similar components.

Terms such as first, second, A, and B may be used to describe various components, but the components should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, a first component may be named a second component without departing from the scope of the present invention, and similarly, the second component may also be named a first component. The term and/or includes any of a plurality of related stated items or a combination of a plurality of related stated items.

When a component is said to be "connected" or "connected" to another component, it is understood that it may be directly connected to or connected to the other component, but that other components may exist in between. It should be. On the other hand, when it is mentioned that a component is “directly connected” or “directly connected” to another component, it should be understood that there are no other components in between.

The terms used in this application are only used to describe specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by a person of ordinary skill in the technical field to which the present invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and unless explicitly defined in the present application, should not be interpreted in an ideal or excessively formal sense. No.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the attached drawings.

Figure 1 is a block diagram of a system for establishing an access and attendance management system linked service through the implementation of a mobile ID card-based facial recognition edging node according to an embodiment of the present invention, and Figures 2 to 6 are a block diagram according to an embodiment of the present invention. This is a detailed diagram of the system for establishing access and attendance management system linked services through the implementation of a mobile ID-based facial recognition edging node. And Figure 7 is an example diagram of an OTAC-based mobile identification card according to an embodiment of the present invention.

Referring to Figures 1 to 6, the system for building an access and attendance management system linked service through the implementation of a mobile ID card-based facial recognition edging node according to an embodiment of the present invention is a hyperledger fabric-based blockchain host server ( 100), blockchain ledger design information database (200), user mobile terminal (300), visitor mobile terminal (400), user's organization server (500), visitor's organization server (600), edging node access terminal (edging node) It may be configured to include an access terminal) (700), an integrated access management server (800), and an affiliate server (900).

Hereinafter, the detailed configuration will be described.

The Hyperledger Fabric-based blockchain host server 100 may be configured to store the Hyperledger Fabric-based blockchain ledger 101.

Since the Hyperledger Fabric-based blockchain host server 100 is based on Hyperledger Fabric, a private blockchain ledger is stored, and a plurality of Hyperledger Fabric-based blockchain host servers 100 may be provided.

The cloud server 100A may be configured to store mobile ID cards. Mobile ID cards include military ID cards, employee ID cards, civil servant ID cards, and student ID cards, and can also include visit cards, pass cards, and various certificates.

The Hyperledger Fabric-based blockchain host server 100 or cloud server 100A can be configured to store all vacation cards, business trip confirmations, quarantine certificates, discount coupons or coupons from affiliates, etc. in connection with the mobile ID.

The blockchain ledger design information database 200 may be configured to store design information about the blockchain ledger 101 of the Hyperledger Fabric-based blockchain host server 100. A blockchain ledger based on Hyperledger Fabric must have predefined information about nodes or user terminals 300 that can access the blockchain, host information where the blockchain ledger is stored, and peer information.

The user mobile terminal 300 may be configured to generate a mobile ID card, store it in the blockchain ledger 101 and the cloud server 100A of the Hyperledger Fabric-based blockchain host server 100, and display the mobile ID card. Previously, when creating various ID cards, they were created under the supervision of an administrator terminal (not shown) or generated at the server end (not shown). However, in the present invention, the user directly creates a mobile ID card at the user terminal 300. It can be configured so that it can be used.

The user mobile terminal 300 includes a user information input module 301, a user information storage module 302, a mobile ID automatic generation module 303, a mobile ID storage module 304, and a mobile ID blockchain storage control module 305. , mobile ID search information database 306, cloud storage control module 307, camera module 308, user facial feature point information extraction module 309, user facial feature point information storage module 310, user facial feature point information upload module. (311), user authentication module 312, OTAC (one-time authentication code) real-time generation module 313, real-time terminal location information generation module 314, OTAC-based QR code generation module 315, OTAC-based random number code Generation module 316, mobile ID display control module 317, display 318, mobile ID BLE transmission control module 319, tagless BLE (Bluetooth low energy) module 320, visit link transmission request It may be configured to include a module 321.

Hereinafter, the detailed configuration will be described.

The user information input module 301 may be configured to receive user information.

The user information storage module 302 may be configured to store user information input from the user information input module 301.

The mobile ID automatic generation module 303 may be configured to automatically generate a mobile ID card including user information stored in the user information storage module 302.

The mobile ID storage module 304 may be configured to store the mobile ID automatically generated by the mobile ID automatic generation module 303.

The mobile ID blockchain storage control module 305 is configured to control the mobile ID automatically generated by the mobile ID automatic generation module 303 to be stored in the blockchain ledger 101 of the Hyperledger Fabric-based blockchain host server 100. It can be.

The mobile ID blockchain storage control module 305 can control the mobile ID card to be stored in the blockchain ledger 101 by referring to the design information of the blockchain ledger 101 pre-stored in the blockchain ledger design information database 200. there is.

The mobile ID search information database 306 is used to search the mobile ID stored in the blockchain ledger 101 of the Hyperledger Fabric-based blockchain host server 100 under the control of the mobile ID blockchain storage control module 305. It may be configured to store ID retrieval information.

Here, the search information may be configured to include location information and path information on the blockchain ledger 101 of the mobile ID. Location information is information about which Hyperledger Fabric-based blockchain host server 100 or which cloud server 100A the mobile ID card is stored on, and path information is used to search for and find the location information. It's information.

The cloud storage control module 307 can control the mobile ID automatically generated by the mobile ID automatic generation module 303 to be stored in the cloud server 100A.

The camera module 308 may be configured to take self-photographs of the user's face.

The user facial feature point information extraction module 309 may be configured to extract user facial feature point information from the user's face captured by the camera module 308.

The user facial feature point information storage module 310 may be configured to store the user facial feature point information extracted from the user facial feature point information extraction module 309.

The user facial feature point information upload module 311 may be configured to upload the user facial feature point information stored in the user facial feature point information storage module 310 to the user's organization server 500.

The user authentication module 312 is configured to perform a user authentication process through the authentication server 10 so that the user facial feature point information upload module 311 can upload the user facial feature point information to the user's organization server 500. You can. Here, the authentication server 10 may be a public authentication server or a telecommunication company authentication server.

The OTAC real-time generation module 313 may be configured to generate OTAC in real time using a pre-stored OTAC generation function. The OTAC creation function may be installed in advance during the process of installing the application on the user terminal 300.

The OTAC real-time generation module 313 includes a first code generation unit 313a, a second code generation unit 313b, a terminal unique code addition unit 313c, a first unit time count unit 313d, and an OTAC real-time generation unit ( 313e).

The OTAC real-time generation module 313 generates OTAC in real time at predetermined unit times, and the OTAC may be configured to be uniquely generated without duplicating other OTACs. For example, it can be uniquely created every unit of time within the range of 10,000 hours. In the case of existing OTP cards, the OTP number is easily leaked if the model name and serial number are leaked, but in the case of OTAC, it is leaked because it is not exposed on the display 318 of the user terminal 300 and there is no serial number. There is no risk of becoming

Hereinafter, the detailed configuration will be described.

The first code generator 313a may be configured to generate a first code indicating the location of the mobile ID card stored in the blockchain ledger 101 with reference to the mobile ID search information database 306.

The second code generator 313b may be configured to generate a second code indicating the path of the mobile ID stored in the blockchain ledger 101 with reference to the mobile ID search information database 306.

The terminal unique code adding unit 313c may be configured to add the terminal unique code of the user terminal 300.

The first unit time count unit 313d may be configured to generate a real-time unit time code in real time by performing a count every predetermined unit time. The unit time can be preset to 3 seconds, 1.5 seconds, 10 seconds, etc., and can also be set variably. Real-time unit time codes are generated differently for each unit of time and are not exposed on the display 318, so security is high. The unit time can be set when installing the application.

The OTAC real-time generation unit 313e includes the first code generated by the first code generation unit 313a, the second code generated by the second code generation unit 313b, and the terminal added by the terminal unique code addition unit 310c. It may be configured to generate OTAC in real time by combining the unique code and the real-time unit time code generated by the first unit time count unit 310d. There are no restrictions on the method of combination.

The real-time terminal location information generation module 314 may be configured to generate real-time terminal location information of the user mobile terminal 300. Since the real-time terminal location information of the user terminal 300 is real-time location information at the time of identity verification, it can be used to secure records of the affiliated organization's workplace, business trip location, etc.

The OTAC-based QR code generation module 315 is configured to generate an OTAC-based QR code containing the OTAC generated in real time by the OTAC real-time generation module 313 and the real-time terminal location information generated by the real-time terminal location information generation module 314. It can be.

At this time, since the OTAC-based QR code is generated based on OTAC that changes every unit of time, it is not a fixed code and may be generated differently every unit of time. Therefore, even if it is leaked, the risk of theft is very low. Since the unit time itself can be set to be very short, there is almost no possibility of theft.

The OTAC-based random number code generation module 316 is configured to generate an OTAC-based random number code containing the OTAC generated in real time by the OTAC real-time generation module 313 and the real-time terminal location information generated by the real-time terminal location information generation module 314. It can be. OTAC-based random number codes are also generated based on OTAC, which changes every unit of time, so there is no room for theft even if exposed.

The mobile ID display control module 317 displays the OTAC-based QR code generated by the OTAC-based QR code generation module 315 or the OTAC-based random number code generation module 316 on the mobile ID stored in the mobile ID storage module 304. It can be configured to control the display by adding an OTAC-based random number code. This mobile ID can be used as an access key or a system key for online access to the system.

The display 318 may be configured to display the mobile ID card under the control of the mobile ID display control module 317. Figure 7 shows an example of a mobile ID card displaying the user's face, and shows that it is used as a system key, access key, groupware key, etc. At this time, the mobile ID may be displayed together with an OTAC-based QR code or an OTAC-based random number code.

The mobile ID BLE transmission control module 319 adds the OTAC-based random number code generated by the OTAC-based random number code generation module 316 to the mobile ID stored in the mobile ID storage module 304 and transmits it to the edging node access terminal 700. You can control it to do so.

The tagless BLE module 320 may be configured to transmit the mobile identification card to the edging node access terminal 700 under the control of the mobile identification card BLE transmission control module 319.

The visit link transmission request module 321 may request that the user's organization server 500 generate a visit link to secure visitor facial feature point information in advance and transmit it to the visitor mobile terminal 400. That is, the user can send a visit link to a visitor who will visit the user's organization, and the visitor can upload the visitor's facial feature point information to the user's organization server 500 in advance through the visit link.

The visitor mobile terminal 400 is a terminal of a visitor who wants to visit the user's organization and meet the user.

The visitor mobile terminal 400 may be configured to generate a mobile ID card, store it in the blockchain ledger 101 and the cloud server 100A of the Hyperledger Fabric-based blockchain host server 100, and display the mobile ID card.

The visitor mobile terminal 400 includes a camera module 401, a visitor facial feature point information extraction module 402, a visitor facial feature point information storage module 403, a visit link reception module 404, a visitor authentication module 405, and a visitor/ It may be configured to include a visit destination information upload module 406, a visitor facial feature point information upload module 407, a display 408, and a tagless BLE module 409.

Hereinafter, the detailed configuration will be described.

The camera module 401 may be configured to take self-photographs of the visitor's face.

The visitor facial feature point information extraction module 402 may be configured to extract visitor facial feature point information from the visitor's face captured by the camera module 401.

The visitor facial feature point information storage module 403 may be configured to store the visitor facial feature point information extracted from the visitor facial feature point information extraction module 402.

The visit link receiving module 404 may be configured to receive a visit link from the user's organization server 500 .

The visitor authentication module 405 may be configured to perform an authentication process of a visitor through the authentication server 10.

When the visitor is authenticated in the visitor authentication module 405, the visitor/visiting destination information upload module 406 uploads the visitor/visiting destination information to the user's organization server 500 through the visiting link received from the visiting link receiving module 404. Can be configured to upload.

When the visitor is authenticated in the visitor authentication module 405, the visitor facial feature point information upload module 407 uploads the visitor feature point facial information to the user's organization server 500 through the visit link received from the visit link reception module 404. Can be configured to upload. Here, the visitor feature point facial information may be encrypted and stored in the user's organization server 500.

Meanwhile, the visitor mobile terminal 400 has a configuration for generating a visitor's mobile ID, a configuration for storing the mobile ID, a configuration for generating an OTAC-based QR code, an OTAC-based random number code, etc., and adding and displaying them to the visitor's mobile ID. It can be provided. These configurations correspond to the corresponding configurations of the user mobile terminal 300.

Display 408 may be configured to display a visitor's mobile identification card.

The tagless BLE module 409 may be configured to transmit the visitor's mobile identification card to the edging node access terminal 700.

The user's organization server 500 may be configured to transmit the member's facial feature point information or the visitor's facial feature point information to the edging node access terminal 500, while the visitor's visit result to the user's organization is sent to the visitor's affiliated organization. It can be configured to automatically forward to organization server 600.

Here, the user's organization server 500 is basically configured to receive the member's entry and exit results or system login results through the edging node access terminal 500, and store the history in the database to perform attendance management of the member. It can be.

The user's organization server 500 includes a user facial feature point information reception module 501, a user facial feature point information database 502, a visit link transmission module 503, a visitor/visiting destination information reception module 504, and a visitor facial feature point information reception module. Module 505, visit information database 506, member/visitor information transmission module 507, facial feature point information transmission module 508, edging node access terminal information database 509, control module 510, code authentication It may be configured to include a result/terminal location information receiving module 511, a code authentication result/terminal location information database 512, and an automatic visit result delivery module 513.

Hereinafter, the detailed configuration will be described.

The user facial feature point information receiving module 501 may be configured to receive user facial feature point information uploaded from the user facial feature point information upload module 311 of the user mobile terminal 300.

The user facial feature point information database 502 may be configured to store the user facial feature point information received from the user facial feature point information receiving module 501.

The visited link transmission module 503 may be configured to transmit a visited link to the visitor mobile terminal 400 according to a request from the visited link transmission request module 321 of the user mobile terminal 300.

The visitor/visiting destination information receiving module 504 may be configured to receive visitor/visiting destination information uploaded from the visitor/visiting destination information upload module 407 of the visitor mobile terminal 400. Here, the destination may be the user's organization.

The visitor facial feature point information receiving module 505 may be configured to receive visitor facial feature point information uploaded from the visitor facial feature point information upload module 407 of the visitor mobile terminal 400.

The visit information database 506 may be configured to store the visitor/visit location information received from the visitor/visit location information receiving module 504 and the visitor facial feature point information received from the visitor facial feature point information receiving module 505. Here, the visitor facial feature point information may be encrypted and stored and configured so that it cannot be viewed or edited separately.

The member/visitor information transmission module 507 may be configured to transmit member information or visitor information stored in the visit information database 506 to the corresponding edging node access terminal 700.

The facial feature point information transmission module 508 is configured to transmit the user facial feature point information stored in the user facial feature point information database 502 or the visitor facial feature point information stored in the visit information database 506 to the corresponding edging node access terminal 700. You can.

The edging node access terminal information database 509 may be configured to store edging node access terminal information in advance. Here, the edging node access terminal information is information about the edging node access terminal installed in the user's organization and may include installation location, IP address, MAC address, etc.

The control module 510 refers to the edging node access terminal information in the edging node access terminal information database 509 and transmits the user facial feature point information stored in the user facial feature point information database 502 to the corresponding edging node access terminal 700. It can be configured to control.

In addition, the control module 510 refers to the edging node access terminal information in the edging node access terminal information database 509 and provides the visitor facial feature points to the edging node access terminal 700 corresponding to the visiting destination information stored in the visit information database 506. It can be controlled to transmit information.

The code authentication result/device location information receiving module 511 may be configured to receive the mobile ID authentication result and real-time terminal location information from the integrated access management server 800.

The code authentication result/terminal location information database 512 may be configured to store the code authentication result and real-time terminal location information received from the code authentication result/terminal location information receiving module 511.

The visit result automatic transmission module 513 automatically delivers the visitor's visit result to the visitor's organization server 600 according to the code authentication result and real-time terminal location information received from the code authentication result/terminal location information reception module 511. It can be configured to do so.

The visitor's organization server 600 may be configured to transmit the visitor's facial feature point information to the user's organization server 500 and automatically receive the visit results from the user's organization server 500. Accordingly, the organization to which the visitor belongs can check whether the visitor has visited and the visit details. For example, you can check visitors' business trips or external meetings in real time.

The edging node access terminal 700 may be installed at the entrance of the user's organization, and may also be installed on a computer or other device of the user's organization for system login, etc.

For example, it may be attached to the entrance door of a military unit or a security area, may be attached to an attendance check device in a school, or may be attached to the entrance door of an affiliated organization such as a government office or company. This access can be used for access management, access permission management according to security level, system login management, attendance management, etc.

Meanwhile, it can also be installed at affiliated companies that provide various benefits such as military discounts and student discounts. For example, there are no restrictions on affiliates such as KTX stations, shopping malls, and convenience stores.

The edging node access terminal 700 is configured to recognize the mobile ID displayed on the user mobile terminal 300 or the visitor mobile terminal 400, request authentication, and allow or deny certain access based on the authentication result of the displayed mobile ID. You can.

In addition, the edging node access terminal 700 receives the facial feature point information of a member or the facial feature point information of a visitor from the user's organization server 500, recognizes and authenticates the face of the user or visitor, and provides predetermined access according to the authentication result. Can be configured to allow or deny.

The edging node access terminal 700 includes a member/visitor information reception module 701, a facial feature point information reception module 702, a facial feature point information registration control module 703, a user facial feature point information database 704, and a visitor facial feature point. Information database 705, camera module 706, subject facial feature point information extraction module 707, facial feature point information comparison module 708, edging node real-time authentication module 709, OTAC-based QR code recognition module 710, OTAC-based random number code input module (711), tagless BLE module (712), OTAC-based QR code/random number code transmission module (713), access processing module (714), face/QR code double capture control module (715), Can be configured to include a two-factor authentication access control module 716.

Hereinafter, the detailed configuration will be described.

The member/visitor information receiving module 701 may be configured to receive member information or visitor information from the member/visitor information transmission module 507 of the user's organization server 500.

The facial feature point information receiving module 702 may be configured to receive user facial feature point information or visitor facial feature point information from the facial feature point information transmission module 508 of the user's organization server 500.

The facial feature point information registration control module 703 operates the user facial feature point information or visitor facial feature point information received from the facial feature point information reception module 702 according to the member information or visitor information received from the member/visitor information reception module 701. You can control how information is stored.

The user facial feature point information database 704 may be configured to store user facial feature point information for each user under the control of the facial feature point information registration control module 703.

The visitor facial feature point information database 705 may be configured to store visitor facial feature point information under the control of the facial feature point information registration control module 703. Here, visitor facial feature point information may be encrypted and stored.

The camera module 706 may be configured to photograph the face of a predetermined subject.

The subject's facial feature point information extraction module 707 may be configured to extract the subject's facial feature point information from the subject's face photographed by the camera module 706.

The facial feature point information comparison module 708 stores the subject facial feature point information extracted from the subject facial feature point information extraction module 707 into the user facial feature point information stored in the user facial feature point information database 704 and the visitor facial feature point information database 705. It may be configured to compare with stored visitor facial feature information.

The edging node real-time authentication module 709 may be configured to authenticate in real time whether the subject is a user who is a member of the organization or a visitor who has already been authenticated, according to the comparison result of the facial feature point information comparison module 708.

When real-time authentication is completed in the edging node real-time authentication module 709, a visitor facial feature point information deletion module (not shown) may be configured to delete the visitor facial feature point information stored in the visitor facial feature information database 705. Because visitor facial feature information is used temporarily, it can be immediately deleted to protect personal information.

The OTAC-based QR code recognition module 710 may be configured to recognize an OTAC-based QR code displayed on the display 318 of the user mobile terminal 300 or the display 408 of the visitor mobile terminal 400.

The OTAC-based random number code input module 711 may be configured to manually input an OTAC-based random number code displayed on the display 318 of the user mobile terminal 300 or the display 408 of the visitor mobile terminal 400.

The tagless BLE module 712 may be configured to receive a mobile identification card transmitted from the tagless BLE module 320 of the user mobile terminal 300 or the tagless BLE module 409 of the visitor mobile terminal 400.

The OTAC-based QR code/random number code transmission module 713 transmits the OTAC-based QR code displayed on the display 320 of the user mobile terminal 300 or the display 408 of the visitor mobile terminal 400 to the integrated access management server 800. It may be configured to transmit to .

And the OTAC-based QR code/random number code transmission module 713 may be configured to transmit the OTAC-based random number code input to the user mobile terminal 300 or the visitor mobile terminal 400 to the integrated access management server 800.

And the OTAC-based QR code/random number code transmission module 713 can be configured to transmit the OTAC-based random number code received from the tagless BLE terminal 712 of the edging node access terminal 700 to the integrated access management server 800. there is.

The access processing module 714 may be configured to allow or deny predetermined access according to a real-time authentication result of the edging node access terminal 700 or remote control of the integrated access management server 800.

That is, the access processing module 714 may immediately process various accesses such as direct entry, login, and coupon use according to the authentication of the edging node real-time authentication module 709, and may process various accesses such as direct entry, login, and coupon use based on the authentication result of the integrated access management server 800. Depending on your needs, it may be configured to handle that access.

The face/QR code dual capture control module 715 can control the camera module 706 and the OTAC-based QR code recognition module 710 to simultaneously dual capture the subject's face and OTAC-based QR code. In other words, the subject's face and OTAC-based QR code can be captured at the same time and used for two-factor authentication.

When the subject's face and OTAC-based QR code are dual captured simultaneously under the control of the face/QR code dual capture control module 715, the double authentication confirmation access control module 716 detects the edging node real-time authentication module 709 and access. The processing module 714 can check the two-factor authentication of the subject's face and OTAC-based QR code, and if the two-factor authentication is confirmed, the access processing module 714 can be controlled to allow or deny access.

The integrated access management server 800 connects to the Hyperledger Fabric-based blockchain host server 100 at the request of the edging node access terminal 700, authenticates the mobile ID card, and sends the mobile ID authentication result to the edging node access terminal 700. ) can be configured to provide real-time feedback.

The integrated access management server (800) includes an OTAC-based QR code/random number code reception module (801), an OTAC real-time verification module (802), a blockchain verification module (803), a cloud access module (804), and a mobile ID authentication module (805). ), access remote control module (806), real-time terminal location information extraction module (807), ID authentication result/real-time terminal location information transmission module (808), blockchain recovery control module (809), blockchain recovery module (810) It may be configured to include.

Hereinafter, the detailed configuration will be described.

The OTAC-based QR code/random number code receiving module 801 may be configured to receive an OTAC-based QR code or an OTAC-based random number code from the OTAC-based QR code/random number code transmitting module 713 of the edging node access terminal 700. .

The OTAC real-time verification module 802 is configured to verify in real-time the OTAC-based QR code or OTAC-based random number code received in real time from the OTAC-based QR code/random number code reception module 801 using the OTAC verification function corresponding to the OTAC generation function. It can be.

The OTAC real-time verification module 802 includes a second unit time count unit 802a, an OTAC real-time verification unit 802b, a first code extraction unit 802c, a second code extraction unit 802d, and a terminal unique code extraction unit ( 802e).

Hereinafter, the detailed configuration will be described.

The second unit time count unit 802a may be configured to generate a real-time unit time code in real time by performing a count every predetermined unit time.

The OTAC real-time verification unit 802b is configured to verify the OTAC received in real time from the OTAC-based QR code/random number code reception module 501 in real time using the real-time unit time code generated in real time by the second unit time count unit 802a. It can be. In other words, the OTAC can be configured to be verified in real time only by using the same unit time code.

The first code extraction unit 802c may be configured to extract the first code according to the real-time verification result of the OTAC real-time verification unit 802b.

The second code extraction unit 802d may be configured to extract the second code according to the real-time verification result of the OTAC real-time verification unit 802b.

The terminal unique code extraction unit 802e may be configured to extract the terminal unique code according to the real-time verification result of the OTAC real-time verification unit 802b.

When the real-time verification of the OTAC real-time verification module 802 is completed, the blockchain verification module 803 may be configured to access the blockchain ledger 101 according to the verification result to verify the corresponding block in real-time. Here, the blockchain verification module 804 uses the first code and the second code to check and search the location and path of the blockchain ledger 101 and uses the terminal unique code to verify the mobile ID on the blockchain ledger 101. It can be configured to authenticate. In other words, the mobile ID can be authenticated by checking whether the terminal unique code of the same smart phone as the smart phone on which the user's mobile ID was created.

When the real-time verification of the OTAC real-time verification module 802 is completed, the cloud access module 804 may be configured to access the cloud server 100A and query the corresponding mobile identification card according to the verification result.

The mobile ID authentication module 805 may be configured to authenticate the mobile ID according to the verification result of the blockchain verification module 803 or the cloud access module 804.

The access remote control module 806 can remotely control the access processing module 714 of the edging node access terminal 700 to allow or deny access when real-time verification of the blockchain verification module 803 is completed.

The real-time terminal location information extraction module 807 may be configured to extract real-time terminal location information from the OTAC-based QR code or OTAC-based random number code received from the OTAC-based QR code/random number code reception module 801. Here, the extracted real-time terminal location information indicates where the user accesses the mobile ID, so the affiliated organization can use it to check whether the user is on a business trip, manage business trip history, and history management.

The ID authentication result/real-time terminal location information transmission module 808 transmits the mobile ID authentication result of the mobile ID authentication module 805 and the real-time terminal location information extracted from the real-time terminal location information extraction module 807 to the user's organization server (500). ) can be configured to transmit.

The blockchain recovery control module 809 is a Hyperledger Fabric-based blockchain host server ( Control the recovery of the blockchain ledger (100) using the blockchain ledger (101) of another Hyperledger Fabric-based blockchain host server, or modify and register each user's mobile ID using the user's mobile terminal (300). You may request to do so.

The blockchain recovery module 810 may be configured to recover the blockchain ledger 101 under the control of the blockchain recovery control module 809.

The affiliate server 900 may be configured to provide benefits of a predetermined affiliate to the user mobile terminal 300 depending on whether access to the edging node access terminal 700 is permitted or denied. Affiliates may provide coupons, etc.

Here, the affiliate server 900 may provide benefits, such as coupons or postpaid payment processes, to members of the user's affiliated organization through a pre-agreed affiliate process between the organization server 500 and the affiliate server 900.

For example, if the edging node access terminal 700 is located at a restaurant or store within the user's organization, the user can enjoy various benefits such as coupons or gifticons through the affiliate server 900.

In addition, if the edging node access terminal 700 is installed at a subway ticket gate, KTX ticket gate, taxi terminal, gas station, etc., you can use the subway, KTX, taxi, gas station, etc. without separate payment through mobile ID or facial recognition during a business trip. It can be done. Subway and KTX taxis may be configured to make postpaid payments from the user's organization server (500) to the affiliate server (900).

Although the description has been made with reference to the above examples, those skilled in the art can understand that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. There will be.

100: Hyperledger Fabric-based blockchain host server
200: Blockchain ledger design information database
300: User mobile terminal
301: User information input module
302: User information storage module
303: Mobile ID automatic generation module
304: Mobile ID storage module
305: Mobile ID blockchain storage control module
306: Mobile ID search information database
307: Cloud storage control module
308: Camera module
309: User facial feature point information extraction module
310: User facial feature point information storage module
311: User facial feature point information upload module
312: User authentication module
313: OTAC real-time generation module
314: Real-time terminal location information generation module
315: OTAC-based QR code generation module
316: OTAC-based random number code generation module
317: Mobile ID card display control module
318: display
319: Mobile ID BLE transmission control module
320: Tagless BLE module
321: Visit link transmission request module
400: Visitor mobile terminal
401: Camera module
402: Visitor facial feature information extraction module
403: Visitor facial feature point information storage module
404: Visit link receiving module
405: Visitor authentication module
406: Visitor/visit information upload module
407: Visitor facial feature point information upload module
408: display
409: Tagless BLE module
500: User’s organization server
501: User facial feature point information reception module
502: User facial feature point information database
503: Visit link transmission module
504: Visitor/visiting destination information receiving module
505: Visitor facial feature point information reception module
506: Visit information database
507: Member/visitor information transmission module
508: Facial feature point information transmission module
509: Edging node access terminal information database
510: control module
511: Code authentication result/terminal location information reception module
512: Code authentication result/terminal location information database
513: Visit result automatic delivery module
600: Visitor’s organization server
700: Edging node access terminal
701: Member/visitor information reception module
702: Facial feature point information reception module
703: Facial feature point information registration control module
704: User facial feature point information database
705: Visitor facial feature information database
706: Camera module
707: Subject facial feature point information extraction module
708: Facial feature point information comparison module
709: Edging node real-time authentication module
710: OTAC-based QR code recognition module
711: OTAC-based random number code input module
712: Tagless BLE module
713: OTAC-based QR code/random number code transmission module
714: Access processing module
715: Face/QR code dual capture control module
716: Two-factor authentication access control module
800: Unified Access Management Server
801: OTAC-based QR code/random number code reception module
802: OTAC real-time verification module
803: Blockchain verification module
804: Cloud access module
805: Mobile ID authentication module
806: Access remote control module
807: Real-time terminal location information extraction module
808: ID authentication result/real-time terminal location information transmission module
809: Blockchain recovery control module
810: Blockchain recovery module
900: Affiliate server

Claims (3)

Hyperledger Fabric-based blockchain host server where the Hyperledger Fabric-based blockchain ledger is stored;
A user mobile terminal that generates a mobile ID card, stores it in a blockchain ledger of the Hyperledger Fabric-based blockchain host server, and displays the mobile ID card;
Access through the implementation of a mobile ID-based facial recognition edging node, including an edging node access terminal that recognizes the mobile ID displayed on the user's mobile terminal, requests authentication, and allows or denies predetermined access according to the authentication result of the displayed mobile ID. and attendance management system linked service construction system.
The method of claim 1, wherein the edging node access terminal,
It extracts the member's facial feature point information, recognizes and authenticates the member's face, and allows or denies access directly based on the authentication result, or allows or denies certain access by command from the user's organization server. A system for building an access and attendance management system linked service through the implementation of a mobile ID-based facial recognition edging node.
According to paragraph 2,
To further include an integrated access management server that connects to the Hyperledger Fabric-based blockchain host server at the request of the edging node access terminal, authenticates the mobile ID card, and feeds back the mobile ID authentication result to the edging node access terminal in real time. A system for building an access and attendance management system linked service through the implementation of a mobile ID-based facial recognition edging node.