WO2017140240A1 - 访客认证方法和*** - Google Patents

访客认证方法和*** Download PDF

Info

Publication number
WO2017140240A1
WO2017140240A1 PCT/CN2017/073547 CN2017073547W WO2017140240A1 WO 2017140240 A1 WO2017140240 A1 WO 2017140240A1 CN 2017073547 W CN2017073547 W CN 2017073547W WO 2017140240 A1 WO2017140240 A1 WO 2017140240A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
household
visitor
gate
server
Prior art date
Application number
PCT/CN2017/073547
Other languages
English (en)
French (fr)
Inventor
胡飞虎
Original Assignee
胡飞虎
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 胡飞虎 filed Critical 胡飞虎
Publication of WO2017140240A1 publication Critical patent/WO2017140240A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/20—Individual registration on entry or exit involving the use of a pass
    • G07C9/215—Individual registration on entry or exit involving the use of a pass the system having a variable access-code, e.g. varied as a function of time
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/20—Individual registration on entry or exit involving the use of a pass
    • G07C9/22—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder
    • G07C9/23—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder by means of a password
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/20—Individual registration on entry or exit involving the use of a pass
    • G07C9/22—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder
    • G07C9/25—Individual registration on entry or exit involving the use of a pass in combination with an identity check of the pass holder using biometric data, e.g. fingerprints, iris scans or voice recognition

Definitions

  • the present invention belongs to the field of information technology, and in particular, to a visitor authentication method and system.
  • Chinese Patent Application No. 201410000185.6 discloses a WeChat-based access control method.
  • the mobile terminal scans the two-dimensional code to obtain the property information; the access control server sends the access selection information; the visitor mobile terminal receives the access selection information and sends the access request information; the access control server sends the access request information, and the resident mobile terminal confirms, if confirmed If the success succeeds, the confirmation success message is sent; after the visitor mobile terminal receives the confirmation success message, the door opening request information is sent, and the access control server determines that the drive control unit opens the door.
  • Chinese Patent Application No. 201410032664.6 discloses an access control method, apparatus and access control system.
  • the access control system receives the visit request sent by the visited user terminal; the visit request includes the terminal information of the visited user terminal; when the access control system determines that the visited user terminal has the access qualification, generates the temporary key of the visited user terminal according to the visit request.
  • the access control system sends the temporary key to the visiting user terminal so that the visiting user terminal has the access qualification.
  • Chinese Patent Application No. 201410459938.X discloses an access control system based on a smartphone and a control method thereof.
  • the user's smart phone uses the dynamic release code to enter and exit the access control system, realizing the hardware-free terminalization and unmanned management of the access control system.
  • the visitor sends an access request to the smart mobile terminal of the household through the smart mobile terminal, and the visitor confirms that the visitor is eligible for admission.
  • the prior art provides a system and method that allows a visitor to send an access request regardless of whether the resident agrees to the visitor, and the resident is passively accepting the access request, so there is a problem that the resident may be disturbed or harassed. For example, when a household does not want to be disturbed, the visitor can still send an access request, thereby interfering with the household. What's more, when a household wants to reject a visitor, the visitor may continually send an access request, causing the occupant to be harassed.
  • the object of the present invention is to provide a method and system for authenticating a guest who has the initiative and can protect the privacy of the resident.
  • the system and method do not need to modify the hardware of the original system, and only need to perform software functions. Fine-tuning enables the authorization of visitors to enter and ensure that residents are not disturbed or harassed while ensuring the privacy of the residents.
  • Visitor authentication methods including identity authentication and access authorization, specifically:
  • the visitor connects to the server through the guest client, selects the household code and inputs the corresponding access verification code to request the passage; the server stores the household information of the household; the household information includes the household code and the access verification code. ;
  • the server determines whether the access verification code is correct; if yes, perform step 1.1.3];
  • the visitor connects to the server through the guest client, selects the group information and inputs the access verification code to request the passage; the server stores the group information and the household information of the corresponding household; the household information includes the access verification code;
  • the server determines whether there is household information corresponding to the access verification code in the group information; if yes, perform step 1.2.3];
  • the corresponding resident generates the release authorization information through the resident client or the server;
  • the verification end obtains the release authorization information to determine whether there is a right to pass; if yes, issue a release indication signal.
  • the server stores the gate information of the gate; the gate information has a corresponding relationship with the verification terminal;
  • the gate information When the visitor requests to communicate with the server through the guest client, the gate information needs to be selected; after the release authorization information is generated, the verification terminal corresponding to the selected gate information obtains the release authorization information.
  • the server stores the gate information of the gate; the resident allows the visitor to have the approval authority from the gate; the resident obtains the approval authority according to one of the following ways:
  • the household information includes an accessible time period and/or a do not disturb switch
  • the visitor can send a pass request to the corresponding resident
  • the server stores the visitor information of the visitor
  • the household information includes a white list and/or a blacklist; the white list and/or blacklist corresponding to the visitor information;
  • the server When the visitor corresponding to the whitelist accesses the corresponding resident, the server directly generates the release authorization information that allows the passage;
  • the server When the visitor corresponding to the blacklist accesses the corresponding resident, the server directly generates the release authorization information for prohibiting the traffic.
  • the present invention also provides a corresponding guest authentication system comprising a server, a household client, a guest client and a verifier, the server, the resident client, the guest client and the authenticator being connected via a network, wherein:
  • the server or the verifier stores household information of the household; the household information includes household identity information and an access verification code; the household information further includes household display information; the household display information is a household code or group information; There is a correspondence between the grouping information and the household information;
  • the guest client includes a request module for transmitting a pass request
  • the server or the verifier includes a verification module for determining whether the access verification code is correct;
  • the resident client includes a receiving module for receiving a pass request
  • the server or the authenticator or the resident client includes an authorization module for generating release authorization information
  • the verifier is used to determine whether there is a right to pass, and if so, a release indication signal is issued.
  • the server stores the gate information of the gate; the gate information has a corresponding relationship with the validator;
  • the request module includes a gate information selection unit
  • the authorization module After the authorization module generates the release authorization information, the validator corresponding to the selected gate information is obtained. The release authorization information.
  • the server stores the gate information of the gate
  • the gate information has a corresponding relationship with the household information; the household having a corresponding relationship with the gate information has the right to allow the visitor to pass through the corresponding gate.
  • the server stores the gate information and the role information of the gate; the household information has a corresponding relationship with the role information; and the gate information has a corresponding relationship with the role information;
  • the household corresponding to the character information corresponding to the gate information has the right to allow the visitor to pass through the corresponding gate.
  • the verifier further includes a recording device and a feature acquisition module for acquiring visitor feature information by the recording device; the resident client receives the visitor feature information acquired by the feature acquisition module.
  • the resident does not need to provide any information related to the real identity (such as name, room number, telephone number, etc.) to the outside world, and provide a household code. Visitors who interact with the household can easily obtain the household code from the household in various ways, but for strangers, it is impossible to obtain any privacy of the user through the household code, thus protecting the privacy of the household. residents can modify their household code at any time if needed. In addition, if needed, residents can also set access verification codes to limit access by unrelated people.
  • the tenants may not even provide the resident code. For the outside world, no information about the households can be seen at all, thus maximizing the privacy of the residents. However, as long as the resident is willing to provide an access verification code, the visitor can still make an access request and enter after authorization. Residents can change the access verification code at any time if needed.
  • the household can set the whitelist information, and the visitors on the whitelist information can directly obtain the authorization. Convenient for friends and family. residents can also set blacklist information to block access by visitors on blacklisted information.
  • the feature information of the visitor can be directly sent to the household's mobile phone through the video recorder installed on the verifier, which is convenient for the residents to judge and improve the security.
  • the cost of the visitor authentication system provided by the present invention is also low.
  • the hardware only needs to add a validator, which can also be implemented by devices such as smartphones. Even in small applications, servers and validators can be combined to further reduce implementation costs.
  • FIG. 1 is a flow of identity authentication in a guest authentication method.
  • Figure 3 is another flow of identity authentication in the guest authentication method.
  • FIG. 5 is a block diagram showing an embodiment of a network connection between a server, a resident client, a guest client, and a verifier.
  • FIG. 6 is a block diagram showing another embodiment of a network connection between a server, a resident client, a guest client, and a verifier.
  • Fig. 7 is a schematic structural view of an embodiment of a verifier.
  • Fig. 8 is a schematic structural view of another embodiment of the verifier.
  • FIG. 9 is a schematic structural diagram of a scheme of integrating a server and a verifier.
  • FIG. 1 shows a flow of identity authentication in a guest authentication method, including the following steps:
  • the visitor connects to the server through the guest client, selects the resident code, and inputs a corresponding access verification code to request the pass;
  • the server can be a computer server or a controller of the corresponding access control system.
  • the server stores the household information of the household; the household information includes the household code and the access verification code.
  • Household information can also include household identity information such as usernames and passwords.
  • Table 1 shows a way to store household information.
  • the corresponding resident does not have an access verification code, that is, the corresponding access verification code is empty, the visitor does not need to input the access verification code, which is equivalent to the resident has no restrictions on the visitor.
  • the household code with the household code "Monkey" does not have an access verification code.
  • the visitor can also input relevant access information, such as the visitor's name, phone number, unit, cause, and desire to pass the door.
  • step S12 the server determines whether the access verification code is correct; if yes, step S13 is performed.
  • the server receives the resident code selected by the guest client and the input access verification code, and compares it with the corresponding household code record in the household information, and determines whether the access verification code input by the visitor and the corresponding record storage access verification The codes are the same, and if so, step S13 is performed.
  • the household client corresponding to the household obtains the request.
  • the corresponding household refers to the household corresponding to the household code selected in step S11.
  • the household client of the household is connected to the server to obtain a visitor's request for access; the household identity information is authenticated before the request is obtained.
  • the household identity information can be achieved by username and password, as shown in Table 1.
  • the access request may include relevant access information such as visitor name, phone number, unit, cause, and desire to pass the door.
  • FIG. 2 shows the flow of the authorization in the visitor authentication method, including the following steps:
  • the corresponding household generates the release authorization information through the household client or the server;
  • the resident can directly generate the release authorization information through the APP software pre-installed on the resident client; or the connection between the resident client and the server, and the release authorization information generated by the software pre-installed by the server.
  • the release authorization information may be an indication of allowing or not allowing traffic, a time period during which access is allowed or the number of times allowed to pass, and may include information such as a gate allowing passage.
  • the verification end obtains the release authorization information, and determines whether there is a right to pass; if yes, issues a release indication signal.
  • the verification end is used to determine whether the corresponding visitor has the right to pass, and if yes, issue a release indication signal.
  • the verification terminal can be a dedicated device or a general-purpose device such as a mobile phone or a tablet. If the authentication end is a device, it is usually located at the gate where the visitor wants to pass. In small applications, the server and verification side can be combined to reduce costs. For example, you can use a tablet that can connect to the Internet to implement both server and authentication functions.
  • the verification side can obtain the release authorization information.
  • the verification terminal can directly connect with the resident client to obtain the release authorization information; the resident client can also first send the release authorization information to the server, and then the verification terminal obtains from the server.
  • the resident client may also first send the release authorization information to the guest client, and then the verification terminal obtains from the guest client; the resident client may also first send the release authorization information to the server, and then the guest client from the server. Obtained, and finally obtained by the verification terminal from the guest client.
  • the verification terminal may directly connect with the server to obtain the release authorization information; or may be obtained by the guest client from the server first, and then obtained by the verification terminal from the guest client.
  • the verification end determines whether there is a right to pass according to the release authorization information.
  • the release authorization information may be an indication of allowing or not allowing traffic, or a time period allowing passage or a number of allowed passages, and the verification terminal may determine whether there is a right to pass based on the information.
  • the difference between the embodiment and the embodiment 1 is that the identity authentication process in the guest authentication method is different, as shown in FIG. 3, including the following steps:
  • the visitor connects to the server through the guest client, selects the group information, and inputs the access verification code to request the pass;
  • the server can be a computer server or a controller of the corresponding access control system.
  • the server stores group information and household information of the corresponding household; the household information includes an access verification code.
  • Household information can also include household identity information such as usernames and passwords.
  • the group information may be a room number, a company name, a department name, etc., and has a corresponding relationship with the user information, and is used to classify the household information, so that the visitor can perform the query and operation.
  • Grouping information can also be used to filter when access verification codes are repeated.
  • Table 2 illustrates a storage method of group information and corresponding household information.
  • Table 2 A group information and corresponding household information
  • Table 3a and Table 3b respectively illustrate the case where only 1 packet and packet are empty, and the visitor can directly input the access verification code without selecting the group information.
  • Table 4 illustrates another storage method for grouping information and corresponding household information.
  • Table 4 Another group information and corresponding household information
  • the visitor can also input relevant access information, such as the name of the visitor, the phone number, the unit, the cause, and the door to the door.
  • step S32 the server determines whether there is household information corresponding to the access verification code in the group information; if yes, step S33 is performed.
  • the server receives the group information selected by the guest client and the input access verification code, and determines whether there is household information corresponding to the access verification code in the group information, and if yes, step S33 is performed.
  • the household client corresponding to the household obtains the request.
  • the corresponding household refers to the household corresponding to the household information determined in the step S32.
  • the household client of the household is connected to the server to obtain a visitor's request for access; the household identity information is authenticated before the request is obtained.
  • the gate information of the gate is stored on the server, and the gate information has a corresponding relationship with the verification end.
  • the gate information when the visitor requests to communicate with the server through the guest client, the gate information needs to be selected; after the release authorization information is generated, the verification terminal corresponding to the selected gate information obtains the release authorization information.
  • Each gate may have a corresponding verification end, and the release authorization information should not be sent to all verification terminals. Only the verification end corresponding to the visitor's wanted gate can receive the corresponding release authorization information.
  • the gate information of the gate is stored on the server; the resident is allowed to have the approval authority from the gate.
  • residents are granted approval authority in one of the following ways:
  • the household corresponding to the character information corresponding to the gate information has the right to allow the visitor to pass through the corresponding gate.
  • the R&D department of a company has a separate gate, and only certain personnel have the right to allow visitors to pass through the door of the R&D department; at this time, the gate information of the R&D department has a corresponding relationship with the household information of the specific personnel. This way is the personal way mentioned above, and each specific person corresponds to one individual.
  • the R&D department of a company has a separate door. Only the R&D department and management personnel have the right to allow visitors to pass through the door of the R&D department. At this time, the door information of the R&D department has a corresponding relationship with the R&D department and management. .
  • This method is the above-mentioned role mode, and the R&D department and the management team each have a corresponding role.
  • the household information includes an accessible time period and/or a do not disturb switch.
  • the visitor can send a pass request to the corresponding resident.
  • the occupant can set relevant options according to his actual situation.
  • the client can be connected to the server and the access time period can be set to 10:00-12:00. Visitors can send a pass request to the resident between 10:00-12:00.
  • the accessible time period in the household information can also be changed to the inaccessible time period, which varies from person to person.
  • the resident client can be connected to the server to open the do not disturb switch of the household information. At this time, the visitor is prohibited from sending a pass request to the resident. After the resident finishes writing the report, the resident client can be connected to the server to turn off the do not disturb switch of the household information. At this time, the visitor is allowed to send a pass request to the resident.
  • the server stores the visitor information of the visitor; the household information includes a whitelist and/or a blacklist; and the whitelist and/or the blacklist correspond to the visitor information.
  • the server When the visitor corresponding to the whitelist accesses the corresponding resident, the server directly generates the permission to pass. Line authorization information.
  • the server When the visitor corresponding to the blacklist accesses the corresponding resident, the server directly generates the release authorization information forbidden.
  • the occupant can connect to the server through the resident client and set up a whitelist and/or blacklist in the occupant information, ie a visitor who will definitely agree and/or will not agree.
  • the whitelist and/or the blacklist correspond to the visitor information.
  • the server directly generates the release authorization information that is allowed to pass.
  • the server directly generates the release authorization information forbidden.
  • the household client 2 and the guest client 3 may be devices such as a mobile phone, a notebook computer, a tablet computer, and the like.
  • the example shown in FIG. 4 also includes the mechanism 5, the resident 7, the visitor 8, and the gate 9.
  • the institution can be a government department, a company, an office building or a residential community.
  • the verifier 4 generally has a correspondence with the mechanism 5, that is, a certain verifier 4 is usually affiliated with a certain mechanism 5.
  • the household 7 and the household client 2 are contained within an oval box indicating that the household 7 uses the household client 2.
  • the guest 8 and guest client 3 are contained within an oval box indicating that the guest 8 is using the guest client 3.
  • the server 1, the resident client 2, the guest client 3, and the authenticator 4 are connected through the network 6.
  • Network 6 can be the Internet.
  • Figure 5 illustrates an embodiment of a network connection between server 1, resident client 2, guest client 3, and verifier 4.
  • the network card 13 of the server 1 is connected to the router 15 via the network cable 14, and is connected to the network 6 through the router 15.
  • the customer client 2 and the guest client 3 are mobile phones, and have built-in RF communication modules 61, such as GPRS, 3G, 4G, etc., and can be directly connected to the network 6.
  • the verifier 4 includes a verification processor 41 and an output device 42 for issuing a release indication signal.
  • the radio frequency communication module 61 is installed in the verifier 4, and can also be directly connected to the network 6.
  • the server 1 usually has a fixed domain name or address, and the resident client 2 and the guest client 3 can access the server 1 through a browser or a developed APP application.
  • the verifier 4 can directly establish a network connection with the server 1 and communicate by means of the HTTP protocol or the like.
  • the customer client 2, the guest client 3 and the verifier 4 are both connected to the network 6 via the radio frequency communication module 61, and have no fixed network address, but they can all communicate directly with the server 1, so the resident client 2 and the guest client
  • the communication between the 3 and the verifier 4 can be realized by the server 1 relay. For example, if the household client 2 wants to send a message to the verifier 4, the household client 2 can first send the message to the server 1 and then forward it by the server 1 to the relevant verifier 4, and vice versa.
  • FIG. 6 shows another embodiment of a network connection between server 1, resident client 2, guest client 3 and verifier 4.
  • the network card 13 of the server 1 is connected to the router 15 via the network cable 14, and is connected to the network 6 through the router 15.
  • the customer client 2 and the guest client 3 are mobile phones with a built-in RF communication module 61 that can be directly connected to the network 6; the guest client 3 also has a built-in wireless communication module 62, such as a Bluetooth or WIFI module.
  • the verifier 4 includes a verification processor 41 and an output device 42 for issuing a release indication signal.
  • a wireless communication module 62 is also installed in the authenticator 4.
  • the resident client 2 and the guest client 3 can access the server 1 through a browser or an installed APP application.
  • Both the guest client 3 and the verifier 4 have wireless communication modules 62 that can communicate directly with each other. Since the verifier 4 cannot be directly connected to the network 6, the communication between the verifier 4 and the server 1 can be realized by the relay of the guest client 3. For example, if the server 1 wants to send a message to the verifier 4, the server 1 can first send the message to the guest client 3, which is then forwarded by the guest client 3 to the verifier 4, and vice versa. In the embodiment shown in FIG. 3, the verifier 4 does not have the radio frequency communication module 61, which can save communication costs.
  • the server 1 or the verifier 4 stores the household information of the household 7. If the household information is stored on the verifier 4, the household information of the household 7 of the corresponding institution 5 is usually stored only on the verifier 4. If the household information is stored on the server 1, the server 1 can store the household information of all the households 7.
  • the household information can also be stored in the cloud, for example, the cloud storage space provided by the cloud storage service provider, the cloud is connected to the network 6, and the server 1 or the verifier 4 accesses the household letter stored on the cloud through the network 6. interest. If the household information is stored in the cloud, the cloud can be considered as external storage for Server 1 or Verifier 4.
  • Household information includes household identity information and access verification codes.
  • the household identity information may be a user name and a login password, or may be a fingerprint information of the corresponding household.
  • Household information can also include information such as household name, room number, and contact information.
  • the access verification code is usually set by the resident 7 and can be used to block access requests from strangers. If the visitor 8 wants to access the resident 7, he/she must first enter the corresponding access verification code, and the system can determine the correct access before sending the access request. By setting the access verification code autonomously, the resident 7 can be well protected from strangers. If the household 7 does not set an access verification code, or the corresponding access verification code is empty, the visitor 8 does not need to input the access verification code, which is equivalent to the resident 7 has no restriction on the access request of the visitor 8.
  • Household information also includes household display information.
  • the household display information is used to facilitate the visitor 8 to screen the household 7 to be accessed through the guest client 3.
  • the household display information is the household code or group information.
  • the household code is the access name displayed by the household 7 and is similar to the network name in the web chat application, and does not need to contain the real information of the household 7.
  • the privacy of the household 7 can be protected by using the household code instead of the real information. If needed, Resident 7 can also change his or her household code at any time to better protect personal privacy.
  • Table 1 is the case where the household code is used as the household display information.
  • the group information may be information such as a room number, a company name, a department name, etc., and a correspondence relationship with the household information.
  • the grouping information is used to classify the household information, so that the visitor 8 can perform the query and operation.
  • the grouping information can also be used for screening when the access verification code is repeated, as shown in the example in Table 2. If only one grouping information or grouping information is empty, the visitor 8 can directly input the access verification code without selecting the grouping information, as shown in the examples shown in Tables 3a and 3b.
  • the server 1 or the verifier 4 stores the household information, it can be used as a server.
  • the guest client 3 includes a request module for transmitting a pass request.
  • the visitor 8 connects to the server through the request module in the guest client 3.
  • the household displays information When it is the household code, the visitor 8 selects the household code by the request module and inputs the corresponding access verification code, and then sends a pass request to the server.
  • the household display information is group information, the visitor 8 selects the group information through the request module and inputs the access verification code, and then sends a pass request to the server. If the household information includes both the household code and the group information, it can be determined by the actual selection of the visitor 8. Taking Table 4 as an example, if the visitor 8 selects the household code "Mr.
  • the corresponding access verification code is "a1b2c3", which is equivalent to the household display information being the household code; if the visitor 8 selects the "C company R&D department", The corresponding access verification code is "abcdef” or "a1b2c3", which is equivalent to the household display information being group information.
  • the request module may be a page sent by the server, or may be an application software installed on the guest client 3.
  • the server includes a verification module for determining whether the access verification code is correct. That is, the verification module is located in the server 1 or the verifier 4 in which the household information is stored.
  • the server determines whether the access verification code is correct by the check module.
  • the verification module receives the household code and the access verification code sent by the request module, and compares with the corresponding household code record in the household information, and determines whether the access verification code input by the visitor and the corresponding record storage access. The verification code is the same; if it is the same, the access verification code is correct.
  • the verification module receives the group information and the access verification code sent by the request module, and determines whether there is household information corresponding to the access verification code in the group information; if yes, the access verification code is correct.
  • the resident client 2 includes a receiving module for receiving a pass request.
  • the receiving module of the corresponding resident client 2 receives the access request forwarded by the verification module.
  • the corresponding household client 2 refers to the household client 2 of the household 7 corresponding to the household information record determined by the verification module.
  • the receiving module needs to connect with the server and authenticate with the household identity information.
  • the identity authentication of the household can be realized by the form of the user name and password as shown in Table 1, or by the fingerprint of the household.
  • the access request may include relevant access information, such as the name of the visitor, the phone number, the unit, the cause, the door to be accessed, and the like. This information is previously entered by the visitor 8 through the request module of the guest client 3.
  • Server 1 or verifier 4 or resident client 2 includes an authorization module for generating release authorization information. After receiving the access request by the receiving module, the resident 7 generates the release authorization information through the authorization module.
  • the release authorization information may be an indication of allowing or not allowing traffic, or a time period information allowing passage or a number of times allowed to pass, and may also include information such as a gate allowing passage.
  • the verifier 4 is configured to determine whether the visitor 8 has a right to pass based on the release authorization information, and if so, issue a release indication signal.
  • the verifier 4 can be a dedicated device or a general-purpose device, such as a mobile phone, a tablet, etc., and is usually located at the gate 9 where the visitor 8 wants to pass.
  • the verifier 4 can obtain the release authorization information.
  • the authenticator 4 can directly connect with the resident client 2 to obtain the release authorization information; the resident client 2 can also first send the release authorization information to the server 1, and then the authenticator 4 obtained from the server 1; the resident client 2 may also first send the release authorization information to the guest client 3, and then from the guest client 3 by the verifier 4; the resident client 2 may also first send the release authorization information to the server. 1, then obtained by the guest client 3 from the server 1, and finally obtained by the verifier 4 from the guest client 3.
  • the verifier 4 can directly connect with the server 1 to obtain the release authorization information; it can also be obtained from the server 1 by the guest client 3, and then from the guest client 3 by the verifier 4 obtain.
  • FIG. 7 shows an embodiment of the verifier 4.
  • the verifier 4 includes a verification processor 41 and an output device 42 for issuing a release indication signal.
  • the verification processor 41 runs a software module for determining whether the visitor has a pass right.
  • the output device 42 includes a display screen 422 through which a release prompt can be issued. For example, information about the visitor and the household and information about the cause can be displayed on the display, and the property manager can allow the visitor to enter after receiving the release prompt.
  • the release indication signal is equivalent to a release prompt issued by the display screen 422.
  • the verifier 4 can also be implemented by a general-purpose device such as a tablet computer, a mobile phone, or a computer integrated machine.
  • FIG. 8 shows another embodiment of the verifier 4.
  • the gate 9 is typically equipped with an electronic lock 512 that is controlled by the access control 51.
  • the output signal of the access 51 can control the opening and closing of the electronic lock 512 to effect control of the gate 9.
  • the verifier 4 includes a verification processor 41 and an output device 42 for issuing a release indication signal.
  • the verification processor 41 runs a software module for determining whether the visitor has a pass right.
  • the output device 42 is a control signal circuit that can generate a door opening control signal 421, and the door opening control signal 421 is input to the unlocking signal terminal 511 of the access control 51 to cause the electronic lock 512 to be controlled to be turned on.
  • the release instruction signal is equivalent to the door open control signal 421.
  • FIG. 9 shows a scheme for integrating the server 1 and the verifier 4, including the server 11, the resident client 2, and the guest client 3.
  • the network card 13 of the server 11 is connected to the router 15 via the network cable 14, and is connected to the network 6 through the router 15.
  • the resident client 2 and the guest client 3 are connected to the network 6 via the radio communication module 61.
  • the server 11 includes a service processor 111 and an output device 42 for simultaneously implementing the functions of the server 1 and the verifier 4 in FIG. 4, that is, the related software modules and stored data in the server 1 and the verifier 4 are in the server 11 At the same time.
  • the service processor 111 can be implemented by an embedded processor, which can run a software module and has its own memory.
  • Each gate 9 may have a corresponding validator 4, and release authorization information should not be sent to all validators 4.
  • the server 1 can also store the gate information of the gate, and the gate information has a corresponding relationship with the verifier 4.
  • the request module may include a gate information selection unit; after the authorization module generates the release authorization information, only the validator 4 corresponding to the selected gate information may obtain the release authorization information.
  • the server 1 can also store the gate information of the gate, and the gate information has a corresponding relationship with the household information; the household 7 corresponding to the gate information has the right to allow the visitor 8 to pass through the corresponding gate 9.
  • Table 5a and Table 5b respectively illustrate the household information and the gate information
  • Table 5c illustrates the correspondence between the gate information and the household information.
  • Table 5c only the resident 7 with the username "002" has the right to allow the visitor 8 to pass through the "B" gate 9.
  • the server 1 can also store the gate information and the role information of the gate; the household information has a corresponding relationship with the role information; the gate information has a corresponding relationship with the role information; and the household 7 corresponding to the role information corresponding to the gate information has the right to allow Visitor 8 passes from the corresponding gate 9.
  • Table 6a, Table 6b, and Table 6c respectively illustrate household information, gate information, and role information.
  • Table 6d shows the correspondence between household information and role information
  • Table 6e shows the gate information and roles. Correspondence of information.
  • the role information of the household 7 with the user name "001" is “management”
  • the role information of the household 7 with the user name "003" is “R&D”
  • the user name is "002”.
  • the role information of Household 7 is “Management” and “R&D Department”. It can be seen from Table 6e that the household 7 whose role information is “management” can allow the visitor 8 to pass through the "A” and "B” gates 9, and the households 7 whose role information is "R&D” can only allow the visitor 8 9 from the "A” gate. It is not difficult to see that the household 7 with the user name "003" has no right to allow the visitor 8 to pass through the "B” gate 9.
  • the verifier 4 further includes a recording device and a feature acquisition module that acquires visitor feature information through the recording device.
  • the resident client 2 receives the visitor feature information acquired by the feature acquisition module.
  • the recording device can be used to obtain feature information such as images, sounds, and the like of the visitor 8, and the feature information of the visitor 8 is transmitted to the corresponding resident client 2, which facilitates identification of the visitor 8.
  • the household information may also include an accessible time period, and the visitor 8 may send a pass request to the corresponding resident 7 when the current time is within the accessible time period.
  • the household information may also include a do not disturb switch, and the visitor 8 is prohibited from sending a pass request to the corresponding resident 7 when the do not disturb switch is turned on.
  • the server 1 may also store visitor information; the household information may also include a whitelist and/or a blacklist; the whitelist and/or blacklist correspond to the visitor information.
  • the server When the visitor 8 corresponding to the whitelist accesses the corresponding resident 7, the server directly generates the release authorization information that allows the passage.
  • the server When the visitor corresponding to the blacklist accesses the corresponding resident, the server directly generates the release authorization information forbidden.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种访客认证方法和***，方法的主要步骤包括访客(8)通过访客客户机(3)选择住户代号或分组并输入对应的访问验证码，服务端判断是否正确，如正确通过对应住户客户机(2)生成放行授权信息，验证端根据该放行授权信息判断是否可通行；方法支持同时有多个大门(9)，支持个人或角色对不同大门(9)设置不同的通行权限，支持设置可访问时间段、勿扰开关选项，支持设置白名单和黑名单；***包括服务器(1)、住户客户机(2)、访客客户机(3)和验证器(4)，验证器(4)支持摄录访客(8)的特征信息供住户(7)判断；该方法和***可以很好地保护住户(7)的隐私，防止骚扰，并且灵活性高，实施成本低。

Description

访客认证方法和*** 技术领域
本发明属于信息技术领域，特别涉及一种访客认证方法和***。
背景技术
大多数居民小区、写字楼等社区都安装了门禁***，用于限制无关人员进入。采用通行卡(如IC卡)等方式的门禁***只适用住户的进入，对访客不适用。虽然有些社区安装了可视电话等门禁***，用于访客的授权，但该类***不仅投资大，后期维护成本高，而且住户不在社区时，访客就无法进入，对住户和访客都造成了不便。随着网络和智能手机的普及，使用智能移动终端实现门禁功能成为一种趋势。
中国专利申请号201410000185.6公开了一种基于微信的门禁控制方法。该专利中，访客移动端扫描二维码得到物业信息；门禁服务器发送访问选择信息；访客移动端接收访问选择信息后发送访问请求信息；门禁服务器发送访问请求信息，住户移动端进行确认，若确认成功则发送确认成功信息；访客移动端接收到确认成功信息后发送开门请求信息，门禁服务器判断后驱动控制单元开门。
中国专利申请号201410032664.6公开了一种门禁控制方法、装置和门禁***。门禁***接收被拜访用户终端发送的拜访请求；拜访请求中包括拜访用户终端的终端信息；当门禁***判断出被拜访用户终端具有准入资格时，根据拜访请求，生成拜访用户终端的临时密钥；门禁***将述临时密钥发送给拜访用户终端，以便拜访用户终端具有准入资格。
中国专利申请号201410459938.X公开了基于智能手机使用的门禁***及其控制方法。通过用户智能手机使用动态放行码的方式进出门禁***，实现了门禁***的无硬件终端化和无人化的管理。
上述发明中，访客都是通过智能移动终端向住户的智能移动终端发送访问请求，住户进行确认后访客才具有准入资格。这就意味着住户必须公开其部分信息(例如办公室/房间号、手机号、姓名等)访客才能对其进行访问，否则访客无法区分住户。由于任何陌生人都有可能通过网络看到住户的相关信息，从而导致住户隐私可能被泄露的严重问题。
此外，现有技术提供的***和方法，无论住户是否同意访客都可以发送访问请求，住户是被动接受访问请求，因此存在住户可能被干扰或骚扰的问题。例如，当住户不想被打扰时，访客照样可以发送访问请求，从而干扰了住户。更有甚者，当住户想拒绝某一访客时，访客可能会不断发送访问请求，从而导致住户被骚扰。
无论是泄露住户隐私，还是干扰或骚扰住户，都可能会导致住户在使用时的抵触情绪，进而关闭访问通道(例如断掉网络或卸载相关APP软件)，限制了上述专利申请的实用性。
发明内容
为了克服上述现有技术的缺点，本发明的目的在于提供一种住户具有主动权且能保护住户隐私的访客认证方法和***，该***和方法无需改造原有***的硬件，只需对软件功能进行微调，即可实现在确保住户隐私的前提下，实现对访客进入的授权，并确保住户不会被干扰或骚扰。
为了实现上述目的，本发明采用的技术方案是：
访客认证方法，包括身份认证和通行授权两大步骤，具体地：
1】身份认证，采用如下方式之一：
1.1】方式1：
1.1.1】访客通过访客客户机与服务端连接，选择住户代号并输入对应的访问验证码，请求通行；所述服务端存储有住户的住户信息；所述住户信息包括住户代号和访问验证码；
1.1.2】所述服务端判断该访问验证码是否正确；如是，执行步骤1.1.3】；
1.1.3】对应住户的住户客户机获得该请求；
1.2】方式2：
1.2.1】访客通过访客客户机与服务端连接，选择分组信息并输入访问验证码，请求通行；所述服务端存储有分组信息以及对应住户的住户信息；所述住户信息包括访问验证码；
1.2.2】服务端判断该分组信息中是否有与该访问验证码对应的住户信息；如是，执行步骤1.2.3】；
1.2.3】对应住户的住户客户机获得该请求；
2】通行授权
2.1】对应住户通过所述住户客户机或所述服务端生成放行授权信息；
2.2】验证端获得该放行授权信息，判断是否有通行的权利；如是，发出放行指示信号。
进一步地，所述服务端存储有大门的大门信息；所述大门信息与所述验证端存在对应关系；
所述访客通过访客客户机与服务端连接请求通行时，需选择所述大门信息；生成所述放行授权信息后，与所选大门信息对应的验证端获得该放行授权信息。
进一步地，所述服务端存储有大门的大门信息；所述住户允许访客从大门通行需拥有审批权限；所述住户按照如下方式之一获得所述审批权限：
个人方式：
建立所述大门信息与所述住户信息的对应关系；与大门信息有对应关系的住户，才有权允许访客从对应大门通行；
角色方式：
在所述服务端建立角色信息；建立所述角色信息与所述住户信息的对应关系；建立所述大门信息与所述角色信息的对应关系；与大门信息有对应关系的角色信息对应的住户，才有权允许访客从对应大门通行。
进一步地，所述住户信息包括可访问时间段和/或勿扰开关；
当前时间在所述可访问时间段内时，访客才能向对应住户发送通行请求；
所述勿扰开关打开时禁止访客向对应住户发送通行请求。
进一步地，所述服务端存储有所述访客的访客信息；
所述住户信息包括白名单和/或黑名单；所述白名单和/或黑名单与所述访客信息对应；
与所述白名单对应的访客在访问对应住户时，所述服务端直接生成允许通行的放行授权信息；
与所述黑名单对应的访客在访问对应住户时，所述服务端直接生成禁止通行的放行授权信息。
本发明还提供了相应的访客认证***，包括服务器、住户客户机、访客客户机和验证器，所述服务器、住户客户机、访客客户机和验证器通过网络连接，其中：
所述服务器或验证器存储有住户的住户信息；所述住户信息包括住户身份信息和访问验证码；所述住户信息还包括住户显示信息；所述住户显示信息是住户代号或分组信息；所述分组信息和所述住户信息存在对应关系；
所述访客客户机包括用于发送通行请求的请求模块；
所述服务器或验证器包括用于判断访问验证码是否正确的核对模块；
所述住户客户机包括用于接收通行请求的接收模块；
所述服务器或验证器或住户客户机包括用于生成放行授权信息的授权模块；
所述验证器用于判断是否有通行的权利，如是则发出放行指示信号。
进一步地，所述服务器存储有大门的大门信息；所述大门信息与所述验证器存在对应关系；
所述请求模块中包括大门信息选择单元；
所述授权模块生成放行授权信息后，与所选大门信息对应的验证器获得 该放行授权信息。
进一步地，所述服务器存储有大门的大门信息；
所述大门信息与所述住户信息存在对应关系；与大门信息有对应关系的住户，才有权允许访客从对应大门通行。
进一步地，所述服务器存储有大门的大门信息和角色信息；所述住户信息与所述角色信息存在对应关系；所述大门信息与所述角色信息存在对应关系；
与大门信息有对应关系的角色信息对应的住户，才有权允许访客从对应大门通行。
进一步地，所述验证器还包括摄录装置以及通过摄录装置获取访客特征信息的特征获取模块；所述住户客户机接收特征获取模块获取的访客特征信息。
与现有技术相比，本发明的有益效果是：
1、住户无需对外界提供任何与真实身份相关的信息(如姓名，房号，电话等)，提供一个住户代号即可。与住户有交往的访客可以很容易通过各种方式从住户处获得这个住户代号，但对陌生人而言，根本无法通过住户代号获得用户的任何隐私，从而很好的保护了住户的隐私。如果需要，住户可以随时对其住户代号进行修改。此外，如果需要，住户还可以设置访问验证码，从而限制无关人员的访问。
2、更进一步，住户甚至连住户代号都可以不用提供。对外界而言，根本看不到住户的任何信息，从而最大限度地保护了住户的隐私。但只要住户愿意提供访问验证码，访客还是可以发出访问请求，并在获得授权后进入。如果需要，住户也可以随时改变访问验证码。
3、住户可以随时设置可访问时间段和/或勿扰开关选项，从而保证住户在不想被干扰时不被干扰。
4、住户可设置白名单信息，白名单信息上的访客可直接获得通行授权， 方便亲朋好友的访问。住户还可以设置黑名单信息，阻止黑名单信息上的访客的访问。
5、支持一个物业同时有多个大门的情况，也支持各大门的通行权限不同的情况。支持住户或住户分类对不同大门设置不同的通行权限。
6、对于陌生访客，可通过验证器上安装的摄录装置将访客的特征信息直接发送到住户的手机上，便于住户判断，提高了安全性。
7、住户可远程随时对访客的通行要求做出决策，住户不在社区时也可进行核准，大大方便了住户和访客。
8、如果物业之前有门禁***，无需对物业原有门禁***的硬件进行改造，只需对软件功能进行微调即可，实施成本极低。
9、如果物业之前没有门禁***，采用本发明提供的访客认证***成本也很低。硬件除了服务器之外，只需要增加验证器，该验证器也可用智能手机等设备实现。甚至在小型应用中，可以将服务器和验证器合二为一，从而进一步降低了实施成本。
附图说明
图1是访客认证方法中身份认证的一种流程。
图2是访客认证方法中通行授权的流程。
图3是访客认证方法中身份认证的另一种流程。
图4是访客认证***的一种实施例。
图5是服务器、住户客户机、访客客户机、验证器之间网络连接的一种实施例的结构示意图。
图6是服务器、住户客户机、访客客户机、验证器之间网络连接的另一种实施例的结构示意图。
图7是验证器的一种实施例的结构示意图。
图8是验证器的另一种实施例的结构示意图。
图9是将服务器和验证器集成在一起的方案的结构示意图。
具体实施方式
下面结合附图和实施例详细说明本发明的实施方式。
实施例1
图1示出了访客认证方法中身份认证的一种流程，包括如下步骤：
在S11中，访客通过访客客户机与服务端连接，选择住户代号并输入对应的访问验证码，请求通行；
其中，服务端可以是电脑服务器，也可以是相应门禁***的控制器。服务端存储有住户的住户信息；住户信息包括住户代号和访问验证码。住户信息还可以包括住户身份信息，如用户名和密码。
表1示意了住户信息的一种存储方式。
表1 住户信息
用户名 密码 住户代号 访问验证码
001 123 张先生 a1b2c3
002 234 Room508 508
003 345 Monkey  
如果对应住户没有设访问验证码，即对应的访问验证码为空，则访客无需输入访问验证码，相当于住户对访客没有限制。在表1中，住户代号为“Monkey”的住户没有设置访问验证码。
在S11中，访客还可以输入相关的访问信息，如访客姓名、电话、单位、事由、欲通行大门等。
在S12中，服务端判断该访问验证码是否正确；如是，执行步骤S13。
在这一步中，服务端接收访客客户端选择的住户代号和输入的访问验证码，并与住户信息中对应的住户代号记录进行比较，判断访客输入的访问验证码是否与对应记录存储的访问验证码相同，如是则执行步骤S13。
在S13中，对应住户的住户客户机获得该请求。
在这一步中，对应住户是指与S11步骤所选住户代号对应的住户。该住户的住户客户机与服务端连接获得访客的通行请求；获得该请求前需通过住户身份信息认证。住户身份信息可通过用户名和密码实现，如表1所示。
通行请求可以包括相关的访问信息，如访客姓名、电话、单位、事由、欲通行大门等信息。
图2示出了访客认证方法中通行授权的流程，包括如下步骤：
在S21中，对应住户通过住户客户机或服务端生成放行授权信息；
住户可以通过住户客户机上预装的APP软件直接生成放行授权信息；也可以通过住户客户机与服务端连接，由服务端预装的软件生成放行授权信息。
放行授权信息可以是允许通行或不允许通行的指示，也可以是允许通行的时间段或允许通行的次数，还可以包含允许通行的大门等信息。
在S22中，验证端获得该放行授权信息，判断是否有通行的权利；如是，发出放行指示信号。
其中，验证端用于判断对应访客是否有通行的权利，如是则发出放行指示信号。验证端可以是专用设备，也可以是通用设备，如手机、平板电脑等。验证端如果是设备，通常位于访客欲通行的大门处。在小型应用中，可以将服务端和验证端合二为一以降低成本。例如，可以用一个可以连接互联网的平板电脑来同时实现服务端和验证端的功能。
验证端获得放行授权信息的方式可以有多种。例如，当放行授权信息由住户客户机生成时，验证端可以直接与住户客户机连接获得放行授权信息；住户客户机也可以先将放行授权信息发送到服务端，再由验证端从服务端获得；住户客户机也可以先将放行授权信息发送到访客客户机，再由验证端从访客客户机获得；住户客户机还可以先将放行授权信息发送到服务端，再由访客客户机从服务端获得，最后由验证端从访客客户机获得。再如，当放行授权信息由服务端生成时，验证端可以直接与服务端连接获得放行授权信息；也可以由访客客户机先从服务端获得，再由验证端从访客客户机获得。
验证端根据放行授权信息来确定是否有通行的权利。放行授权信息可以是允许通行或不允许通行的指示，也可以是允许通行的时间段或允许通行的次数，验证端可以根据这些信息来确定是否有通行的权利。
实施例2
该实施例与实施例1的不同之处在于，访客认证方法中的身份认证流程不同，如图3所示，包括如下步骤：
在S31中，访客通过访客客户机与服务端连接，选择分组信息并输入访问验证码，请求通行；
其中，服务端可以是一台电脑服务器，也可以是相应门禁***的控制器。服务端存储有分组信息以及对应住户的住户信息；住户信息包括访问验证码。住户信息还可以包括住户身份信息，如用户名和密码。分组信息可以是房号、公司名称、部门名称等，和用户信息存在对应关系，用于对住户信息进行分类，便于访客进行查询和操作。
分组信息还能在访问验证码重复时起到筛选作用。表2示意了分组信息及对应的住户信息的一种存储方式。
表2 一种分组信息及对应的住户信息
用户名 密码 分组信息 访问验证码
001 123 行政部 a1b2c3
002 234 市场部 A123456
003 345 市场部 a1b2c3
在表2中，虽然用户名“001”和“003”的访问验证码完全一样，但由于分组信息不同，因此不会出现查询结果重复的情况。当访客选择分组信息“行政部”并输入访问验证码“a1b2c3”时，等同于访问用户名为“001”的住户；当访客选择分组信息“市场部”并输入访问验证码“a1b2c3”时，等同于访问用户名为“003”的住户。
如果住户信息只有1个分组或者分组为空，则访客无需选择分组信息可 以直接输入访问验证码。表3a和表3b分别示意了只有1个分组和分组为空的情况，此时访客无需选择分组信息可以直接输入访问验证码。
Figure PCTCN2017073547-appb-000001
表4示意了分组信息及对应的住户信息的另一种存储方式。
表4 另一种分组信息及对应的住户信息
用户名 密码 分组信息 住户代号 访问验证码
001 123 A小区 张先生 a1b2c3
002 234 B公司市场部   abcdef
003 345 B公司市场部   123456
004 456 C公司研发部   abcdef
005 567 C公司研发部 李先生 a1b2c3
在表4中，如果访客选择了分组信息“C公司研发部”，会看到住户代号为“李先生”的住户，其对应用户名为“005”；但当访客输入的访问验证码为“abcdef”时，却等同于访问用户名为“004”的住户。
在S31中，访客还可以输入相关的访问信息，如访客姓名、电话、单位、事由、欲通行大门等。
在S32中，服务端判断该分组信息中是否有与该访问验证码对应的住户信息；如是，执行步骤S33。
在这一步中，服务端接收访客客户机选择的分组信息和输入的访问验证码，并判断该分组信息中是否有与该访问验证码对应的住户信息，如是则执行步骤S33。
在S33中，对应住户的住户客户机获得该请求。
在这一步中，对应住户是指在S32步骤中所确定住户信息对应的住户。该住户的住户客户机与服务端连接获得访客的通行请求；获得该请求前需通过住户身份信息认证。
实施例3
本实施例中，在服务端存储有大门的大门信息，大门信息与验证端存在对应关系。
本实施例中，访客通过访客客户机与服务端连接请求通行时，需选择大门信息；生成放行授权信息后，与所选大门信息对应的验证端获得该放行授权信息。
现实中，政府部门、企事业单位、写字楼和小区都可能存在有多个大门的情况。当访客通过访客客户机与服务端连接请求通行时，需选择欲通行大门的大门信息。每个大门都可能有对应的验证端，不应将放行授权信息发送到所有的验证端，只有与访客欲通行大门对应的验证端才可以收到对应的放行授权信息。
本实施例的其它步骤与实施例1或实施例2相同。
实施例4
现实中，政府部门、企事业单位、写字楼和小区都可能存在有多个大门的情况，并且各大门的通行权限可能不同。
本实施例中，在服务端存储有大门的大门信息；住户允许访客从大门通行需拥有审批权限。住户按照如下方式之一获得审批权限：
个人方式：
建立大门信息与住户信息的对应关系。与大门信息有对应关系的住户，才有权允许访客从对应大门通行。
角色方式：
在服务端建立角色信息；建立角色信息与住户信息的对应关系；建立大 门信息与角色信息的对应关系。与大门信息有对应关系的角色信息对应的住户，才有权允许访客从对应大门通行。
例如，某企业的研发部有单独的大门，只有特定人员才有权允许访客从研发部的大门通行；此时，研发部大门的大门信息与特定人员的住户信息存在对应关系。这种方式即为上述的个人方式，每个特定人员对应一个个人。
再如，某企业的研发部有单独的大门，只有研发部和管理层的人员有权允许访客从研发部的大门通行；此时，研发部大门的大门信息与研发部、管理层存在对应关系。这种方式即为上述的角色方式，研发部和管理层各对应一个角色。
实施例5
本实施例中，住户信息包括可访问时间段和/或勿扰开关。
当前时间在所述可访问时间段内时，访客才能向对应住户发送通行请求。
勿扰开关打开时禁止访客向对应住户发送通行请求。
本实施例中，住户可根据自己的实际情况，设置相关选项。
例如，住户10:00-12:00期间空闲，则可以通过住户客户机连接服务端，将可访问时间段设置为10:00-12:00。访客可以在10:00-12:00之间向该住户发送通行请求。住户信息中的可访问时间段也可以换成不可访问时间段，因人而异。
再如，住户正在写报告不想被访客打扰，则可以通过住户客户机连接服务端，将住户信息的勿扰开关打开，此时，禁止访客向该住户发送通行请求。当住户写完报告后，可以通过住户客户机连接服务端，将住户信息的勿扰开关关闭，此时，允许访客向该住户发送通行请求。
实施例6
本实施例中，服务端存储有访客的访客信息；住户信息包括白名单和/或黑名单；白名单和/或黑名单与访客信息对应。
与白名单对应的访客在访问对应住户时，服务端直接生成允许通行的放 行授权信息。
与黑名单对应的访客在访问对应住户时，服务端直接生成禁止通行的放行授权信息。
现实中，有些访客只要访问某住户，该住户就一定会同意，例如访客是住户的亲人时。同样，有些访客只要访问某住户，该住户就一定会不同意。为此，住户可以通过住户客户机连接服务端，设置住户信息中的白名单和/或黑名单，即一定会同意和/或一定不会同意的访客。其中，白名单和/或黑名单与访客信息对应。位于住户白名单上的访客在访问对应住户时，服务端直接生成允许通行的放行授权信息。位于住户黑名单上的访客在访问对应住户时，服务端直接生成禁止通行的放行授权信息。
图4示出了本发明中访客认证***的一种实施例，包括服务器1、住户客户机2、访客客户机3和验证器4。住户客户机2和访客客户机3可以是手机、笔记本电脑、平板电脑等设备。图4示出的例子还包括机构5、住户7、访客8和大门9。其中，机构可以是政府部门、企业、写字楼或住宅小区等。验证器4通常与机构5存在对应关系，即某个验证器4通常隶属于某一个机构5。住户7和住户客户机2包含在椭圆框内，表示该住户7使用该住户客户机2。访客8和访客客户机3包含在椭圆框内，表示该访客8使用该访客客户机3。
服务器1、住户客户机2、访客客户机3和验证器4通过网络6连接。网络6可以是互联网。
图5示出了服务器1、住户客户机2、访客客户机3和验证器4之间网络连接的一种实施例。在该实施例中，服务器1的网卡13通过网线14与路由器15连接，再通过路由器15连接到网络6中。住户客户机2和访客客户机3为手机，内置有射频通信模块61，如GPRS、3G、4G等模块，可以直接连接到网络6中。验证器4包括验证处理器41及用于发出放行指示信号的输出装置42。验证器4内安装了射频通信模块61，也可以直接连接到网络6中。 服务器1通常有固定的域名或地址，住户客户机2和访客客户机3可以通过浏览器或开发的APP应用程序访问服务器1。验证器4可以通过HTTP协议等方式直接与服务器1建立网络连接并进行通信。住户客户机2、访客客户机3与验证器4均通过射频通信模块61与网络6连接，没有固定的网络地址，但它们都可以与服务器1直接进行通信，因此住户客户机2、访客客户机3与验证器4之间的通信可以通过服务器1中转来实现。例如，住户客户机2欲向验证器4发送一消息，则该住户客户机2可以首先把该消息发送到服务器1，再由服务器1向相关验证器4转发，反之亦然。
图6示出了服务器1、住户客户机2、访客客户机3和验证器4之间网络连接的另一种实施例。在该实施例中，服务器1的网卡13通过网线14与路由器15连接，再通过路由器15连接到网络6中。住户客户机2和访客客户机3为手机，内置有射频通信模块61，可以直接连接到网络6中；访客客户机3还内置有无线通信模块62，如蓝牙或WIFI模块。验证器4包括验证处理器41及用于发出放行指示信号的输出装置42。验证器4内也安装了无线通信模块62。住户客户机2和访客客户机3可以通过浏览器或安装的APP应用程序访问服务器1。访客客户机3与验证器4均有无线通信模块62，相互之间可以直接进行通信。验证器4因无法直接连接到网络6中，因此验证器4与服务器1之间的通信可以通过访客客户机3中转来实现。例如，服务器1欲向验证器4发送一消息，则服务器1可以首先把该消息发送到访客客户机3，再由访客客户机3向该验证器4转发，反之亦然。图3示出的实施例中，验证器4没有射频通信模块61，可以节约通信费用。
服务器1或验证器4存储有住户7的住户信息。如果住户信息存储在验证器4上，通常只在该验证器4上存储对应机构5的住户7的住户信息。如果住户信息存储在服务器1上，则该服务器1可以存储所有住户7的住户信息。住户信息也可以存储在云端，例如云存储服务商提供的云存储空间，云端与网络6连接，服务器1或验证器4通过网络6存取云端上存储的住户信 息。如果住户信息存储在云端，可将云端视为服务器1或验证器4的外接存储器。
住户信息包括住户身份信息和访问验证码。
住户身份信息可以是用户名和登录密码，也可以是对应住户的指纹信息等。住户信息还可以包括住户姓名、房号、联系方式等信息。
访问验证码通常由住户7设置，可以用来阻止陌生人的访问请求。访客8如果欲访问住户7，必须首先输入对应的访问验证码，***判断正确后才能发送访问请求。通过自主设置访问验证码，可以很好地保护住户7不受陌生人的打扰。如果住户7没有设置访问验证码，或对应的访问验证码为空，则访客8无需输入访问验证码，相当于住户7对访客8的访问请求没有限制。
住户信息还包括住户显示信息。住户显示信息用来方便访客8通过访客客户机3筛选欲访问的住户7。
住户显示信息是住户代号或分组信息。
住户显示信息是住户代号时，住户代号为住户7对外显示的访问名称，与网络聊天应用中的网名类似，无需包含住户7的真实信息。使用住户代号而不是真实信息可以保护住户7的隐私。如果需要，住户7还可以随时改变自己的住户代号，以更好地保护个人隐私。表1所示的例子，就属于使用住户代号作为住户显示信息的情况。
住户显示信息是分组信息时，分组信息可以是房号、公司名称、部门名称等信息，和住户信息存在对应关系。分组信息用于对住户信息进行分类，便于访客8进行查询和操作。分组信息还能在访问验证码重复时起到筛选作用，如表2所示的例子。如果只有1个分组信息或者分组信息为空，则访客8无需选择分组信息可以直接输入访问验证码，如表3a和表3b所示的例子。
当服务器1或验证器4存储有住户信息时，均可作为服务端。
访客客户机3包括用于发送通行请求的请求模块。
访客8通过访客客户机3中的请求模块与服务端连接。当住户显示信息 是住户代号时，访客8通过请求模块选择住户代号并输入对应的访问验证码，之后向服务端发送通行请求。当住户显示信息是分组信息时，访客8通过请求模块选择分组信息并输入访问验证码，之后向服务端发送通行请求。如果住户信息同时包括住户代号和分组信息，则可以通过访客8的实际选择为准来确定。以表4为例，如果访客8选择了住户代号“李先生”，则对应的访问验证码为“a1b2c3”，相当于住户显示信息是住户代号；如果访客8选择了“C公司研发部”，则对应的访问验证码为“abcdef”或“a1b2c3”，相当于住户显示信息是分组信息。
请求模块可以是服务端发送的页面，也可以是安装于访客客户机3的应用软件。
服务端包括用于判断访问验证码是否正确的核对模块。即核对模块位于存储有住户信息的服务器1或验证器4中。
服务端接收到访客客户机3中的请求模块发送的通行请求后，通过核对模块判断访问验证码是否正确。当住户显示信息是住户代号时，核对模块接收请求模块发送的住户代号和访问验证码，并与住户信息中对应的住户代号记录进行比较，判断访客输入的访问验证码是否与对应记录存储的访问验证码相同；如果相同，则访问验证码正确。当住户显示信息是分组信息时，核对模块接收请求模块发送的分组信息和访问验证码，并判断该分组信息中是否有与该访问验证码对应的住户信息；如果有，则访问验证码正确。
住户客户机2包括用于接收通行请求的接收模块。
如果核对模块判断访问验证码正确，则对应住户客户机2的接收模块接收核对模块转发的通行请求。对应住户客户机2是指与核对模块所确定的住户信息记录对应的住户7的住户客户机2。接收模块获得通行请求前需与服务端连接并通过住户身份信息认证，住户身份信息认证可通过如表1所示的用户名和密码的形式实现，也可以通过住户指纹等形式实现。通行请求可以包括相关的访问信息，如访客姓名、电话、单位、事由、欲通行的大门等信 息，这些信息由访客8通过访客客户机3的请求模块事先录入。
服务器1或验证器4或住户客户机2包括用于生成放行授权信息的授权模块。住户7通过接收模块收到通行请求后，通过授权模块生成放行授权信息。放行授权信息可以是允许通行或不允许通行的指示，也可以是允许通行的时间段信息或允许通行的次数信息，还可以包含允许通行的大门等信息。
验证器4用于根据放行授权信息判断访客8是否有通行的权利，如是则发出放行指示信号。验证器4可以是专用设备，也可以是通用设备，如手机、平板电脑等，通常位于访客8欲通行的大门9处。
验证器4获得放行授权信息的方式可以有多种。例如，当放行授权信息由住户客户机2生成时，验证器4可以直接与住户客户机2连接获得放行授权信息；住户客户机2也可以先将放行授权信息发送到服务器1，再由验证器4从服务器1获得；住户客户机2也可以先将放行授权信息发送到访客客户机3，再由验证器4从访客客户机3获得；住户客户机2还可以先将放行授权信息发送到服务器1，再由访客客户机3从服务器1获得，最后由验证器4从访客客户机3获得。再如，当放行授权信息由服务器1生成时，验证器4可以直接与服务器1连接获得放行授权信息；也可以由访客客户机3先从服务器1获得，再由验证器4从访客客户机3获得。
图7示出了验证器4的一种实施例。
在该实施例中，验证器4包括验证处理器41及用于发出放行指示信号的输出装置42。验证处理器41运行有用于判断访客是否有通行权利的软件模块。输出装置42包括显示屏422，通过该显示屏422可以发出放行提示。例如，可以在显示屏上显示访客及住户的相关信息及事由信息，物业管理人员在收到放行提示后，允许访客进入。在该实施例中，放行指示信号相当于显示屏422发出的放行提示。在该实施例中，验证器4也可用平板电脑、手机、电脑一体机等通用设备实现。
图8示出了验证器4的另一种实施例。
在该实施例中，大门9通常已安装了电子锁512，该电子锁512受门禁51的控制，门禁51的输出信号可以控制电子锁512的开启及闭合，从而实现对大门9的控制。在该实施例中，验证器4包括验证处理器41及用于发出放行指示信号的输出装置42。验证处理器41运行有用于判断访客是否有通行权利的软件模块。输出装置42为一种控制信号电路，该控制信号电路可以产生开门控制信号421，将该开门控制信号421输入到门禁51的开锁信号端511，使电子锁512受控开启。在该实施例中，放行指示信号相当于开门控制信号421。
在小型应用中，也可以将服务器1和验证器4集成在一起来实现，以降低整个应用的实施成本。图9示出了一种将服务器1和验证器4集成在一起的方案，包括服务端11、住户客户机2和访客客户机3。服务端11的网卡13通过网线14与路由器15连接，再通过路由器15连接到网络6中。住户客户机2和访客客户机3通过射频通信模块61与网络6连接。服务端11包括服务处理器111和输出装置42，用于同时实现图4中服务器1和验证器4的功能，即将服务器1和验证器4中相关的软件模块和存储的数据在服务端11中同时实现。服务处理器111可以采用嵌入式处理器实现，能运行软件模块，又自带存储器。
政府部门、企事业单位、写字楼和小区都可能存在有多个大门9的情况，每个大门9都可能有对应的验证器4，不应将放行授权信息发送到所有的验证器4。服务器1还可存储有大门的大门信息，大门信息与验证器4存在对应关系。请求模块中可包括大门信息选择单元；授权模块生成放行授权信息后，只有与所选大门信息对应的验证器4可获得该放行授权信息。
政府部门、企事业单位、写字楼和小区都可能存在有多个大门9的情况，并且各大门9的通行权限可能不同。服务器1还可存储有大门的大门信息，大门信息与住户信息存在对应关系；与大门信息有对应关系的住户7，才有权允许访客8从对应大门9通行。
例如，表5a和表5b分别示意了住户信息和大门信息，表5c示意了大门信息与住户信息对应关系。从表5c可以看出，只有用户名为“002”的住户7才有权允许访客8从“B”大门9通行。
表5a 住户信息
用户名 密码
001 123
002 234
003 345
表5b 大门信息
大门名
A
B
表5c 大门信息与住户信息对应关系
用户名 大门
001 A
002 A
002 B
003 A
政府部门、企事业单位、写字楼和小区都可能存在有多个大门9的情况，并且各大门9的通行权限可能不同。服务器1还可存储有大门的大门信息和角色信息；住户信息与角色信息存在对应关系；大门信息与角色信息存在对应关系；与大门信息有对应关系的角色信息对应的住户7，才有权允许访客8从对应大门9通行。
例如，表6a、表6b和表6c分别示意了住户信息、大门信息和角色信息，表6d示意了住户信息与角色信息的对应关系，表6e示意了大门信息与角色 信息的对应关系。
从表6d可以看出，用户名为“001”的住户7的角色信息为“管理层”，用户名为“003”的住户7的角色信息为“研发部”，用户名为“002”的住户7的角色信息为“管理层”和“研发部”。从表6e可以看出，角色信息为“管理层”对应的住户7可以允许访客8从“A”、“B”大门9通行，角色信息为“研发部”对应的住户7只能允许访客8从“A”大门9通行。不难看出，用户名为“003”的住户7无权允许访客8从“B”大门9通行。
表6a 住户信息
用户名 密码
001 123
002 234
003 345
表6b 大门信息
大门名
A
B
表6c 角色信息
角色名
管理层
研发部
表6d 住户信息与角色信息的对应关系
用户名 角色名
001 管理层
002 管理层
002 研发部
003 研发部
表6e 大门信息与角色信息的对应关系
大门名 角色名
A 管理层
B 管理层
A 研发部
验证器4还包括摄录装置以及通过摄录装置获取访客特征信息的特征获取模块。住户客户机2接收特征获取模块获取的访客特征信息。
摄录装置可以用于获得访客8的图像、声音等特征信息，将该访客8的特征信息传送给对应住户客户机2，可便于对访客8进行身份识别。
住户信息还可包括可访问时间段，当前时间在可访问时间段内时，访客8才能向对应住户7发送通行请求。
住户信息还可包括勿扰开关，勿扰开关打开时禁止访客8向对应住户7发送通行请求。
服务器1还可存储有访客信息；住户信息还可包括白名单和/或黑名单；白名单和/或黑名单与访客信息对应。与白名单对应的访客8在访问对应住户7时，服务端直接生成允许通行的放行授权信息。与黑名单对应的访客在访问对应住户时，服务端直接生成禁止通行的放行授权信息。

Claims (10)

  1. 访客认证方法，其特征在于，包括：
    1】身份认证，采用如下方式之一：
    1.1】方式1：
    1.1.1】访客通过访客客户机与服务端连接，选择住户代号并输入对应的访问验证码，请求通行；所述服务端存储有住户的住户信息；所述住户信息包括住户代号和访问验证码；
    1.1.2】所述服务端判断该访问验证码是否正确；如是，执行步骤1.1.3】；
    1.1.3】对应住户的住户客户机获得该请求；
    1.2】方式2：
    1.2.1】访客通过访客客户机与服务端连接，选择分组信息并输入访问验证码，请求通行；所述服务端存储有分组信息以及对应住户的住户信息；所述住户信息包括访问验证码；
    1.2.2】服务端判断该分组信息中是否有与该访问验证码对应的住户信息；如是，执行步骤1.2.3】；
    1.2.3】对应住户的住户客户机获得该请求；
    2】通行授权
    2.1】对应住户通过所述住户客户机或所述服务端生成放行授权信息；
    2.2】验证端获得该放行授权信息，判断是否有通行的权利；如是，发出放行指示信号。
  2. 根据权利要求1所述访客认证方法，其特征在于，
    所述服务端存储有大门的大门信息；所述大门信息与所述验证端存在对应关系；
    所述访客通过访客客户机与服务端连接请求通行时，需选择所述大门信息；生成所述放行授权信息后，与所选大门信息对应的验证端获得该放行授权信息。
  3. 根据权利要求1所述访客认证方法，其特征在于，
    所述服务端存储有大门的大门信息；所述住户允许访客从大门通行需拥有审批权限；所述住户按照如下方式之一获得所述审批权限：
    个人方式：
    建立所述大门信息与所述住户信息的对应关系；与大门信息有对应关系的住户，才有权允许访客从对应大门通行；
    角色方式：
    在所述服务端建立角色信息；建立所述角色信息与所述住户信息的对应关系；建立所述大门信息与所述角色信息的对应关系；与大门信息有对应关系的角色信息对应的住户，才有权允许访客从对应大门通行。
  4. 根据权利要求1所述访客认证方法，其特征在于，
    所述住户信息包括可访问时间段和/或勿扰开关；
    当前时间在所述可访问时间段内时，访客才能向对应住户发送通行请求；
    所述勿扰开关打开时禁止访客向对应住户发送通行请求。
  5. 根据权利要求1所述访客认证方法，其特征在于，
    所述服务端存储有所述访客的访客信息；
    所述住户信息包括白名单和/或黑名单；所述白名单和/或黑名单与所述访客信息对应；
    与所述白名单对应的访客在访问对应住户时，所述服务端直接生成允许通行的放行授权信息；
    与所述黑名单对应的访客在访问对应住户时，所述服务端直接生成禁止通行的放行授权信息。
  6. 访客认证***，包括服务器、住户客户机、访客客户机和验证器，所述服务器、住户客户机、访客客户机和验证器通过网络连接，其特征在于：
    所述服务器或验证器存储有住户的住户信息；所述住户信息包括住户身份信息和访问验证码；所述住户信息还包括住户显示信息；所述住户显示信息是住户代号或分组信息；所述分组信息和所述住户信息存在对应关系；
    所述访客客户机包括用于发送通行请求的请求模块；
    所述服务器或验证器包括用于判断访问验证码是否正确的核对模块；
    所述住户客户机包括用于接收通行请求的接收模块；
    所述服务器或验证器或住户客户机包括用于生成放行授权信息的授权模块；
    所述验证器用于判断是否有通行的权利，如是则发出放行指示信号。
  7. 根据权利要求6所述访客认证***，其特征在于，
    所述服务器存储有大门的大门信息；所述大门信息与所述验证器存在对应关系；
    所述请求模块中包括大门信息选择单元；
    所述授权模块生成放行授权信息后，与所选大门信息对应的验证器获得该放行授权信息。
  8. 根据权利要求6所述访客认证***，其特征在于，
    所述服务器存储有大门的大门信息；
    所述大门信息与所述住户信息存在对应关系；与大门信息有对应关系的住户，才有权允许访客从对应大门通行。
  9. 根据权利要求6所述访客认证***，其特征在于，
    所述服务器存储有大门的大门信息和角色信息；所述住户信息与所述角色信息存在对应关系；所述大门信息与所述角色信息存在对应关系；
    与大门信息有对应关系的角色信息对应的住户，才有权允许访客从对应大门通行。
  10. 根据权利要求6所述访客认证***，其特征在于，
    所述验证器还包括摄录装置以及通过摄录装置获取访客特征信息的特征获取模块；所述住户客户机接收特征获取模块获取的访客特征信息。
PCT/CN2017/073547 2016-02-19 2017-02-15 访客认证方法和*** WO2017140240A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610094367.3 2016-02-19
CN201610094367.3A CN107103662A (zh) 2016-02-19 2016-02-19 访客认证方法和***

Publications (1)

Publication Number Publication Date
WO2017140240A1 true WO2017140240A1 (zh) 2017-08-24

Family

ID=59624672

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/073547 WO2017140240A1 (zh) 2016-02-19 2017-02-15 访客认证方法和***

Country Status (2)

Country Link
CN (1) CN107103662A (zh)
WO (1) WO2017140240A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107665530A (zh) * 2017-09-26 2018-02-06 四川仪岛科技有限公司 一种人脸识别单元门禁***及控制方法
CN107833332A (zh) * 2017-11-28 2018-03-23 江苏瑞孚特物联网科技有限公司 基于物联网的医院病区访客管理***及方法
CN111080853A (zh) * 2019-12-20 2020-04-28 珠海格力电器股份有限公司 一种智能门锁***、开锁方法、装置、设备及介质
CN113223224A (zh) * 2021-05-12 2021-08-06 支付宝(杭州)信息技术有限公司 通行处理方法及装置
CN113593100A (zh) * 2021-07-27 2021-11-02 重庆联创建筑规划设计有限公司 一种智慧小区出入管控***及装置
US20220262184A1 (en) * 2019-07-31 2022-08-18 Dominus Systems, Limited Property management systems
CN115862206A (zh) * 2022-06-09 2023-03-28 上海交慧通达智能科技有限公司 一种基于中间数据层的智慧园区无感通行管理方法及***
US12020525B2 (en) * 2019-07-31 2024-06-25 Dominus Systems, Limited Property management systems

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108806026B (zh) * 2017-05-03 2022-01-28 腾讯科技（深圳）有限公司 访客自助实现到访鉴权的方法和***
CN107578506A (zh) * 2017-09-06 2018-01-12 深圳市盛路物联通讯技术有限公司 物联网终端的控制方法及装置
CN107786538B (zh) * 2017-09-18 2019-03-05 深圳市微开互联科技有限公司 门禁授权控制方法、装置及计算机可读存储介质
CN109859348A (zh) * 2017-11-30 2019-06-07 长城汽车股份有限公司 一种远程门禁的授权方法、装置及***
CN108174142A (zh) * 2017-12-21 2018-06-15 广东汇泰龙科技有限公司 一种基于智能门铃和智能云锁的远程控锁方法、***
CN108510630A (zh) * 2018-04-02 2018-09-07 深圳春沐源控股有限公司 物业管理方法
CN109215188A (zh) * 2018-08-10 2019-01-15 遵义仁科信息技术有限公司 智能访客门禁***
CN109727349A (zh) * 2018-12-11 2019-05-07 深圳中正信息科技有限公司 访客派梯方法、装置、计算机设备和存储介质
CN110033541A (zh) * 2019-04-09 2019-07-19 上海上实龙创智慧能源科技股份有限公司 一种基于云服务及智能终端的访客管理方法
CN110298943A (zh) * 2019-06-12 2019-10-01 恒大智慧科技有限公司 一种访客管理***及管理方法
CN111179484B (zh) * 2019-10-30 2021-11-16 腾讯科技（深圳）有限公司 访客管理方法、装置、***及存储介质
US20230047608A1 (en) * 2019-12-20 2023-02-16 Inventio Ag Method for conveying personalised information to a user of a building
CN112184972B (zh) * 2020-09-09 2022-06-14 支付宝(杭州)信息技术有限公司 业务通行处理方法及装置
CN112037407A (zh) * 2020-09-10 2020-12-04 上海掌腾信息科技有限公司 用于防疫的掌静脉识别门禁***及其控制方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101364734A (zh) * 2008-08-01 2009-02-11 上海同盛工程建设配套管理有限公司 一种用于电力***的安全防卫***
CN102663846A (zh) * 2012-05-11 2012-09-12 尤敦朋 基于安卓操作平台的智能访客管理***及其控制方法
CN105261100A (zh) * 2015-11-05 2016-01-20 广东安居宝数码科技股份有限公司 门禁开锁方法及***

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100423578C (zh) * 2004-12-21 2008-10-01 丰誉电信事业股份有限公司 门禁对讲***
CN101080030A (zh) * 2007-06-21 2007-11-28 北京互信互通信息技术有限公司 一种门禁对讲方法和***
CN201167383Y (zh) * 2008-02-05 2008-12-17 珠海市太川电子企业有限公司 一种可视对讲***门口机
CN201413537Y (zh) * 2009-04-24 2010-02-24 北京博雅英杰科技有限公司 重点单位来访人员管理***
CN103888854A (zh) * 2012-12-24 2014-06-25 深圳市中联创新自控***有限公司 访客对讲***
US9235943B2 (en) * 2013-07-26 2016-01-12 Joseph Frank Scalisi Remote identity verification of lodging guests
CN103679882A (zh) * 2013-11-29 2014-03-26 朱佩芬 住宅区电子门禁***
CN103679903B (zh) * 2014-01-02 2015-10-28 苏州众天力信息科技有限公司 一种基于微信的门禁控制方法
KR20150000442A (ko) * 2014-07-28 2015-01-02 주식회사 브랜덤 식별 수단을 이용한 안전 출입 시스템 및 그 동작방법
CN104484929A (zh) * 2014-12-22 2015-04-01 唐玉勇 一种新型社区安全应用***及实施方法
CN104767960B (zh) * 2015-03-12 2018-06-12 伟创达电子科技（深圳）有限公司 微信楼宇可视对讲***及其通信方法
CN204791237U (zh) * 2015-07-15 2015-11-18 重庆慧居智能电子有限公司 一种无线智能门禁对讲***

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101364734A (zh) * 2008-08-01 2009-02-11 上海同盛工程建设配套管理有限公司 一种用于电力***的安全防卫***
CN102663846A (zh) * 2012-05-11 2012-09-12 尤敦朋 基于安卓操作平台的智能访客管理***及其控制方法
CN105261100A (zh) * 2015-11-05 2016-01-20 广东安居宝数码科技股份有限公司 门禁开锁方法及***

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107665530A (zh) * 2017-09-26 2018-02-06 四川仪岛科技有限公司 一种人脸识别单元门禁***及控制方法
CN107833332A (zh) * 2017-11-28 2018-03-23 江苏瑞孚特物联网科技有限公司 基于物联网的医院病区访客管理***及方法
US20220262184A1 (en) * 2019-07-31 2022-08-18 Dominus Systems, Limited Property management systems
US12020525B2 (en) * 2019-07-31 2024-06-25 Dominus Systems, Limited Property management systems
CN111080853A (zh) * 2019-12-20 2020-04-28 珠海格力电器股份有限公司 一种智能门锁***、开锁方法、装置、设备及介质
CN113223224A (zh) * 2021-05-12 2021-08-06 支付宝(杭州)信息技术有限公司 通行处理方法及装置
CN113223224B (zh) * 2021-05-12 2023-10-24 支付宝(杭州)信息技术有限公司 通行处理方法及装置
CN113593100A (zh) * 2021-07-27 2021-11-02 重庆联创建筑规划设计有限公司 一种智慧小区出入管控***及装置
CN115862206A (zh) * 2022-06-09 2023-03-28 上海交慧通达智能科技有限公司 一种基于中间数据层的智慧园区无感通行管理方法及***
CN115862206B (zh) * 2022-06-09 2024-04-26 上海交慧通达智能科技有限公司 一种基于中间数据层的智慧园区无感通行管理方法及***

Also Published As

Publication number Publication date
CN107103662A (zh) 2017-08-29

Similar Documents

Publication Publication Date Title
WO2017140240A1 (zh) 访客认证方法和***
US10367817B2 (en) Systems and methods for challengeless coauthentication
Hulsebosch et al. Context sensitive access control
US8881252B2 (en) System and method for physical access control
CN113272805B (zh) 公用计算设备的基于邻近度的解锁
KR101920654B1 (ko) Ｎｆｃ 기반 출입 관리 시스템 및 그 방법
WO2016169424A1 (zh) 社区联网门禁***及基于该***的社区进入方法
CN112840339B (zh) 对数据和设备功能性的渐进访问
US10679446B2 (en) Extended instant guest access using near field communication tags
US9306943B1 (en) Access point—authentication server combination
KR101118679B1 (ko) Ｎｆｃ 기반의 출입 통제 방법
CN105741395A (zh) 基于二维码和人脸识别的门禁访问方法和***
KR101852599B1 (ko) 모바일 장치를 이용한 출입통제 시스템 및 방법
JP2017210862A (ja) 位置設定可能な電子ロック制御方法、プログラム及びシステム
MX2013011116A (es) Distribucion de informacion de acceso a instalaciones.
US20170169635A1 (en) Method and system for visitor access control management
KR20150122637A (ko) 모바일 디바이스 관리 및 보안 분야에서 근거리 무선 통신의 활용 및 응용
US20100268778A1 (en) Apparatus and method for sharing identity in ubiquitous environment
KR101855494B1 (ko) 모바일 장치를 이용한 도어 시스템 및 방법
US20220255929A1 (en) Systems and methods for preventing unauthorized network access
US20210243188A1 (en) Methods and apparatus for authenticating devices
CN108876987A (zh) 楼宇门禁控制方法、云服务器及计算机可读存储介质
US20170257364A1 (en) Systems and methods for authentication using authentication votes
CN112286632A (zh) 云平台、云平台管理方法、装置、电子设备及储存介质
En-Nasry et al. Towards an open framework for mobile digital identity management through strong authentication methods

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17752672

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17752672

Country of ref document: EP

Kind code of ref document: A1