KR102429807B1 - Method and system for managing visit history of visitors - Google Patents

Abstract

A method and system for managing a visitor's visit history are provided. A method for managing a visitor's visit history according to an embodiment of the present invention includes: encrypting visit information generated when a visitor enters and exits using a visitor terminal; generating an authentication key capable of confirming public visit information allowed to be disclosed by the visitor from the encrypted visit information; and providing the authentication key to a manager terminal that manages access to check the public visit information.

Description

Method and system for managing visitor's visit history

The present invention relates to a method and system for managing a visitor's visit history.

Companies, universities, public institutions, business facilities, and organizations that require visitor access control collect visitor information through paper or a separate management system for visitor records, and manage and store it.

However, visitors have the burden of providing personal information to the places they visit and have anxiety about leakage of personal information. In addition, the manager of the place visited by the visitor is burdened with the collection, management, and storage of personal information about non-members, and efforts are required to prevent damage caused by the leakage of personal information of visitors.

Japanese Patent No. 5257912 (Registered on May 2, 2013) Japanese Patent Laid-Open No. 2006-338587 (published on December 14, 2006) Republic of Korea Patent Registration No. 10-1920654 (Registered on November 15, 2018) Republic of Korea Patent No. 10-0806340 (Registered on Feb. 16, 2008)

The present invention is to solve the above problem, and provides a method and system for managing a visitor's visit history, in which a visitor selects an information provision range and the like, and a visiting company can check only the information permitted by the visitor.

The problems to be solved by the present invention are not limited to the problems mentioned above, and other problems not mentioned will be clearly understood by those skilled in the art from the following description.

According to an embodiment of the present invention, there is provided a method for managing a visitor's visit history, comprising: encrypting visit information generated when a visitor enters and exits using a visitor terminal; generating an authentication key capable of confirming public visit information allowed to be disclosed by the visitor from the encrypted visit information; and providing the authentication key to a manager terminal that manages access to check the public visit information.

In addition, the method may further include encrypting and storing personal identification information proving that the visitor is an identity using the visitor terminal in a database.

Also, the encrypting the visit information may include identifying the visitor terminal using at least one of an NFC tag, a QR code, or a beacon signal.

In addition, when the visitor terminal first accesses using at least one of the NFC tag, QR code, or beacon signal, the method may include installing an access application.

In addition, the generating of the authentication key may include generating an authentication key for releasing the marking process of the public visit information in the encrypted visit information by the authentication key.

The method may further include requesting notification information requested by the manager terminal to the visitor terminal.

In addition, the requesting from the visitor terminal may include requesting notification information related to the visitor's infectious disease symptoms from the visitor terminal.

A method for managing a visitor's visit history according to an embodiment of the present invention for achieving the above object includes: encrypting, in the visitor terminal, visit information generated when the visitor enters and exits using the visitor terminal; transmitting and storing the encrypted visit information to a visit management server; and when there is a request for providing personal information to the visitor from the manager terminal, providing the encrypted visit information to the visitor terminal to decrypt the visitor terminal.

In addition, generating a confirmation key that can be confirmed by decrypting the visit information in the visitor terminal; and storing the confirmation key in the visitor terminal.

In addition, encrypting the confirmation key in the visitor terminal; and transmitting and storing the encrypted confirmation key to the visit management server.

and, when the confirmation key is not present in the visitor terminal, requesting the encrypted confirmation key to the visit management server; receiving the encrypted confirmation key from the visit management server to the visitor terminal; and decrypting the encrypted confirmation key.

A visitor's visit history management system according to an embodiment of the present invention for achieving the above object encrypts personal identification information that proves that the visitor is the person using the visitor terminal, and the visitor enters and exits using the visitor terminal an information encryption unit for encrypting visit information generated at the time; an authentication key generation unit generating an authentication key capable of confirming public personal identification information and public visit information allowed to be disclosed by the visitor from the encrypted personal identification information and visit information; and an authentication key providing unit that provides the authentication key to a manager terminal that manages access.

In addition, it may further include a visitor identification unit for identifying the visitor terminal using at least one of an NFC tag, a QR code, or a beacon signal.

In addition, when the visitor terminal first accesses using at least one of the NFC tag, QR code, or beacon signal, an application installation for requesting the visitor terminal to install an access application and installing the access application to the visitor terminal It may include more wealth.

In addition, it may further include a notification requesting unit for requesting the information requested by the manager terminal to the visitor terminal.

Also, the notification requesting unit may request the visitor terminal to submit an answer to the question information requested by the manager terminal.

In addition, it may further include a control unit for controlling to store the personal identification information and visit information encrypted by the information encryption unit, and the authentication key generated by the authentication key generating unit in an external database.

Also, the controller may determine whether encryption of the visitor's personal identification information and visit information is required.

In addition, the information encryption unit may encrypt the personal identification information and the visit information by marking and displaying.

Other specific details of the invention are included in the detailed description and drawings.

According to the present invention, the visitor takes the initiative in managing information related to the visitor, thereby preventing the burden of information collection and management of various visiting companies and the risk of information leakage of the visitor, and the visitor himself/herself can easily manage the visit history.

1 is a diagram illustrating the configuration of an overall system to which a method for managing a visitor's visit history according to an embodiment of the present invention is applied.
2 is a diagram illustrating a sequence of a method for managing a visitor's visit history according to an embodiment of the present invention.
3 is a diagram illustrating a detailed sequence of a method for managing a visitor's visit history according to an embodiment of the present invention.
4 is a diagram illustrating a sequence of a method for managing a visitor's visit history according to another embodiment of the present invention.
5 and 6 are diagrams illustrating a detailed sequence of a method for managing a visitor's visit history according to another embodiment of the present invention.
7 is a diagram illustrating the configuration of a visitor history management system according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but will be implemented in a variety of different forms, only these embodiments allow the disclosure of the present invention to be complete, and common knowledge in the technical field to which the present invention belongs It is provided to fully inform the possessor of the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

Although first, second, etc. are used to describe various elements, components, and/or sections, it should be understood that these elements, components, and/or sections are not limited by these terms. These terms are only used to distinguish one element, component, or sections from another. Accordingly, it goes without saying that the first element, the first element, or the first section mentioned below may be the second element, the second element, or the second section within the spirit of the present invention.

The terminology used herein is for the purpose of describing the embodiments and is not intended to limit the present invention. In this specification, the singular also includes the plural, unless specifically stated otherwise in the phrase. As used herein, "comprises" and/or "made of" refers to a referenced component, step, operation and/or element of one or more other components, steps, operations and/or elements. The presence or addition is not excluded.

Unless otherwise defined, all terms (including technical and scientific terms) used herein may be used with the meaning commonly understood by those of ordinary skill in the art to which the present invention belongs. In addition, terms defined in a commonly used dictionary are not to be interpreted ideally or excessively unless clearly defined in particular.

Hereinafter, the present invention will be described in more detail with reference to the accompanying drawings.

1 is a diagram illustrating the configuration of an overall system to which a method for managing a visitor's visit history according to an embodiment of the present invention is applied.

Referring to FIG. 1 , the entire system to which the method of managing a visitor's visit history according to an embodiment of the present invention is applied is a visitor terminal 10 , a visit management server 20 , a manager terminal 30 , and a gate device 40 . ) is included. In addition, it may further include a database 50 under the management of the visit management server (20).

The visitor terminal 10 may visit a place to visit by tagging the NFC tag installed in the gate device 40 or accessing it through a QR code scan. Visit information is generated when entering and exiting the gate device 40 using the visitor terminal 10 , and the visit information may be collected to become visit history information.

The visitor terminal 10 is a general mobile communication terminal, 2G/3G/4G/5G, a terminal capable of WiBro wireless network service, a Palm Personal Computer (PC), a personal digital assistant (PDA), and a smart phone (Smart phone). phone), WAP phone (Wireless application protocol phone), etc., can mean all wired and wireless home appliances/communication devices that have a user interface for accessing the network, and for wireless LAN connection such as IEEE 802.11 wireless LAN network card. It may be a device equipped with an interface. In addition, the visitor terminal 10 may be an information communication device such as a computer or a notebook computer, or a device including the same, in addition to a mobile communication terminal.

Here, the visitor terminal 10 may include an NFC module, a QR code reader, a beacon module, a camera, a memory, a processor, a communication module, an input module such as a touch sensor or keyboard, an output module such as a display, a microphone, etc. . You can tag an NFC tag using an NFC module, or scan a QR code using a QR code reader or camera. Also, a beacon signal may be received through the beacon module.

The visitor may manage the scope of information provided to the subject who manages access to the place to be visited through the visitor terminal 10 . That is, the visitor can manage whether or not the information is provided and the scope thereof in the visitor terminal 10 by themselves. Thus, the visitor can relieve the burden of providing personal information and the anxiety about personal information leakage.

The visit management server 20 provides the visitor terminal 10 with an access application that allows the visitor to independently manage visit information. In addition, the visit management server 20 provides an authentication key generated by encrypting various information of the visitor to the manager terminal 30 . In addition, the visit management server 20 may provide the stored encrypted visit information, etc. to the manager terminal (30). The visit management server 20 cannot directly check the encrypted visitor information, and it is preferable to store various types of information and data in a separate database 50 .

The manager terminal 30 may control the gate device 40 and manage visitors entering and leaving the gate device 40 by tagging an NFC tag or accessing it through a QR code.

The manager terminal 30 may be an information communication device such as a general mobile communication terminal, a computer, or a notebook computer, or a device including the same. In addition, if the manager terminal 30 can be linked with an output device such as a display that can check visitor information, it can include a physical server, a logical server, and the like. It will be self-evident to you.

The manager terminal 30 may check the visitor's personal information, visit information, visit history information, etc. within an allowed range through the authentication key. Information for which the visitor does not agree to provide information is marked and cannot be confirmed in the manager terminal 30 . Therefore, the manager of the manager terminal 30 can be freed from the burden of collection, management, and storage of information about the visitor and the risk of information leakage.

The gate device 40 is an apparatus or facility for visitor access management, and an NFC tag, QR code, beacon, etc. matching information of a place to be visited may be installed in the gate device 40 . The gate device 40 may be managed under the control of the manager terminal 30 . When a visitor enters and exits through the gate device 40, encrypted personal information of the visitor, visit information, etc. are generated and stored in the visit management server 20 or the database 50 controlled by the visit management server 20 . And, as the encrypted information is generated, an authentication key for confirming the encrypted information is generated in the visitor terminal 10 or the visit management server 20 and provided to the manager terminal 30 .

The database 50 stores various data and information obtained from the visit management server 20 , the visitor terminal 10 , and the manager terminal 30 . In particular, the encrypted personal information and visit information of the visitor, and an authentication key generated according to the encrypted information are stored.

The database 50 may mean a logical or physical storage server for storing data and information, and may be an external database such as a cloud, but it will be apparent to those skilled in the art that it is not limited thereto.

Hereinafter, a method for managing a visitor's visit history according to an embodiment of the present invention will be described in detail.

2 is a diagram illustrating a sequence of a method for managing a visitor's visit history according to an embodiment of the present invention. Also, FIG. 3 is a diagram illustrating a detailed sequence of a method for managing a visitor's visit history according to an embodiment of the present invention.

Referring to FIG. 2 , in the method for managing a visitor's visit history according to an embodiment of the present invention, the visitor uses the visitor terminal 10 to encrypt visit information generated when entering and exiting (S110), and the encrypted visit information generates an authentication key for confirming the public visit information allowed to be disclosed by the visitor (S120), and provides the authentication key to the manager terminal 30 that manages access to check the public visit information ( S130).

When the visit information is encrypted ( S110 ), when the visitor tags an NFC tag of a place to be visited using the visitor terminal 10 , the visit information is generated and encrypted. Here, when the visitor visits several times, the visit information may be the visit history information through which the visit history can be known.

After the visit information is encrypted, the administrator cannot immediately check it. After the visit information is encrypted, the information may be provided to the administrator of the place to visit according to the decision of the visitor, and the scope of the information provision may be selected.

The encrypted information may be stored in the manager terminal 30 or a storage (not shown) under the management of the manager terminal 30 .

Alternatively, in order to prevent the risk of personal information leakage in advance, it may be stored in the database 50 managed by the visit management server 20 . Encrypted information stored in the database 50 may be transmitted to the manager terminal 30 under the permission of the visitor. In addition, in encrypting the visit information, since the visitor enters and exits using the visitor terminal 10, it is necessary to check whether the visitor is a legitimate visitor. In this case, the visitor terminal 10 may be identified using at least one of an NFC tag, a QR code, or a beacon signal, and entry and exit of the visitor using the identified visitor terminal 10 may be permitted.

For example, when a visitor tags the visitor terminal 10 with an NFC tag that controls access to the gate device 40 , or scans a QR code, or receives a beacon signal, the access application installed on the visitor terminal 10 . Through this, the administrator can request permission for access along with the answer to the questionnaire, and the administrator who has completed checking whether the visitor is a legitimate visitor can grant the visitor's access.

As an example of checking whether the visitor is a legitimate visitor, an access key issued by the manager of the manager terminal 30 to the visitor of the visitor terminal 10 is transmitted to a predetermined device such as the visitor terminal 10 or the gate device 40 . can The access key transmitted to the visitor terminal 10 is shared with the manager terminal 30 so that the manager of the gate device 40 can check whether the visitor using the visitor terminal 10 is a legitimate visitor.

More specifically, the manager terminal 30 issues an access key, etc., and provides the issued access key directly to the visitor terminal 10 or provides the visitor terminal 10 through the visit management server 20, and provides the visitor may use the access key to authenticate the manager terminal 30 or the gate device 40 to authenticate whether the visitor is a legitimate visitor.

At this time, the manager managing the gate device 40 and the like can check the validity of the access key through the manager terminal 30 to confirm whether the visitor is a legitimate visitor, but the visitor information is encrypted and the visitor information can be checked without the visitor's consent. can't

The process of installation of the access application, authentication of visitors, etc. will be described later in detail.

When generating the authentication key (S120), an authentication key that can confirm only the information selected by the visitor from the encrypted visit information is generated.

Specifically, the authentication key may be generated by marking the public visit information allowed to be disclosed by the visitor in the encrypted visit information.

For example, after marking a part of information such as the visitor's name, phone number, and address, it may be provided to the manager terminal 30 so that the manager cannot check the visitor's personal information.

In this case, the authentication key may be stored and managed in the database 50 managed by the visit management server 20, and through this, the authentication key may be backed up. The authentication key stored in the database 50 may be transmitted to the manager terminal 30 by the visit management server 20 under the permission of the visitor terminal 10 when the manager terminal 30 requests it.

When the authentication key is provided (S130), the authentication key is provided to the manager terminal 30 that manages access so that public visit information can be checked. The manager terminal 30 may check the encrypted visit information using the authentication key.

Since the authentication key provided to the manager terminal 30 can check the public visit information allowed to be disclosed by the visitor, the manager terminal 30 can check only the information allowed by the visitor.

In particular, for the authentication key provided to the manager terminal 30 , an effective period for checking public visit information may be set. For example, visit information encrypted through the authentication key can be checked for 24 hours. After the expiration of the validity period, after permission of a legitimate visitor, the visit management server 20 may set the validity period.

In addition, the authentication key provided to the manager terminal 30 may be automatically revoked after a predetermined period (eg, one month, etc.). In this case, the authentication key stored and managed in the database 50 may be retransmitted from the visit management server 20 to the manager terminal 30 after the visitor's permission. In this way, the privacy of visitors can be further strengthened.

3, before the process of encrypting information related to the visitor (S110), generating an authentication key related to the encrypted information (S120), and providing the authentication key to the manager terminal 30 (S130), application installation (S15), visitor of the person (S19) may be verified.

More specifically, after the visitor accesses the visitor terminal 10 through an NFC tag, a QR code, a beacon signal, etc. (S11), depending on whether the APP of the access application that manages the visitor's access history, etc. is installed (S13), If the APP is not installed (S13, No), the APP installation proceeds (S15). That is, when the visitor terminal 10 first accesses using an NFC tag, a QR code, a beacon signal, or the like, an access application may be installed.

In addition, when the access application has already been installed in the visitor terminal 10 (S13, Yes) or the installation of the access application is completed (S15), it is determined whether the visitor has visited for the first time (S17). Here, whether the visitor has visited for the first time may be determined as the first visit if there is no history of visiting a place to which the visitor wants to enter. The visit history may be stored in the visitor terminal 10 or in the database 50 managed by the visit management server 20, and it is determined whether it is the first visit based on the visit history.

In particular, since the visit information transmitted from the visitor terminal 10 to the outside is encrypted and only the public visit information allowed to be disclosed by the visitor by the authentication key can be checked, the visit management server 20 or the manager terminal 30 authenticates By identifying the key, you can check whether it is the first visit.

For example, the visiting company may distinguish the second visitor terminal 10 that is distinguished from the arbitrary first visitor terminal 10 through the authentication key. In this case, the visitor terminals 10 can be distinguished from each other through the authentication key, but other information can be set so that the manager terminal 30 cannot confirm it. For example, the visit management server 20 lists the authentication keys generated according to the information encryption of the visitor terminals 10 for each visitor terminal 10, and the database 50 lists the authentication keys for each visitor terminal 10. can be stored in

When the visitor of the visitor terminal 10 is the first visit (S17, Yes), the visitor authenticates himself (S19). For example, the visitor terminal 10 from the visit management server 20 may request identification using a name, a resident registration number, a phone number of the visitor terminal 10, etc. can be entered into the visitor terminal 10 to verify the identity.

At this time, the personal identification information that the visitor proves that he or she is himself by using the visitor terminal 10 is encrypted and stored in the external database 50 . In the case of encrypting personal identification information, an authentication key may be generated that can verify only personal identification information allowed to be disclosed by the visitor. The authentication key for verifying personal identification information may be transmitted to the manager terminal 30 under the consent of the visitor.

If the visitor of the visitor terminal 10 is not the first visit (S17, No), since the identity authentication for the visitor of the visitor terminal 10 has already been made, a separate identity authentication is omitted and the visit information is encrypted (S110) ). In addition, when identification is made (S19), personal identification information according to the identification is encrypted and encrypted as the first visit information (S110).

After the visitor information is encrypted, an authentication key is generated and provided to the manager terminal 30, which is the same as described above, so a detailed description thereof will be omitted.

In addition, although not shown in the drawing, notification information requested by the manager terminal 30 may be requested from the visitor terminal 10 .

More specifically, the visitor of the visitor terminal 10 may request an answer to a question set by the administrator. For example, it is possible to request question information related to the symptoms of an epidemic, and transmit question information, such as whether the visitor's fever is checked, whether the visitor has cough symptoms, whether breathing difficulties, and whether or not to travel abroad within a predetermined period to the visitor terminal 10 . and may request a response.

Such notification information may be requested from the manager terminal 30 to the visitor terminal 10 , and symptoms of infectious diseases such as corona may be checked directly from the visitor terminal 10 online rather than offline.

4 is a diagram illustrating a sequence of a method for managing a visitor's visit history according to another embodiment of the present invention. 5 and 6 are diagrams illustrating a detailed sequence of a method for managing a visitor's visit history according to another embodiment of the present invention.

Referring to FIG. 4 , the visitor terminal 10 encrypts visit information generated when the visitor enters and exits using the visitor terminal (S210), and transmits the encrypted visit information to the visit management server 20 (S218) ), stored (S220), and when there is a request for providing personal information to the visitor from the manager terminal 30 (S222), the encrypted visit information is provided to the visitor terminal (S224), and decrypted in the visitor terminal do (S230).

When the visit information is encrypted in the visitor terminal 10 (S210), when the visitor tags an NFC tag of a place to visit using the visitor terminal 10 (S202), the visit information is generated and the tag fact is stored in the manager It is transmitted to the terminal 30 (S204). Here, when the visitor visits several times, the visit information is gathered and may be the visit history information to know the visit history, and a tag list is generated in the manager terminal 30 ( S206 ).

At this time, questionnaire information such as whether the visitor's fever has been checked, whether the visitor has cough symptoms, whether breathing difficulties, and whether or not to travel abroad within a predetermined period is transmitted to the visitor terminal 10 together with the tag, and an answer is sent to the visitor terminal 10 ) can be requested.

Through this, since the visitor terminal 10 can check the symptoms of infectious diseases such as corona directly online rather than offline, and check it on the manager terminal 30 , it is possible to manage the visitor for necessary matters non-face-to-face.

After the visit information is encrypted, the encrypted visit information is transmitted to the visit management server 20 (S218), and is stored in the visit management server 20 or the database 50 managed by the visit management server 20 (S220). Since the visit information is encrypted and transmitted to the visit management server 20 and stored in the database 50 or the like, it cannot be checked in the visit management server 20 or the manager terminal 30, so it is possible to protect the visitor's personal information.

The manager of the manager terminal 30 must make a request to provide personal information to the visit management server 20 in order to check the personal information of the visitor (S222). The visit management server 20 transmits the personal information provision request of the manager terminal 30 to the visitor terminal 10 (S224). Here, the visit management server 20 may transmit the encrypted visit information to the visitor terminal 10 .

The visitor terminal 10 decrypts the encrypted visit information (S230), and transmits it to the visit management server 20 (S232). Here, the scope of the information provision may be selected according to the decision of the visitor. If the encrypted visit information is stored in the visitor terminal 10, it can be directly decrypted, but if there is no encrypted visit information in the visitor terminal 10, it is encrypted from the visitor terminal 10 to the visit management server 20 You can request the transmission of your visit information. When the encrypted visit information is transmitted from the visit management server 20 to the visitor terminal 10 , the visitor terminal 10 decrypts the encrypted visit information.

The decrypted visit information is transmitted from the visit management server 20 to the manager terminal 30 . Since the range of information provision is selected according to the visitor's decision and transmitted to the manager terminal 30 , the manager of the manager terminal 30 can also check the visitor's personal information within the range of information provision.

In order to decrypt the encrypted visit information, a confirmation key may be generated and stored in the visitor terminal 10 .

Referring to FIG. 5 , generation and storage of a confirmation key for decrypting encrypted visit information may be performed.

More specifically, a confirmation key that can be confirmed by decrypting the visit information is generated in the visitor terminal 10 (S22), and the confirmation key is stored in the visitor terminal 10 (S24). Since there is a confirmation key in the visitor terminal 10 , the encrypted visit information can be checked only in the visitor terminal 10 .

That is, since only the public visit information allowed to be disclosed by the visitor can be checked by the confirmation key, the visitor's personal information cannot be checked in the visit management server 20 or the manager terminal 30 without the confirmation key.

In addition, the confirmation key may be encrypted in the visitor terminal 10 (S26), and the encrypted confirmation key may be transmitted to the visit management server 20 (S28) and stored (S30).

This is because the encrypted visit information can be confirmed only when there is a confirmation key, so in case the confirmation key disappears from the visitor terminal 10 due to deletion, etc., the confirmation key itself is encrypted and stored in a separate visit management server 20 . will be.

This encrypted confirmation key can be used by being transmitted back to the visitor terminal 10 .

Referring to FIG. 6 , when a request for decryption of visit information is requested from the visit management server 20 to the visitor terminal 10 (S32), if there is a confirmation key in the visitor terminal 10 (S34, Yes), the visit information Decryption is possible (S230).

And, when the confirmation key is not present in the visitor terminal 10 (S34, No), the encrypted confirmation key is requested from the visit management server 20 (S36), and the visitor terminal 10 from the visit management server 20 to receive the encrypted confirmation key (S38).

Thereafter, the encrypted confirmation key is decrypted in the visitor terminal 10 (S40). By decrypting the encrypted confirmation key, it is possible to decrypt the encrypted visit information using it (S230).

In this case, the decryption of the encrypted confirmation key may be performed by inputting a password set in advance by the visitor into the visitor terminal 10 , thereby decrypting the encryption of the confirmation key. For example, the visitor may decrypt the encrypted confirmation key by inputting a predetermined PIN number or the like into the visitor terminal 10 .

7 is a diagram illustrating the configuration of a visitor history management system according to an embodiment of the present invention.

Referring to FIG. 7 , the visitor history management system 100 according to an embodiment of the present invention includes an information encryption unit 110 , an authentication key generation unit 120 , and an authentication key providing unit 130 . In addition, the visitor history management system 100 may further include a control unit 140 , a visitor identification unit 150 , an application installation unit 160 , a notification request unit 170 , and the like.

The information encryption unit 110 encrypts personal identification information that proves that the visitor is the person using the visitor terminal 10, and can encrypt the visit information generated when the visitor enters and exits using the visitor terminal 10. have.

In this case, the encryption of personal identification information is information that proves that the visitor is the person when he or she first visits a company or place to be visited.

In addition, in the case of encrypting the visit information, when the visitor tags an NFC tag of a place to be visited using the visitor terminal 10 , the visit information is generated and encrypted. Here, when the visitor visits several times, the visit information can be gathered and information can be known about the visit history. can

Encrypted personal identification information and/or visit information can be verified by a third party by an authentication key.

In addition, the information encryption unit 110 may encrypt personal identification information and visit information by marking and displaying. For example, after marking a part of information such as the visitor's name, phone number, and address, it is provided to the manager terminal 30 so that the manager cannot check the visitor's personal information such as personal identification information and visit information can do.

The authentication key generation unit 120 may generate an authentication key capable of confirming the public personal identification information and public visit information allowed to be disclosed by the visitor from the encrypted personal identification information and visit information.

For example, when a part of information such as a visitor's name, phone number, and address is marked, the authentication key generator 120 checks the visitor's information, such as personal identification information and visit information, which have been marked and only partially disclosed. You can create a valid authentication key.

The authentication key providing unit 130 may provide the authentication key to the manager terminal 30 that manages access. As the authentication key is provided to the manager terminal 30 by the authentication key providing unit 130 , the manager terminal 30 can confirm the visitor's personal information such as personal identification information and visit information encrypted using the authentication key.

Accordingly, since the manager terminal 30 can check only the information allowed by the visitor, the manager of the manager terminal 30 can reduce the burden of collecting, managing, and storing information about the visitor, and preventing the visitor from leaking personal information. risk can be avoided.

The control unit 140 may store the personal identification information and visit information encrypted by the information encryption unit 110 and the authentication key generated by the authentication key generation unit 120 in the external database 50 .

At this time, it is preferable to store the information generated by the information encryption unit 110 and the authentication key generated by the authentication key generation unit 120 in separate databases 50 , respectively. Since information encrypted by the authentication key can be checked, the security of information can be improved by implementing the physically separated database 50 .

In particular, the controller 140 can control to store the authentication key in the database 50, and only with the consent of the visitor so that the controller 140 can access the database 50 in which the authentication key is stored and receive the authentication key. It is preferable to do

Also, the controller 140 may determine whether encryption of the visitor's personal identification information and visit information is required.

For example, when the visitor terminal 10 tags an NFC tag, etc., the controller 140 determines whether an access application is installed, and first accesses the gate device 40 in which the NFC tag tagged by the visitor terminal 10 is installed. You can determine whether encryption of the visitor's personal information is required by checking whether or not

After the access application is installed in the visitor terminal 10 and the first visit of the visitor is confirmed, the control unit 140 encrypts personal information such as personal identification information and visit information that proves that the visitor is the person.

In addition, the controller 140 tags the visitor terminal 10 with an NFC tag for controlling entry and exit of the gate device 40 , or scans a QR code, or receives a beacon signal, to the visitor terminal 10 . Through the installed access application, it is possible to request authentication for access to the visitor, and to request the access of the visitor who has completed authentication to the manager terminal 30 .

The visitor identification unit 150 may identify the visitor terminal 10 using at least one of an NFC tag, a QR code, or a beacon signal. For the visitor terminals 10 identified by the visitor identification unit 150 , the controller 140 may request access to the manager terminal 30 .

For example, the control unit 140 transmits an access key, etc. to the visitor of the visitor terminal 10 identified by the visitor identification unit 150, and through the access key authentication in the gate device 40, a preset access password If it matches, the administrator terminal 30 is notified that the visitor is a legitimate visitor, and access can be requested. In addition, a manager who manages the gate device 40 and the like may permit a legitimate visitor to enter the visitor terminal 10 requested through the manager terminal 30 .

The application installation unit 160 requests the visitor terminal 10 to install an access application when the visitor terminal 10 first accesses it using at least one of an NFC tag, a QR code, or a beacon signal, and the access application can be installed in the visitor terminal 10 . That is, if the application installation unit 160 does not install the access application for managing the visitor's visit history, etc., the installation proceeds to the visitor terminal 10 .

The notification requesting unit 170 may request question information requested by the manager terminal 30 from the visitor terminal 10 . This may include an infectious disease questionnaire, consent according to the visit place, notification information, and the like according to the question configuration of the manager terminal 30 .

Specifically, the notification requesting unit 170 may request the visitor terminal 10 to submit an answer to the question information requested by the manager terminal 30 . For example, the notification requesting unit 170 may request to submit an answer to question information related to the visitor's infectious disease symptoms.

For example, the notification requesting unit 170 transmits question information such as whether the visitor's fever is checked, whether the visitor has cough symptoms, whether breathing difficulties, and whether or not to travel abroad within a predetermined period to the visitor terminal 10, and for this A response may be requested from the visitor terminal 10 .

Such question information, notification information, etc. can be requested from the manager terminal 30 to the visitor terminal 10, and the symptoms of infectious diseases such as corona in the visitor terminal 10 are checked online rather than offline, and this is checked by the manager terminal ( 30), it is possible to manage the visitors non-face-to-face before the visitor face-to-face.

On the other hand, the method and system for managing a visitor's visit history according to an embodiment of the present invention can be implemented as one module by at least one of software, firmware, and hardware, and the above-described embodiments of the present invention can be executed on a computer. It can be implemented in a general-purpose computer that operates the program using a computer-readable recording medium that can be written as a program. The computer-readable recording medium is implemented in the form of a magnetic medium such as a ROM, a floppy disk, a hard disk, an optical medium such as a CD or DVD, and a carrier wave such as transmission through the Internet. In addition, the computer-readable recording medium is distributed in a computer system connected to a network so that the computer-readable code can be stored and executed in a distributed manner.

And, the component or '~ unit' used in the embodiment of the present invention is a task, class, subroutine, process, object, execution thread, software such as a program, or FPGA ( It may be implemented in hardware such as a field-programmable gate array or an application-specific integrated circuit (ASIC), or may be implemented in a combination of the software and hardware. The component or '~ unit' may be included in a computer-readable storage medium, or a part thereof may be distributed and distributed in a plurality of computers.

Although the embodiments of the present invention have been described above with reference to the accompanying drawings, those of ordinary skill in the art to which the present invention pertains can realize that the present invention can be embodied in other specific forms without changing the technical spirit or essential features. you will be able to understand Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive.

10: Visitor terminal
20: visit management server
30: administrator terminal
40: gate device
50: database
100: visit history management system
110: information encryption unit 120: authentication key generation unit
130: authentication key providing unit

Claims (19)

Encrypting visit information generated when a visitor enters and exits using a visitor terminal;
generating an authentication key capable of confirming public visit information allowed to be disclosed by the visitor from the encrypted visit information; and
providing the authentication key to a manager terminal that manages access so that the public visit information can be checked;
The step of encrypting the visit information,
using at least one of an NFC tag, a QR code, or a beacon signal to identify the visitor terminal;
When the visitor terminal first accesses using at least one of the NFC tag, QR code, or beacon signal, installing an access application. The method of claim 1,
The method of managing a visitor's visit history, further comprising the step of encrypting and storing personal identification information that proves that the visitor is the person using the visitor terminal by using the visitor terminal. delete delete The method of claim 1,
The step of generating the authentication key comprises:
and generating an authentication key for canceling marking processing of the public visit information from the encrypted visit information by the authentication key. The method of claim 1,
Further comprising the step of requesting notification information requested by the manager terminal to the visitor terminal, the visitor's visit history management method. 7. The method of claim 6,
The step of requesting the visitor terminal,
Comprising the step of requesting notification information related to the visitor's infectious disease symptoms to the visitor terminal, the visitor's visit history management method. Encrypting visit information generated when a visitor enters and exits using the visitor terminal at the visitor terminal;
transmitting and storing the encrypted visit information to a visit management server; and
when there is a request for providing personal information to the visitor from the manager terminal, providing the encrypted visit information to the visitor terminal to decrypt the visitor terminal;
generating, in the visitor terminal, a confirmation key that can be verified by decrypting the visit information; and
Storing the confirmation key in the visitor terminal, the visitor's visit history management method. delete 9. The method of claim 8,
encrypting the confirmation key in the visitor terminal; and
Further comprising the step of transmitting and storing the encrypted confirmation key to the visit management server, the visitor's visit history management method. 11. The method of claim 10,
if the confirmation key is not present in the visitor terminal, requesting the encrypted confirmation key from the visit management server;
receiving the encrypted confirmation key from the visit management server to the visitor terminal; and
Further comprising the step of decrypting the encrypted confirmation key, visitor's visit history management method. an information encryption unit that encrypts personal identification information proving that the visitor is the person using the visitor terminal, and encrypts visit information generated when the visitor enters and exits using the visitor terminal;
an authentication key generation unit generating an authentication key capable of confirming public personal identification information and public visit information allowed to be disclosed by the visitor from the encrypted personal identification information and visit information;
an authentication key providing unit providing the authentication key to a manager terminal that manages access;
a visitor identification unit for identifying the visitor terminal using at least one of an NFC tag, a QR code, or a beacon signal; and
When the visitor terminal first accesses using at least one of the NFC tag, QR code, or beacon signal, it includes an application installation unit that requests the visitor terminal to install an access application, and installs the access application to the visitor terminal , a visitor history management system. delete delete 13. The method of claim 12,
Further comprising a notification requesting unit for requesting the question information requested by the manager terminal to the visitor terminal, the visitor's visit history management system. 16. The method of claim 15,
The notification request unit,
Requesting the visitor terminal to submit an answer to the question information requested by the manager terminal, the visitor's visit history management system. 13. The method of claim 12,
The visitor's visit history management system further comprising a control unit for controlling to store the personal identification information and visit information encrypted by the information encryption unit, and the authentication key generated by the authentication key generation unit in an external database. 18. The method of claim 17,
The control unit is
A visitor's visit history management system that determines whether encryption of the visitor's personal identification information and visit information is required. 13. The method of claim 12,
The information encryption unit,
By marking and displaying, the visitor's visit history management system encrypts the personal identification information and visit information.

Images