Visitor management method, visitor management system and access control equipment
By collecting and matching visitor information with historical access needs, and combining it with shared data from other users, the system enables fast and accurate permission settings and information sharing. This solves the problems of resource waste and security risks in existing visitor management systems, and improves the efficiency and security of visitor management.
Patent Information
- Application Number
- CN202411116820.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-14
- Publication Date
- 2026-03-03
AI Technical Summary
In existing visitor management systems, the frequent entry and exit of public service personnel into the community leads to resource waste and inefficiency, and the lack of timely information updates may cause security risks. Furthermore, the development cost of integrating with third-party systems is high and maintenance is difficult.
By collecting visitor information and confirming it against historical visitor information that matches historical access needs, access permissions can be set. By referring to historical visitor information and reviews shared by other users, permissions can be issued quickly and accurately, and information sharing and permission reset can be supported.
It improved the accuracy and convenience of visitor information verification, ensured community safety, reduced repetitive work, lowered system maintenance costs, and enhanced the real-time nature and accuracy of information.
Smart Images
Figure CN121600624A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of digital management technology, specifically to a visitor management method, a visitor management system, and an access control device. Background Technology
[0002] In existing technologies, for community security reasons, visitors typically need to verify their information before entering and exiting the community. Specifically, visitor information is usually verified by a system or manually before granting appropriate access permissions. Since public service personnel (such as delivery personnel and domestic service workers) frequently enter and exit the community, requiring visitor registration, verification, and permission granting each time not only wastes resources but also reduces the efficiency of visitor management due to repetitive work. Furthermore, if the information of public service personnel changes, failure to update it promptly may lead to erroneous access and potential security risks.
[0003] In addition, although there is a way to grant access control permissions by obtaining service personnel information through integration with third-party service systems, this method requires integration with multiple different third-party service systems, resulting in high integration and development costs, and the system also requires continuous maintenance in the later stages.
[0004] Therefore, it is necessary to improve the existing visitor management methods and visitor management systems. Summary of the Invention
[0005] To address the above problems, this invention provides a visitor management method, comprising: an information confirmation step, which collects visitor information based on access needs and confirms visitor information according to historical visitor information in historical access needs that match the access needs; and an access permission setting step, which sets access permissions based on the result of the information confirmation step, wherein the visitor information includes visitor identity information, the historical visitor information includes historical visitor identity information, and the historical access needs and their associated historical visitor information include information shared by other users.
[0006] The visitor management method provided in this application, in the visitor information confirmation stage, can use the matching of historical access requests and historical visitor identity information with current access requests and current visitor identity information as a reference to confirm visitor identity information and access requests. This allows for faster confirmation of visitor information and a faster determination of whether to grant permissions. Compared with the existing technology where information needs to be reconfirmed and permissions granted when a visitor visits repeatedly, this method achieves visitor registration and permission granting more conveniently and efficiently while ensuring information accuracy.
[0007] Furthermore, in this embodiment, when referencing historical visitor information, information shared by other users is referenced. These other users can be residents within the community / neighborhood. Since residents are the primary counterparts of visitors, they generate a large amount of valuable data during their interactions with visitors. The historical visitor information generated by referencing information shared by users can improve the comprehensiveness, real-time nature, and accuracy of the historical visitor information. Moreover, when managing visitors based on historical visitor information, visitor information confirmation will be more accurate and convenient.
[0008] Optionally, the permission setting step further includes: referring to historical access permission information associated with the historical access request and the historical visitor information, and / or referring to historical user rating information associated with the historical access request and the historical visitor information.
[0009] Based on historical access permission information associated with historical visitor information and historical access requests, we can know the access permissions that the visitor has obtained in the historical accesses associated with the current access request. Based on the historical access permission information, we can refer to whether to grant the current permission and set the scope of the permission, which can make the granting of permissions more convenient and secure.
[0010] Once a visitor has been granted access permissions associated with this access request, permissions can be quickly granted by referring to historical access permission information after the visitor information has been confirmed.
[0011] Optionally, the visitor management method provided in this application further includes a user evaluation step: after the visitor terminates their visit, the visitor evaluates the visitor's activity to form user evaluation information.
[0012] Because service quality can vary even among the same type of service providers—for example, in room cleaning services, differences in efficiency and quality among cleaning staff can lead to varying levels of user satisfaction—and because residents may have personal preferences in certain application scenarios, and service needs within the same community tend to be similar, resident evaluations of visitors (service providers) are highly valuable. In the visitor information verification process, residents or property management personnel can not only verify the visitor's identity and qualifications based on objective identity information and access records, but also, if the visitor has historical access records, use resident evaluations of their past services to assess the visitor's service capabilities / quality, providing a reference for residents to decide whether to accept the service or set corresponding permissions.
[0013] Optionally, the visitor management method further includes: an information sharing step: sharing visitor information and / or access requests, as well as access permissions and / or user rating information, with other users.
[0014] This setup not only allows for visitor management based on information shared by other users, but also enables the sharing of information obtained / generated during the current visit with other users. The information mentioned here mainly includes: visitor information, access requests, access permissions, and user rating information. Based on this, the information generated by visitor visits can be effectively utilized.
[0015] Specifically, to ensure the validity of information, the information shared usually includes at least visitor information or access requests, as well as access permissions or user review information. In this way, a valid and complete set of information can be formed. For example, a visitor's visitor information combined with the access permissions they have obtained, or the access permissions they have obtained based on a certain access request, or a visitor's visitor information and the user review information they have obtained, etc.
[0016] Optionally, the information sharing step further includes: setting the sharing scope of information shared with other users. In this application, users can set the sharing scope of information (visitor information, access requests, access permissions, and user evaluation information) shared with other users. In this way, on the one hand, it is not limited to sharing the above information only within the same community / street. It can be shared with other communities / streets that are equipped with the same visitor management system or apply the same visitor management method. These communities / streets can belong to the same area / street / property management company. This is because visitors from the same area / street / property management company may overlap. Sharing visitor information, access requests, access permissions, and / or user evaluation information can make full use of the obtained data, realize data sharing and reference on a larger scale, and further improve the accuracy, security, and convenience of visitor management.
[0017] On the other hand, when a user's evaluation is negative and primarily aimed at the service personnel and their company, it is possible that the user may be unwilling to share such information in order to protect their personal privacy. Therefore, setting the scope of sharing such information to be configurable / selectable can improve the user experience and protect user privacy.
[0018] Specifically, the logic for setting the sharing scope of the above information can be based on a hierarchical structure. For example, the hierarchical structure can be: the same household; the same unit; the same building; the same community; the same street area; the same platform, etc. Users can set different sharing scopes based on the specific needs of the scenario or requirements. The scope hierarchy can be preset or defined by the user. For example, the user can limit the sharing scope to one or several other users in the same unit.
[0019] Optionally, the visitor information may also include service qualification information, and the historical visitor information may also include historical service qualification information; the information confirmation step may further include: collecting service qualification information, and matching the visitor information that meets the access requirements with the historical service qualification information and the service qualification information.
[0020] Since service personnel entering residential communities may require corresponding service qualifications to perform their duties, the information verification process can be conducted by matching historical service qualification information with the collected service qualification information. This approach can more conveniently and accurately verify the visitor's service qualifications, ensuring service quality and protecting the safety of users and the community.
[0021] Considering that visitors or service personnel may change in their company, position, qualifications, and capabilities, the historical service qualification information mentioned above refers to the latest historical service qualification information. The latest historical service qualification information is the service qualification information of the relevant visitor most recently obtained through preset information channels. This service qualification information can be obtained through periodic retrieval, or through the visitor management system in real time, for example, updated weekly. It can also be obtained in real time through manual retrieval, or a combination of periodic retrieval and manual retrieval. It should be noted that the latest historical service qualification information obtained from the same visitor is updated based on the same data information or information obtained at the same point in time. This ensures the completeness and accuracy of the information.
[0022] In this application, the historical service qualification information for reference can also be a list of historical service qualification information displayed in chronological order. Users can select the service qualification information of a user within a certain time period as a reference according to their needs, so as to make a more comprehensive and accurate judgment on the service qualification of visitors.
[0023] Optionally, the visitor permissions can be reset.
[0024] Since unexpected events may occur during the service provision process, such as early service termination, service delay, or sudden service cancellation, this implementation provides a permission reset function for users from the perspective of flexible management and ensuring user safety. During regular service, permissions can be shortened or extended based on service progress, or the predetermined permissions can be canceled. In the event of an emergency, visitor permissions can be terminated at any time to ensure user safety.
[0025] Additionally, if a visitor has not visited for an extended period or has received a low user rating, their access privileges can be revoked or restricted after the preset conditions are met by setting corresponding time limits or rating thresholds.
[0026] In order to achieve the above-mentioned objectives, this application provides a visitor management system for managing visitors within a community, using the visitor management method described above.
[0027] To achieve the above-mentioned objectives, this application provides an access control management device that integrates the visitor management system described above.
[0028] In summary, the visitor management method and device provided in this application can confirm visitor information and grant access permissions based on the reference to the visitor's historical access information. This makes visitor management more convenient, information confirmation more accurate, and community security more guaranteed. In addition, the information referenced in the visitor management of this application can also come from user sharing, so the real-time and accuracy of the information are stronger, further ensuring information security. Attached Figure Description
[0029] Figure 1 This is a schematic diagram of the steps of the visitor management method provided by the embodiments of the present invention;
[0030] Figure 2 This is a schematic diagram illustrating the steps of another visitor management method provided by an embodiment of the present invention;
[0031] Figure 3 This is a schematic diagram illustrating the steps of another visitor management method provided by an embodiment of the present invention;
[0032] Figure 4 This is a schematic diagram illustrating the steps of another visitor management method provided by an embodiment of the present invention;
[0033] Figure 5 This is a schematic diagram illustrating the steps of another visitor management method provided by an embodiment of the present invention;
[0034] Figure 6 This is a schematic diagram of the visitor management system provided in an embodiment of the present invention. Detailed Implementation
[0035] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of the present invention.
[0036] like Figure 1As shown, this embodiment provides a visitor management method, including: an information confirmation step, which collects visitor information based on access needs and confirms visitor information according to historical visitor information in historical access needs that match the access needs; and a permission setting step, which sets access permissions based on the result of the information confirmation step, wherein visitor information includes visitor identity information, historical visitor information includes historical visitor identity information, and historical access needs and their associated historical visitor information include information shared by other users.
[0037] Generally, the primary matching criteria are access requests and historical access requests. Once access requests and historical access requests match, further matching is performed on visitor information and historical visitor information.
[0038] One possibility is that multiple historical access requests satisfy the matching result. In this case, the most recent historical access request will generally be selected, and further matching of other information or permission settings will be performed. Of course, if the matching degree of other information is not good, further matching from other matched historical access requests will be used as a reference. In addition, if the most recent matched historical access request is provided by other users, and there are also historical access requests that the user has made, then the user's own most recent historical access request may be mainly used as the basis for matching other information and setting permissions, while the historical access requests and related information provided by other users are used as a reference.
[0039] Another possibility is that if no matching requests in the historical access requests are found, the historical visitor information (historical visitor identity information) can be matched first based on the visitor information (visitor identity) and the historical access requests that meet the matching conditions and their related information can be used as a reference for setting permissions.
[0040] The access requirements include the reason for access, such as the need for services like renovation, cleaning, food delivery, and express delivery; the access time period, which can be set in advance according to the purpose of access, or real-time access can be granted after identity verification, such as from 12:00 to 14:00 on a certain day; and the access permission requirements, such as access control for the community gate, access control for the unit doors of specific buildings, and access permissions for other community facilities.
[0041] Visitor information includes visitor identity information, such as the visitor's name, ID number, and other personal information that can clearly identify the visitor; it also includes service qualification information, such as company name, job title, and qualification information that can prove service qualifications / capabilities.
[0042] The historical visitor information refers to the visitor information of historical visitors to the community / residential area recorded / stored / imported by the visitor management system. Since historical visitor information may change, it is preferable to use historical visitor information as a reference and regularly update the historical visitor information data to ensure its accuracy. Furthermore, historical visitor information can be obtained by retrieving it from the stored records of the visitor management system or through the data interface of enterprises / organizations cooperating with the community / residential area. Users or system administrators can also manually update the visitor management system with changes in historical visitor information. This setting can improve the accuracy of information when retrieving historical visitor information, ensure the safety of residents in the community / residential area, and avoid safety hazards caused by unqualified or no longer employed personnel being mistakenly allowed to enter due to untimely information updates.
[0043] Access permissions include the areas or operations that visitors within the community / residential area require permission to enter or perform. Specifically, this includes access control at the community / residential area gate, building unit entrances, garage doors, electrical room doors, and individual home doors, etc.
[0044] The visitor management method provided in this embodiment, in the visitor information confirmation stage, can use the matching of historical access requests and historical visitor identity information with current access requests and current visitor identity information as a reference to confirm visitor identity information and access requests. This allows for faster confirmation of visitor information and a faster determination of whether to grant permissions. Compared with the prior art, which requires reconfirmation of information and granting of permissions when a visitor makes a repeated visit, this method achieves visitor registration and permission granting more conveniently and efficiently while ensuring information accuracy.
[0045] Furthermore, in this embodiment, when referencing historical visitor information, information shared by other users is referenced. These other users can be residents within the community / neighborhood. Since residents are the primary counterparts of visitors, they generate a large amount of valuable data during their interactions with visitors. The historical visitor information generated by referencing information shared by users can improve the comprehensiveness, real-time nature, and accuracy of the historical visitor information. Moreover, when managing visitors based on historical visitor information, visitor information confirmation will be more accurate and convenient.
[0046] The above text details how referencing historical visitor identity information and access requests improves the convenience and accuracy of visitor information verification during the information confirmation process. Applicants realize that referencing historical visitor information can also assist in setting permissions.
[0047] Specifically, such as Figure 2As shown, the permission setting steps also include:
[0048] Refer to historical access permission information associated with historical access requests and their historical visitor information, and / or refer to historical user review information associated with historical access requests and their historical visitor information.
[0049] This setting allows you to base your permissions on historical access permissions and user ratings during the permission settings process.
[0050] Based on historical access permission information associated with historical visitor information and historical access requests, we can know the access permissions that the visitor has obtained in the historical accesses associated with the current access request. Based on the historical access permission information, we can refer to whether to grant the current permission and set the scope of the permission, which can make the granting of permissions more convenient and secure.
[0051] Once a visitor has been granted access permissions associated with this access request, permissions can be quickly granted by referring to historical access permission information after the visitor information has been confirmed.
[0052] Because service providers of the same type may have varying service quality—for example, different cleaning staff may have different efficiency levels and residents may have different levels of satisfaction after cleaning—and because residents may have personal preferences in some application scenarios, and because service needs within the same community tend to be similar, residents' evaluations of visitors (service providers) within the same community are highly valuable. Therefore, in the visitor information confirmation process, residents or property management personnel can not only verify the visitor's identity and qualifications based on the visitor's objective identity information and access records, but also, if the visitor has historical access records, can use residents' historical user evaluations of the visitor, along with the visitor's service capabilities / quality, to provide a reference for residents on whether to accept the service or set corresponding permissions.
[0053] Preferably, such as Figure 3 As shown, the visitor management method provided in this embodiment further includes:
[0054] User review process: After a visitor terminates their visit, they evaluate their visitor activity and generate user review information.
[0055] This user review information can also be shared to the visitor management system as shared information, so that property management and other users can refer to it when selecting relevant services or personnel. It also provides a reference for property management and other users in the permission setting process to determine whether to grant permissions or the scope of permissions granted.
[0056] Since user reviews only represent one side of the story, to ensure their objectivity and reliability, verification of these reviews can be conducted to assess their authenticity and objectivity, thus enhancing their credibility. Specifically, when service personnel have objections to user reviews, they can submit evidence and appeals to have the system adjudicate the review content. If a user is ultimately determined to have provided unfair, malicious, or false reviews, their review privileges will be restricted. For example, the scope of their reviews will be limited, and negative reviews will be subject to stricter review. Furthermore, user reviews deemed inappropriate will be ordered to be corrected, or hidden or deleted through the system.
[0057] Optionally, such as Figure 4 As shown, the visitor management method provided in this embodiment further includes: an information sharing step: sharing visitor information and / or access requests, as well as access permissions and / or user evaluation information, with other users.
[0058] In this embodiment, visitor management can be carried out not only based on information shared by other users, but also based on information obtained / generated during the current visit and shared with other users. The information mentioned here mainly includes: visitor information, access requests, access permissions and user evaluation information.
[0059] Specifically, to ensure the validity of information, the information shared usually includes at least visitor information or access requests, as well as access permissions or user review information. In this way, a valid and complete set of information can be formed. For example, a visitor's visitor information combined with the access permissions they have obtained, or the access permissions they have obtained based on a certain access request, or a visitor's visitor information and the user review information they have obtained, etc.
[0060] Optionally, the information sharing steps may also include: setting the sharing scope of information shared with other users.
[0061] In this implementation, users can set the sharing scope of information (visitor information, access requests, access permissions, and user evaluation information) shared with other users. This means that, on one hand, the information is not limited to sharing only within the local community; it can be shared with other communities that have the same visitor management system or use the same visitor management method. These communities may belong to the same area / street / property management company. This is because visitors from the same area / street / property management company may overlap. Sharing visitor information, access requests, access permissions, and / or user evaluation information can fully utilize the obtained data, enabling data sharing and reference on a larger scale, further improving the accuracy, security, and convenience of visitor management.
[0062] On the other hand, when a user's review is negative and primarily aimed at the service personnel and their company, it is possible that the user may be unwilling to share their review information to protect their personal privacy. Therefore, setting the scope of such information sharing to be configurable / selectable can improve the user experience and protect user privacy.
[0063] Specifically, the logic for setting the sharing scope of the above information can be based on a hierarchical structure. For example, the hierarchical structure can be: the same household; the same unit; the same building; the same community; the same street area; the same platform, etc. Users can set different sharing scopes based on the specific needs of the scenario or requirements. The scope hierarchy can be preset or defined by the user. For example, the user can limit the sharing scope to one or several other users in the same unit.
[0064] Preferably, such as Figure 5 As shown, visitor information also includes service qualification information, and historical visitor information also includes historical service qualification information. The information confirmation step also includes: collecting service qualification information, and matching visitor information with access requirements based on historical service qualification information. Since service personnel entering the community may need corresponding service qualifications to perform their work, the information confirmation step can be based on historical service qualification information and matched with the collected service qualification information to confirm the service qualification information. This can more conveniently and accurately confirm the visitor's service qualifications, ensuring service quality and protecting the safety of users and the community.
[0065] In some implementations, the historical service qualification information for reference can also be a list of historical service qualification information displayed in chronological order. Users can select the service qualification information of a user within a certain time period as a reference according to their needs, so as to make a more comprehensive and accurate judgment on the service qualification of visitors.
[0066] In some implementations, visitor permissions can be reset. This reset can be, at the level of permission scope, including adding, reducing, or canceling permissions; and at the level of permission duration, including extending permissions, shortening durations, and immediately prohibiting permissions.
[0067] Since unexpected events may occur during the service provision process, such as early service termination, service delay, or sudden service cancellation, this implementation provides a permission reset function for users from the perspective of flexible management and ensuring user safety. During regular service, permissions can be shortened or extended based on service progress, or the predetermined permissions can be canceled. In the event of an emergency, visitor permissions can be terminated at any time to ensure user safety.
[0068] Optionally, this embodiment provides a visitor management system for managing visitors within a community, which applies the visitor management method described in this embodiment.
[0069] Optionally, this embodiment provides an access control management device that integrates the visitor management system provided in this embodiment.
[0070] It should be noted that this implementation also provides various visitor management methods, which can be implemented by... Figures 1 to 5 The steps of the visitor management method shown are formed by freely combining user needs, and will not be listed one by one here.
[0071] like Figure 6 As shown, the visitor management method and visitor management system provided in this embodiment will be explained in detail below with specific examples.
[0072] The visitor management method provided in this embodiment mainly manages public service personnel. Different access permissions can be set according to the visitor's identity and service type. For example, the needs of delivery personnel and food delivery personnel are mainly building access control, while the needs of domestic workers and caregivers are mainly building access control and home access control. In some application scenarios, the visitor management also includes the user's relatives and friends. For example, when only domestic workers, caregivers or elderly people are in the user's home, it is also necessary to confirm visitor information and issue access permissions through visitor management.
[0073] In visitor management systems, especially for access control to apartment buildings and individual residences, the rules are typically set by the user.
[0074] If an event occurs without pre-defined rules, a higher security level will be applied by default, meaning access will be denied. For example, a delivery person is only required to enter the community and leave the package in a public area such as a property management office or a smart locker. If delivery to the user's home is required, the delivery person can submit a request beforehand. During the event's initiation and until the user's access control request actually occurs, the user will be reminded via push notification to set the actual permissions or permission rules. Users can also pre-set time-related permission rules, such as granting access to the building's access control between 5:00 PM and 8:00 PM daily, ensuring someone is home and it is convenient. If the delivery person arrives during this time, the package can be delivered directly to the door.
[0075] The event can be initiated based on the relevant services generated on the service platform, and the corresponding information verification steps can be started. For example, the identity information and qualification information of the service personnel from the service platform can be initially matched. When the service personnel arrive at the community access control, they can be further identified and matched through, for example, captured images and sounds.
[0076] For a simpler visitor management system for service personnel, once the community system receives an event from the relevant service platform and successfully matches the visitor information on the service platform with the historical visitor information related to that event, the service personnel gain access to the relevant community access control systems via their mobile devices or related mobile applications (e.g., by entering a specified username and password). Examples include NFC, QR codes, etc. Alternatively, facial recognition, license plate numbers, etc., can be used.
[0077] The visitor management method provided in this embodiment is implemented by community users (residents), who are configured with corresponding permission granting authority on a household basis. The scope of their authority may change based on changes in community service rules or user needs. Changes to the scope of authority can be initiated by users or configured by the community service center / property management center through administrator privileges. The community service center / property management center can also be the implementing entity for the visitor management method. Besides indirectly configuring users' visitor management permissions and managing visitor information, the community service center / property management center can also directly confirm visitor information and grant visitor permissions. For example, when a user is not at home and it is inconvenient to remotely manage visitors, they can entrust property management personnel to manage the relevant visitors. Whether the visitor is a user's relative or a public service worker, the property management personnel are not familiar with them. Therefore, based on the visitor management method provided in this embodiment, referring to relevant visitor history information when confirming visitor information and granting access permissions will greatly improve the efficiency of visitor information confirmation and ensure the security of permission granting.
[0078] The visitor management method provided in this embodiment utilizes equipment including visitor management devices at the service center (also referred to as access control devices when the management content is access control permissions), terminal devices in users' homes that can communicate with the outdoor unit, such as indoor units, central control screens, mobile apps, etc., and outdoor units installed at building unit doors and other necessary locations that communicate with the visitor management devices. Specifically, visitors can provide necessary information through the outdoor unit. For example, they can provide information by calling residents / property management via voice / video, or by logging into an information collection mini-program via QR code, or by using facial recognition for secondary information confirmation after the information has been entered. Users or property management personnel use the visitor management device to compare and confirm visitor information based on the information provided by the visitor and by referring to historical visitor information stored in the device or cloud server. After confirming that the user information is correct, access permissions are granted based on the historical visitor information.
[0079] Preferably, to make visitor management more convenient, visitor management can also be carried out remotely via a mobile terminal with the visitor management system application installed on the mobile device.
[0080] Preferably, visitor access permissions can be granted in real time based on the application. For example, after visitor information is confirmed, the user can remotely open the door for the visitor through the app.
[0081] Preferably, after referring to historical user reviews, users can also set access levels for the same service. For example, for housekeeping services, specific service areas can be set and the service areas can be specifically divided. For example, housekeeping service personnel with high ratings can be granted access to areas where valuable items are stored.
[0082] The technical solution of the present invention has now been described in conjunction with the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to the specific embodiments described above. Without departing from the principles of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions resulting from such changes or substitutions will all fall within the scope of protection of the present invention.
Claims
1. A visitor management method, comprising: The information confirmation step involves collecting visitor information based on access requirements and confirming visitor information based on historical visitor information from historical access requirements that match the access requirements. The permission setting step sets access permissions based on the result of the information confirmation step, wherein the visitor information includes visitor identity information and the historical visitor information includes historical visitor identity information; The characteristic is that the historical access requests and the associated historical visitor information include information shared by other users.
2. The visitor management method according to claim 1, characterized in that, The permission setting steps also include: Referencing the historical access permission information associated with the historical access requests and their historical visitor information, and / or Refer to historical user review information associated with the historical access requests and the historical visitor information.
3. The visitor management method according to claim 1, characterized in that, It also includes a user evaluation step: after the visitor terminates their visit, the visitor evaluates their activity and generates user evaluation information.
4. The visitor management method according to claim 3, characterized in that, Also includes Information sharing steps: Share the visitor information and / or the access request, as well as the access permissions and / or the user rating information, with other users.
5. The visitor management method according to claim 4, characterized in that, The information sharing steps also include: setting the sharing scope of information to be shared with other users.
6. The visitor management method according to any one of claims 1-5, characterized in that, The visitor information also includes service qualification information, and the historical visitor information also includes historical service qualification information; The information confirmation step also includes: Information on the qualifications of the collection service The visitor information is matched with the historical service qualification information to determine the access requirements.
7. The visitor management method according to any one of claims 1-5, characterized in that, The visitor permissions can be reset.
8. A visitor management system, used for managing visitors within a community, characterized in that, The visitor management method according to any one of claims 1-7.
9. An access control management device, characterized in that, The system integrates the visitor management system as described in claim 8.