CN114077992A

CN114077992A - Visitor visiting management method and device and server

Info

Publication number: CN114077992A
Application number: CN202010826004.0A
Authority: CN
Inventors: 魏连杰; 宋楠楠; 黄建超; 贺富强; 郑光杰; 刘雨; 赵少华
Original assignee: Hongfujin Precision Electronic Yantai Co Ltd; Hon Hai Precision Industry Co Ltd
Current assignee: Hongfujin Precision Electronic Yantai Co Ltd; Hon Hai Precision Industry Co Ltd
Priority date: 2020-08-17
Filing date: 2020-08-17
Publication date: 2022-02-22
Also published as: TWI764266B; TW202209268A

Abstract

The invention relates to a visitor visiting management method, a visitor visiting management device and a server. The method comprises the following steps: establishing a master file for the visiting customer according to a pre-stored customer database; receiving an appointment application; auditing the reservation application based on the master file according to a preset method, and generating a reservation success record when the audit is passed; generating a killing instruction based on the reservation success record, killing the vehicle and the articles of the visiting client according to the killing instruction, and recording a killing record; generating access authority information according to the reservation success record and the killing record; and identifying the license plate of the vehicle and the driver of the vehicle according to the access authority information, generating an identification record, and controlling a gateway barrier to pass the identified vehicle and the driver. The present case has improved visitor's visiting managerial efficiency through the authority of automatic audit, discernment and management visitor.

Description

Visitor visiting management method and device and server

Technical Field

The invention relates to the technical field of authority management, in particular to a visitor visiting management method, a visitor visiting management device and a server.

Background

Currently, when a visitor accesses a special area, multiple audits are required, including verification of personnel identity, confirmation of carried articles, and the like. For example, when a manufacturer needs to enter a factory area, the manufacturer often needs to finish the operation by a large amount of manpower, the efficiency is not high enough, and particularly, the workload of auditing visitors in a special period (for example, during a new crown epidemic situation) is large, and the existing visitor visit management method cannot effectively solve various management problems of visitor visits.

Disclosure of Invention

In view of the foregoing, there is a need for a visitor visiting management method, device and server to solve the problem of multiple audits of visitors who cannot effectively manage visiting visitors.

A first aspect of the present application provides a visitor visiting management method, which is applied in a server, and the method includes:

establishing a master file for a visiting client according to a client database prestored in the server;

receiving a reservation application submitted by the visiting client;

auditing the reservation application based on the master file according to a preset method, and generating a reservation success record when the audit is passed;

generating a killing instruction based on the reservation success record, sending the killing instruction to a designated person to kill the vehicle and the articles of the visiting client, and recording the killing record;

generating access authority information according to the reservation success record and the killing record;

and identifying the license plate of the vehicle and the driver of the vehicle according to the access authority information, generating an identification record, and controlling a gateway barrier to pass the identified vehicle and the driver.

Preferably, the establishing a master file for the visiting client according to the client database pre-stored in the server comprises:

and importing company information of the visiting client, staff information related to the visiting client and vehicle information related to the visiting client into the master file from the client database prestored in the server.

Preferably, the receiving the reservation application submitted by the visiting client includes:

receiving a reservation application submitted by the visiting client, and storing the received reservation application in the server, wherein the reservation application comprises vehicle reservation and personnel reservation.

Preferably, the reviewing the reservation application based on the master file according to the preset method, and the generating a reservation success record when the review is passed includes:

judging whether a vehicle reserved by the vehicle and a person reserved by the person are recorded in the master file, and accessing a health epidemic prevention database and acquiring historical movement records and health conditions recorded in the health epidemic prevention database by the person when the vehicle and the person are both recorded in the master file;

when the historical movement record and the health condition both accord with preset conditions, determining that the examination is passed, generating a reservation success record according to the reservation application, or when the historical movement record or the health condition does not accord with the preset conditions, determining that the examination is not passed, outputting reservation failure information and prompting the non-conformity with the preset conditions.

Preferably, the generating of the killing instruction based on the reservation success record, and the sending of the killing instruction to a designated person to kill the vehicle and the article of the visiting customer comprises:

generating the kill instruction when the vehicle of the visiting customer and the driver of the vehicle are consistent with the reservation success record.

Preferably, the record killing record comprises:

recording the killing time, the information of the killed vehicles, the information of drivers of the killed vehicles and the image data of the killing process recorded by the photographing device;

and generating the killing record according to the killing time, the killed vehicle, the driver information and the image data.

Preferably, the generating the access right information according to the reservation success record and the kill record includes:

and when the vehicle information in the killing record is matched with the vehicle information recorded successfully in the reservation, generating the access authority information according to the vehicle information and the driver information.

Preferably, the identifying the license plate of the vehicle and the driver of the vehicle according to the access right information and generating the identification record comprises:

shooting an image of the vehicle by using a shooting device, recognizing the license plate number of the vehicle based on the shot image, and recording recognition time, recognition position and the license plate number;

detecting the certificate of the driver through a detection device, and identifying the identity information of the driver recorded by the certificate;

and generating an identification record according to the recorded identification time, identification position, license plate number and identity information.

A second aspect of the present application provides a visitor visiting management apparatus, applied to a server, the apparatus including:

the establishing module is used for establishing a master file for the visiting client according to a client database pre-stored in the server;

the application module is used for receiving a reservation application submitted by the visiting client;

the auditing module is used for auditing the reservation application based on the main file according to a preset method, and generating a reservation success record when the auditing is passed;

the instruction generating module is used for generating a killing instruction based on the reservation success record, sending the killing instruction to a designated person to kill the vehicle and the articles of the visiting client and recording the killing record;

the authority management module is used for generating access authority information according to the reservation success record and the killing record;

and the identification module is used for identifying the license plate of the vehicle and the driver of the vehicle according to the access authority information, generating an identification record and controlling a gateway brake to release the identified vehicle and the driver.

A third aspect of the present application provides a server comprising:

a memory storing at least one instruction; and

and a processor executing instructions stored in the memory to implement the guest visit management method.

According to the invention, the visitor visiting management efficiency is improved by automatically auditing the reservation application, automatically identifying the vehicle and the driver and managing the vehicle and the driver visiting authority; and the health condition of the driver is audited through a health epidemic prevention database, so that the epidemic prevention management efficiency of a factory is improved, and the problem of multiple audits of visitors who cannot effectively manage visits is solved. Furthermore, the killing of the visiting vehicles and articles can be effectively controlled and recorded.

Drawings

Fig. 1 is a flowchart of a visitor visiting management method according to an embodiment of the present invention.

Fig. 2 is a block diagram of a visitor visiting management apparatus according to an embodiment of the present invention.

FIG. 3 is a schematic diagram of an operating environment in accordance with an embodiment of the present invention.

Fig. 4 is a schematic diagram of a server according to an embodiment of the invention.

Description of the main elements

Visitor visiting management device	30
		Building module	301
Application module	302
		Auditing module	303
Instruction generation module	304
		Authority management module	305
Identification module	306
		Server	40
Customer database	401
		Main gear	402
Database for appointment applications	403
		Database for recording reservation success	404
Database of killing records	405
		Access rights repository	406
Identification record database	407
		Photographing device	421
Channel gate	422

Image capturing apparatus	423
		Detection device	424
Health epidemic prevention database	411
		Network	430、431
Server	6
		Memory device	61
Processor with a memory having a plurality of memory cells	62
		Computer program	63

Detailed Description

In order that the above objects, features and advantages of the present invention can be more clearly understood, a detailed description of the present invention will be given below with reference to the accompanying drawings and specific embodiments. It should be noted that the embodiments and features of the embodiments of the present application may be combined with each other without conflict.

In the following description, numerous specific details are set forth to provide a thorough understanding of the present invention, and the described embodiments are merely a subset of the embodiments of the present invention, rather than a complete embodiment. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

The visitor management method of the embodiment of the invention is applied to a server, and can also be applied to a hardware environment formed by the server and electronic equipment connected with the server through a network, and is executed by the server and the electronic equipment together. Networks include, but are not limited to: a wide area network, a metropolitan area network, or a local area network.

The server may be a computer or a computer system that provides services to other devices (e.g., electronic devices) in the network. A personal computer may also be called a server if it can externally provide a File Transfer Protocol (FTP) service.

The server is an electronic device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction, and the hardware thereof includes, but is not limited to: microprocessors, Application Specific Integrated Circuits (ASICs), programmable gate arrays (FPGAs), digital processors (DSPs), embedded devices, and the like. The server may also include a network device and/or a user device. Wherein the network device includes, but is not limited to, a single network server, a server group consisting of a plurality of network servers, or a Cloud Computing (Cloud Computing) based Cloud consisting of a large number of hosts or network servers, wherein Cloud Computing is one of distributed Computing, a super virtual computer consisting of a collection of loosely coupled computers. The user equipment includes, but is not limited to: any electronic product, such as a personal computer, a tablet computer, a smart phone, a Personal Digital Assistant (PDA), etc., can interact with a user through a keyboard, a mouse, a remote controller, a touch pad, a voice control device, etc.

Example 1

Fig. 1 is a flowchart of a visitor visit management method according to an embodiment of the present invention. The order of the steps in the flow chart may be changed and some steps may be omitted according to different needs.

Referring to fig. 1, the visitor visiting management method is applied to a server, and specifically includes the following steps:

step S11, according to the customer database pre-stored in the server, a master file is established for the visiting customer.

With reference to the schematic diagram shown in fig. 3, in this embodiment, the creating a master file for the visiting client according to the client database pre-stored in the server includes:

the company information of the visiting client, the staff information associated with the visiting client, and the vehicle information associated with the visiting client are imported from a client library 401 pre-stored in the server 40 to a master file 402.

Specifically, the company information includes: name, code, person in charge, etc.; the staff information includes: name, identification card number, contact mode, responsible unit, service type, service area, personnel type, etc.; the vehicle information includes: license plate, vehicle type, date of delivery, number of axles, color of head, GPS web address, GPS account number, GPS password, vehicle accessory, vehicle use, driver name associated with the vehicle, etc.

And step S12, receiving the appointment application submitted by the visiting client.

With reference to the schematic diagram shown in fig. 3, in this embodiment, the receiving the reservation application submitted by the visiting client includes:

receiving a reservation request submitted by the visiting client, and storing the received reservation request in a reservation request database 403 in the server 40, wherein the reservation request comprises a vehicle reservation and a personnel reservation. Specifically, the vehicle reservation may include a company name, a license plate, a driver's name associated with the vehicle, and the like, and the person reservation may include a company name, a person name, a certificate number, and the like.

And step S13, checking the reservation application based on the master file according to a preset method, and generating a reservation success record when the checking is passed.

With reference to the schematic diagram shown in fig. 3, in this embodiment, the reviewing the reservation application based on the master file according to the preset method, and the generating a reservation success record when the review is passed includes:

judging whether the vehicle reserved by the vehicle and the personnel in the personnel reservation are recorded in the master file 402, accessing a health epidemic prevention database 411 connected with the server 40 through a network 430 and obtaining historical movement records and health conditions recorded by the personnel in the health epidemic prevention database 411 when the vehicle and the personnel are recorded in the master file 402, determining that the historical movement records and the health conditions are in accordance with preset conditions, determining that the historical movement records and the health conditions are approved, generating reservation success records according to the reservation application, storing the reservation success records in a reservation success record database 404, or determining that the historical movement records or the health conditions are not in accordance with the preset conditions, determining that the historical movement records and the health conditions are not in accordance with the preset conditions, outputting reservation failure information and prompting the non-met preset conditions.

Specifically, the historical trend record includes: departure date, departure time, arrival date, arrival time, departure place, destination, transportation, vehicle number/license plate, trip purpose, presence or absence of people related to epidemic situation areas, presence or absence of epidemic situation area contact history and the like; the health conditions include: time of measurement, body temperature, location, current location, cough, diarrhea, chest tightness, exertion, runny nose, sore throat, palpitation, muscle soreness, other abnormalities, and the like.

And step S14, generating a killing instruction based on the reservation success record, sending the killing instruction to a designated person to kill the vehicle and the articles of the visiting client, and recording the killing record.

With reference to the schematic diagram shown in fig. 3, in this embodiment, the generating a killing instruction based on the reservation success record, and sending the killing instruction to a designated person to kill the vehicle and the article of the visiting customer includes:

the kill instruction is generated when the visiting customer's vehicle and the driver of the vehicle are consistent with the reservation success record in the reservation success record repository 404.

With reference to the schematic diagram shown in fig. 3, in this embodiment, the record killing record includes:

recording the killing time, the information of the killed vehicles, the information of the drivers of the killed vehicles and the image data of the killing process recorded by the photographing device 421; the killing record is generated according to the killing time, the killed vehicle, the driver information and the image data, the killing record is transmitted to the server through a network 431, and the killing record is stored in a killing record database 405.

And step S15, generating access authority information according to the reservation success record and the killing record.

With reference to the schematic diagram shown in fig. 3, in this embodiment, the generating the access right information according to the reservation success record and the kill record includes:

when the vehicle information in the killing record stored in the killing record database 405 matches the vehicle information in the reservation success record stored in the reservation success record database 404, the access authority information is generated according to the vehicle information and the driver information, and is stored in the access authority database 406.

And step S16, identifying the license plate of the vehicle and the driver of the vehicle according to the access authority information, generating an identification record, and controlling a gateway brake to release the identified vehicle and the driver.

In the present embodiment, in conjunction with the schematic diagram shown in fig. 3, the license plate of the vehicle and the driver of the vehicle are identified according to the access authority information in the access authority database 406, an identification record is generated and stored in the identification record database 407, and the control gateway 422 passes through the identified vehicle and the identified driver.

With reference to the schematic diagram shown in fig. 3, in this embodiment, the identifying the license plate of the vehicle and the driver of the vehicle according to the access authority information and generating the identification record includes:

shooting an image of the vehicle by using a shooting device 423, recognizing a license plate number of the vehicle based on the shot image, and recording recognition time, recognition position and the license plate number;

detecting the certificate of the driver through a detection device 424, and identifying the identity information of the driver recorded by the certificate;

and generating an identification record according to the recorded identification time, identification position, license plate number and identity information, and storing the identification record in the identification record database 407.

According to the invention, the visitor visiting management efficiency is improved by automatically auditing the reservation application, automatically identifying the vehicle and the driver and managing the vehicle and the driver visiting authority; and the health condition of the driver is checked through a health epidemic prevention database, so that the epidemic prevention management efficiency of an access area is improved, and the problem of multiple checks of visitors who cannot effectively manage visits is solved. Furthermore, the killing of the visiting vehicles and articles can be effectively controlled and recorded.

Example 2

Fig. 2 is a block diagram of a visitor management device 30 according to an embodiment of the invention.

In some embodiments, the guest visiting management apparatus 30 operates in a server. The guest visiting management apparatus 30 may include a plurality of function modules composed of program code segments. Program codes of respective program segments in the guest visit management apparatus 30 may be stored in a memory and executed by at least one processor to perform a guest visit management function.

In this embodiment, the visitor management device 30 may be divided into a plurality of functional modules according to the functions performed by the visitor management device. Referring to fig. 2, the visitor management device 30 may include an establishing module 301, an applying module 302, an auditing module 303, an instruction generating module 304, a rights management module 305, and an identifying module 306. The module referred to herein is a series of computer program segments capable of being executed by at least one processor and capable of performing a fixed function and is stored in memory. In some embodiments, the functionality of the modules will be described in greater detail in subsequent embodiments.

The establishing module 301 establishes a master file for the visiting client according to a client database pre-stored in the server.

In this embodiment, the establishing module 301, according to the client database pre-stored in the server, establishes a master file for the visiting client, including:

the establishing module 301 imports company information of the visiting client, staff information associated with the visiting client, and vehicle information associated with the visiting client from the client database pre-stored in the server to the master file.

The application module 302 receives a reservation application submitted by the visiting client.

In this embodiment, the receiving, by the application module 302, the reservation application submitted by the visiting client includes:

the application module 302 receives a reservation application submitted by the visiting client, and stores the received reservation application in the server, wherein the reservation application comprises a vehicle reservation and a personnel reservation. Specifically, the vehicle reservation may include a company name, a license plate, a driver's name associated with the vehicle, and the like, and the person reservation may include a company name, a person name, a certificate number, and the like.

The auditing module 303 audits the reservation application based on the master file according to a preset method, and generates a reservation success record when the audit is passed.

In this embodiment, the auditing module 303 audits the reservation application based on the master file according to a preset method, and generating a reservation success record when the audit is passed includes:

the auditing module 303 judges whether the vehicle reserved by the vehicle and the personnel in the personnel reservation are recorded in the master file, and accesses a health epidemic prevention database and acquires the historical movement record and the health condition of the personnel recorded in the health epidemic prevention database when the vehicle and the personnel are both recorded in the master file;

The instruction generating module 304 generates a killing instruction based on the reservation success record, sends the killing instruction to a designated person to kill the vehicle and the articles of the visiting customer, and records the killing record.

In this embodiment, the instruction generating module 304 generates a killing instruction based on the reservation success record, and sending the killing instruction to a designated person to kill the vehicle and the article of the visiting customer includes:

In this embodiment, the record killing record includes:

The rights management module 305 generates access rights information according to the reservation success record and the kill record.

In this embodiment, the generating, by the rights management module 305, the access rights information according to the successful reservation record and the kill record includes:

The identification module 306 identifies the license plate of the vehicle and the driver of the vehicle according to the access authority information, generates an identification record, and controls a gateway to pass the identified vehicle and the driver.

In this embodiment, the identifying module 306, identifying the license plate of the vehicle and the driver of the vehicle according to the access right information and generating the identification record, includes:

Example 3

Fig. 4 is a schematic diagram of the server 6 according to an embodiment of the present invention.

The server 6 comprises a memory 61, a processor 62 and a computer program 63 stored in the memory 61 and executable on the processor 62. The processor 62, when executing the computer program 63, implements the steps of the guest visit management method embodiment, such as the steps S11-S16 shown in fig. 1. Alternatively, the processor 62 executes the computer program 63 to implement the functions of the modules/units in the visitor management device embodiment, such as the modules 301 to 306 in fig. 2.

Illustratively, the computer program 63 may be partitioned into one or more modules/units that are stored in the memory 61 and executed by the processor 62 to carry out the invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 63 in the server 6. For example, the computer program 63 may be divided into a setup module 301, an application module 302, an audit module 303, an instruction generation module 304, a rights management module 305, and an identification module 306 in fig. 2, and specific functions of each module are described in embodiment 2.

In this embodiment, the server 6 may be a computer or a computer system capable of providing services to other devices (e.g., electronic devices) in the network. It will be appreciated by those skilled in the art that the schematic diagram is merely an example of a server 6 and does not constitute a limitation of the server 6, and may include more or less components than those shown, or some components in combination, or different components, e.g., the server 6 may also include input output devices, network access devices, buses, etc.

The Processor 62 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor 62 may be any conventional processor or the like, the processor 62 being the control center for the server 6, with various interfaces and lines connecting the various parts of the overall server 6.

The memory 61 may be used for storing the computer programs 63 and/or modules/units, and the processor 62 may implement various functions of the server 6 by running or executing the computer programs and/or modules/units stored in the memory 61 and calling data stored in the memory 61. The memory 61 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the server 6, and the like. In addition, the memory 61 may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.

The integrated modules/units of the server 6, if implemented in the form of software functional modules and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and which, when executed by a processor, may implement the steps of the above-described embodiments of the method. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like.

In the embodiments provided in the present invention, it should be understood that the disclosed server and method can be implemented in other ways. For example, the above-described server embodiment is only illustrative, and for example, the division of the modules is only one logical functional division, and there may be other divisions when the actual implementation is performed.

In addition, each functional module in each embodiment of the present invention may be integrated into the same processing module, or each module may exist alone physically, or two or more modules may be integrated into the same module. The integrated module can be realized in a hardware form, and can also be realized in a form of hardware and a software functional module.

It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is to be understood that the word "comprising" does not exclude other modules or steps, and the singular does not exclude the plural. Several modules or electronic devices recited in the server claims may also be implemented by one and the same module or electronic device by means of software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.

Finally, it should be noted that the above embodiments are only for illustrating the technical solutions of the present invention and not for limiting, and although the present invention is described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A visitor visiting management method is applied to a server, and is characterized by comprising the following steps:

receiving a reservation application submitted by the visiting client;

2. The visitor visiting management method of claim 1, wherein the establishing a master profile for the visiting client according to a client library pre-stored in the server comprises:

3. The visitor visit management method as claimed in claim 1, wherein said receiving a reservation request submitted by the visiting client comprises:

4. The visitor visit management method of claim 3, wherein the reviewing the reservation application based on the master profile in a predetermined method, the generating a reservation success record when the review passes comprises:

when the historical movement record and the health condition accord with preset conditions, the record is determined to be passed, the reservation success record is generated according to the reservation application, or when the historical movement record or the health condition does not accord with the preset conditions, the record is determined to be not passed, reservation failure information is output, and the preset conditions which do not accord with are prompted.

5. The visitor visit management method of claim 1, wherein the generating a kill instruction based on the reservation success record, the sending the kill instruction to a designated person to kill the visitor customer's vehicle and items comprises:

6. The visitor visit management method of claim 1, wherein the recording a kill record comprises:

7. The visitor visit management method of claim 1, wherein the generating the access right information according to the reservation success record and the kill record comprises:

8. The visitor visit management method as claimed in claim 1, wherein said identifying a license plate of the vehicle and a driver of the vehicle according to the access right information and generating an identification record comprises:

9. A visitor visiting management apparatus applied to a server, the apparatus comprising:

10. A server, characterized in that the server comprises:

a memory storing at least one instruction; and

a processor executing instructions stored in the memory to implement the guest visit management method of any one of claims 1 to 8.