JP6013848B2 - Facility management system and facility management method - Google Patents

Description

  The present invention relates to a facility management system and a facility management method for managing a facility.

  2. Description of the Related Art Conventionally, facility management systems that check whether or not a visitor to a facility is an appropriate person and monitor unauthorized intrusion into the facility have been used. For example, the intercom system disclosed in Patent Document 1 captures a face image of a visitor and displays it on a terminal in the room, and also talks with the visitor via the terminal in the room, so that the visitor is a suspicious visitor. It is possible to determine whether or not.

  Patent Document 2 discloses a home security system in which an intrusion attempt is detected by providing a sensor at a window or an entrance and operating a sensor when a resident sets the guard mode.

JP 2012-160830 A JP 2008-65746 A

  However, the above-described technique of Patent Document 1 determines whether or not a resident is a suspicious person based on a visitor's image or conversation, and the confirmation of the visitor's identity has been insufficient. . For example, if a visitor tells you that you are in a courier uniform and has come to deliver, you can check if the person is truly a courier or a suspicious person posing as a courier. There wasn't. For this reason, it is required to improve convenience by guaranteeing the identity of the visitor.

  Moreover, since the technique of the above-mentioned patent document 2 performs on / off control of a warning mode from an indoor terminal, there is a problem that convenience is low. Specifically, since it is often the case that the resident goes out, the warning mode can be set to ON while leaving the doorway. It is also desirable to be able to operate outside the entrance / exit even when the warning mode is set to OFF when returning home.

  For these reasons, it has become an important issue how to realize a facility management system that can improve the convenience of visitor identity guarantee and security operation switching.

  The present invention has been made to solve the above-described problems of the prior art, and an object of the present invention is to provide a facility management system and a facility management method that can improve convenience.

In order to solve the above-described problems and achieve the object, the invention according to claim 1 is a facility management system for managing a facility, and is carried by a visitor visiting the facility and identifies the visitor. and portability of the identification information holding means for holding the visitor identification information, from the identification information holding means, located on the outside of the facility, the identification information reading means for reading the visitor identification information, by the identification information reading means Identification information transmitting means for transmitting the read visitor identification information to an authentication center, authentication means for performing authentication processing of the visitor based on the visitor identification information transmitted to the authentication center, and the authentication means It is operable in the facility inside based on the authentication result by the authentication result using terminal for notifying the visitor authentication result to the person in the facility, the visitor The position information of the question and facilities, wherein the purpose of the visit by the visitor and a visit history management means for managing whether the transient has been achieved as a visit history.

Further, an invention according to claim 2, in the invention described in claim 1, wherein the identification information reading means, wherein disposed on the outside of the facility, the identification information holding means before Ri by the short-range wireless communication from Symbol It is characterized by reading visitor identification information.

According to a third aspect of the present invention, in the first aspect of the present invention, the visitor identification information is written in the identification information holding means, and the identification information reading means is the written visitor identification. Information is read by image recognition.

The invention according to claim 4 is the invention according to claim 1, 2 or 3 , wherein the authentication means is at least one of the affiliation, visitor name, date of birth, image and sound of the visitor. Any one of them is output as the authentication result.

The invention according to claim 5 further comprises output range setting means for individually setting information to be included in the authentication result for each visitor by the authentication means in the invention according to claim 4. Features.

The invention of claim 6 is the invention according to any one of claims 1 to 5, based on the previous SL access history, determining hands stage whether the visiting is appropriate Is further provided.

The invention according to claim 7 is the invention according to any one of claims 1 to 6 , wherein an information acquirer who is permitted to acquire information on the state of the facility is authenticated, and the information acquirer is authenticated. On the other hand, the information processing device further includes information providing means for providing information on an authentication result by the authentication means.

The invention according to claim 8 is a facility management method for managing a facility, and visitor identification information for identifying a visitor visiting the facility from identification information holding means located outside the facility. an identification information reading step of reading, on the basis of the said identification information reading an identification information transmitting step of transmitting the visitor identification information read in the authentication center in step, the visitor identification information transmitted to the authentication center An authentication step for performing a visitor authentication process, an authentication result transmission step for transmitting an authentication result obtained by the authentication step to an authentication result utilization terminal operable within the facility, and a location of the facility visited by the visitor information, that it contained a visiting history management step of managing whether a transient object of the visit by the visitor was achieved as access history And butterflies.

According to the present invention, the visitor identification information is read from the identification information holding means located outside the facility, the visitor identification information is transmitted to the authentication center, and authentication is performed based on the visitor identification information transmitted to the authentication center. Since the processing is performed and the authentication result using terminal is operated based on the authentication result, convenience related to the management of the facility can be improved.

FIG. 1 is an explanatory diagram for explaining visitor authentication according to the first embodiment. FIG. 2 is a diagram illustrating a system configuration of the facility management system according to the first embodiment. FIG. 3 is an internal configuration diagram showing an internal configuration of the authentication server shown in FIG. FIG. 4 is an explanatory diagram for describing data stored in the storage unit illustrated in FIG. 3. FIG. 5 is an internal configuration diagram showing an internal configuration of the indoor terminal shown in FIG. FIG. 6 is a flowchart for explaining the operation of the facility management system shown in FIG. FIG. 7 is an explanatory diagram for explaining the use of the visit history. FIG. 8 is an explanatory diagram for explaining visitor authentication according to the second embodiment. FIG. 9 is an internal configuration diagram showing an internal configuration of the mobile terminal shown in FIG. FIG. 10 is an explanatory diagram for explaining home security control according to the third embodiment. FIG. 11 is a diagram illustrating a system configuration of the facility management system according to the third embodiment. FIG. 12 is an internal configuration diagram showing an internal configuration of the authentication server shown in FIG. FIG. 13 is an explanatory diagram for describing data stored in the storage unit illustrated in FIG. 12. FIG. 14 is an internal configuration diagram showing an internal configuration of the monitoring control terminal shown in FIG. FIG. 15 is a flowchart for explaining the operation of the facility management system shown in FIG.

  Exemplary embodiments of a facility management system and a facility management method according to the present invention will be described below in detail with reference to the accompanying drawings.

  In Example 1, a facility management system that authenticates visitors to a residence will be described. FIG. 1 is an explanatory diagram for explaining visitor authentication according to the first embodiment. As shown in FIG. 1, a visitor carries a card 21, and a reading terminal 10 is provided outside a residence that is a visited facility.

  The card 21 has a near field communication function and holds a visitor ID (Identification) for identifying a visitor. When the visitor holds the card 21 over the visited reading terminal 10, the reading terminal 10 reads the visitor ID (1) and transmits the read visitor ID to the indoor terminal 40 (2). The indoor terminal 40 transmits a verification request including the visitor ID and the indoor terminal ID of the terminal itself to the authentication server 30 (3).

  The authentication server 30 holds a registrant database 32a in which information about visitors and information about destinations are registered in advance. Here, the visitor ID of the card 21 is registered in the registrant database 32a as information related to the visitor, and the indoor terminal ID of the indoor terminal 40 is registered in the registrant database 32a as information related to the visited place.

  If the authentication server 30 receives the verification request including the visitor ID and the indoor terminal ID from the indoor terminal 40, the authentication server 30 performs verification of the visitor based on the registrant database 32a. As a result of this collation, when it is determined that the visit is an appropriate visit, the authentication server 30 transmits the collation result to the indoor terminal 40 (4). The collation result preferably includes information about the visitor, such as affiliation, name, and visitor face image.

  The indoor terminal 40 outputs the verification result received from the authentication server 30 by display or the like, and notifies the resident of the residence that there was a visit. The resident can check the information about the visitor by using the indoor terminal 40 and can deal with the visitor. For example, by talking with the visitor through the intercom, it is possible to confirm whether the affiliation or name described by the visitor matches the affiliation or name obtained as a comparison result. Similarly, it can be confirmed whether or not the appearance of the visitor matches the face image obtained as a matching result.

  In this way, the card 21 storing the visitor ID is issued to the visitor, and the visitor ID is read from the card 21 held by the visitor and transmitted to the authentication server 30 to perform authentication. It is possible to determine whether or not the visitor is a proper visitor. If the visitor is an appropriate visitor, by transmitting information related to the visitor to the indoor terminal 40 of the residence, the resident can take action after confirming the visitor's information.

  Next, the system configuration of the facility management system according to the first embodiment will be described. FIG. 2 is a diagram illustrating a system configuration of the facility management system according to the first embodiment. As illustrated in FIG. 2, the facility management system according to the first embodiment includes a plurality of cards 21, a plurality of visit targets, an authentication server 30, a service management device 50, a plurality of visitor registration centers 60, and a plurality of visitor registration centers 60. And a guardian terminal 70. The visit target includes the indoor terminal 40 and the reading terminal 10.

  The authentication server 30 is connected to the indoor terminal 40 and the guardian terminal 70 via a network. The authentication server 30 is connected to the service management device 50 and the visitor registration center 60. The connection between the authentication server 30, the service management apparatus 50, and the visitor registration center 60 may also be a connection via a network.

  The visitor registration center 60 is a center that registers visitors with the authentication server 30. The visitor registration center 60 is provided by a company that performs a visit to a visit target, such as a company that performs a home delivery service, a company that provides home care, and the like. The card 21 carried by the person is registered in the authentication server 30.

  The authentication server 30 accepts visitor registration from the visitor registration center 60. The authentication server 30 also accepts registration for the visit target. When the authentication server 30 receives the verification request including the indoor terminal ID and the visitor ID from the indoor terminal 40, the authentication server 30 verifies the indoor terminal ID and the visitor ID with the registered information, so that the visit is appropriate. It is determined whether it is a thing. That is, the authentication server 30 verifies the visitor's identity based on the information registered by the visitor registration center 60.

  Moreover, the authentication server 30 memorize | stores the log | history of a visit, when the collation request | requirement containing indoor terminal ID and visitor ID is received from the indoor terminal 40. FIG.

  The authentication server 30 also accepts browsing of visit histories from the service management device 50 and the guardian terminal 70. The service management apparatus 50 and the guardian terminal 70 that perform browsing are in a state in which necessary information is registered in the authentication server 30 in advance and authentication for browsing is possible. When various services are charged, the authentication server 30 manages the charging information and accepts browsing of the charging information from the service management device 50 and the guardian terminal 70. For browsing from the service management device 50 or the guardian terminal 70, a range of information that can be browsed for each viewer can be set.

  The service management device 50 is a device for an administrator that manages a visitor authentication service. The service management apparatus 50 can register with the authentication server 30 in advance and perform authentication, thereby browsing various information included in the authentication server 30 and collecting visit proofs and billing information.

  The guardian terminal 70 is a terminal associated with the visited site. For example, when the visit target is a residence where an elderly person lives, the visit history can be confirmed from another place by registering the terminal of the related person as the guardian terminal 70. It is also possible to register and charge various information related to the visit target from the guardian terminal 70.

  Next, the internal configuration of the authentication server 30 shown in FIG. 2 will be described. FIG. 3 is an internal configuration diagram showing an internal configuration of the authentication server 30 shown in FIG. As illustrated in FIG. 3, the authentication server 30 includes a communication unit 31, a storage unit 32, and a control unit 33.

  The communication unit 31 is a communication interface for communicating with the indoor terminal 40, the service management device 50, the visitor registration center 60, and the guardian terminal 70. The storage unit 32 is a storage device such as a hard disk device or a nonvolatile memory, and stores a registrant database 32a and a visit history 32b.

  The registrant database 32 a is a database that stores information about visitors registered by the visitor registration center 60 and information about destinations registered by the indoor terminal 40 or the guardian terminal 70. The visit history 32b is data indicating the history of visits by visitors.

  The control unit 33 is a control unit that controls the entire authentication server 30, and includes a visitor registration unit 33a, a visit destination registration unit 33b, a verification processing unit 33c, a verification result notification unit 33d, a visit history management unit 33e, and a browsing processing unit 33f. Have

  The visitor registration unit 33a is a processing unit that performs processing for registering information related to visitors received from the visitor registration center 60 in the registrant database 32a. The visited site registration unit 33b is a processing unit that performs processing for registering information about the visited site received from the indoor terminal 40 or the guardian terminal 70 in the registrant database 32a.

  The verification processing unit 33c is a processing unit that performs verification of a visitor based on the registrant database 32a when a verification request including a visitor ID and an indoor terminal ID is received from the indoor terminal 40. The collation result notification unit 33d transmits the collation result to the indoor terminal 40. Further, when it is determined that the visit is an appropriate visit as a result of the collation, information on the visitor, for example, the affiliation, the name, and the visitor's face image are included in the collation result.

  The visit history management unit 33e is a processing unit that updates the visit history 32b when a matching request including a visitor ID and an indoor terminal ID is received from the indoor terminal 40. The browsing processing unit 33f authenticates the service management device 50 and the guardian terminal 70 when receiving access from the service management device 50 and the guardian terminal 70, and provides data such as a visit history 32b when the authentication is successful. Is a processing unit.

  Next, data stored in the storage unit 32 shown in FIG. 3 will be described. FIG. 4 is an explanatory diagram for describing data stored in the storage unit 32 illustrated in FIG. 3. As shown in FIG. 4, the registrant database 32a includes visitor data that is information related to visitors registered by the visitor registration unit 33a, and visit destinations that are information related to visits registered by the visit destination registration unit 33b. Contains data.

  The visitor data includes a device type, a visitor ID, a visitor's organization, a visitor's personal name, a visitor's date of birth, a visitor's biometric information, a notification range setting, and a final visit destination. The model type indicates the type of a storage medium that holds a visitor ID such as a card, a tag, or a mobile terminal. The visitor ID is transmitted to the authentication server 30 together with the indoor terminal ID at the time of authentication. At this time, the collation date may be further transmitted.

  The affiliation, personal name, date of birth, and biometric information are notified to the indoor terminal 40 together with the verification result. All of these pieces of information may be transmitted, or a part of the information may be selected and transmitted. The notification range setting defines which of these pieces of information is notified. Moreover, the last visited place shows the visited place which read the visitor ID last. By using this final destination, it is possible to determine whether the visitor carrying the card 21 is appropriately moved.

  The registrant data may include data such as public / private information and dispatch status. The public / private information is used to notify a visitor whether the visitor is visiting publicly or privately. Specifically, it is managed by a flag or the like in cooperation with an attendance management system or an entry / exit management system in the company to which the visitor belongs. This public / private information indicates that if the visitor is on duty, the visit is public, and if the visit is off-duty, It is shown that it is a typical visit. In addition, in cooperation with a system for managing public visits from companies, private visits may be made if the visitor is not designated even if he / she is on duty.

  The dispatch state is used to notify the visited party whether or not the visitor is dispatched (for example, engaged in a delivery service). This dispatch state can be switched using GPS information of a delivery truck, GPS information of a portable terminal carried by a visitor, or the like. If it is an appropriate visit, the dispatched state should be dispatched, and if the visit was made even though the dispatched state was not dispatched, the visitor himself was temporarily registered. Even a person is shown to be a suspicious visit.

  The visited data includes the device type, indoor terminal ID, visited name, visited location information, contractor information, user information, notification method, and telephone transfer destination. The device type is the type of the indoor terminal 40. The indoor terminal ID is the ID of the indoor terminal 40.

  The visited name is text data indicating the name of the visited place, and the visited position information is data such as the visited address, GPS position information, and address code. The contractor information is data indicating the name of the contractor, the telephone number, whether it is an individual or a corporation, and the like. The contractor may be a resident of the visited site, or may be another person such as a guardian or a corporation. The user information is data indicating the name of the resident of the visited site, a telephone number, whether the person is a person or a corporation, and the like.

  The notification method is data that specifies a method for notifying the verification result. When the indoor terminal 40 has a display unit, the verification result is notified as displayable data. On the other hand, when the indoor terminal 40 does not have a display unit, the collation result is notified as data that can be output by voice. The telephone transfer destination is a telephone number of a visited place to be used when the collation result is transferred to the telephone and output by voice. In addition, the visitor data includes information for verifying the identity of the resident, the date and time of the last connection, information on the history of successive visits, etc., to detect impersonation of the resident, breakdown, and the occurrence of an attack Can be used.

  The visit history 32b includes date and time, visitor ID, indoor terminal ID, visited location information, verification result, and visit result. The date and time indicate the date and time when the visit was made, and the ID included in the verification request is stored in the visitor ID and the indoor terminal ID. The visited location information is visited location information corresponding to the indoor terminal ID.

  The verification result indicates whether the verification is successful. The visit result indicates whether or not the purpose of the visit has been achieved. For example, if a visit was made to deliver a package, the purpose of the visit was achieved when the package was received, and if the visit was made for care, the care was completed. In some cases, the purpose of the visit has been achieved. The visit result is updated by notification from the indoor terminal 40.

  Next, the internal configuration of the indoor terminal 40 shown in FIG. 2 will be described. FIG. 5 is an internal configuration diagram showing an internal configuration of the indoor terminal 40 shown in FIG. As illustrated in FIG. 5, the indoor terminal 40 includes a communication unit 41, a microphone 42, a speaker 43, an operation unit 44, a display unit 45, a control unit 46, and a storage unit 47. The communication unit 41 is a communication interface for communicating with the reading terminal 10 and the authentication server 30.

  The microphone 42 is a device that collects a resident's voice, and the collected voice is used for output from an intercom terminal provided outside the door. The speaker 43 is used for outputting voice data received from an intercom terminal provided on the outside of the door or the authentication server 30, calling a resident when receiving a verification result, and the like. The microphone 42 and the speaker 43 allow the resident to have a conversation with the visitor through the intercom terminal.

  The operation unit 44 is a touch panel, a button, or the like that receives a resident's operation input. The display unit 45 is a liquid crystal display or the like for performing display output, and is used for displaying the verification result received from the authentication server 30. The storage unit 47 is a storage device such as a nonvolatile memory, and stores the indoor terminal ID 47 a of the indoor terminal 40. The indoor terminal ID 47a is registered in the authentication server 30 in advance.

  The control unit 46 is a control unit that totally controls the indoor terminal 40, and includes a reading processing unit 46a, a verification request unit 46b, a verification result receiving unit 46c, a verification result notification unit 46d, a visitor response processing unit 46e, and an abnormal termination unit 46f. Have

  The reading processing unit 46 a performs processing for acquiring a visitor ID read by the reading terminal 10 from the card 21. When the reading processing unit 46a acquires the visitor ID, the verification request unit 46b reads the indoor terminal ID 47a from the storage unit 47 and transmits a verification request including the acquired visited ID and indoor terminal ID 47a to the authentication server 30. Is a processing unit.

  The verification result receiving unit 46 c is a processing unit that receives the verification result from the authentication server 30. When the collation result receiving unit 46c receives the collation result, the collation result notifying unit 46d controls the display of the received collation result on the display unit 45 and outputs a ringing tone from the speaker 43 to visit the resident. That the person is present.

  If the resident recognizes the presence of the visitor by the ringing tone output from the speaker 43, the resident can confirm the information related to the visitor based on the content displayed on the display unit 45. In addition, since the visitor correspondence processing unit 46e performs a call connection between the visitor and the resident using the microphone 42 and the speaker 43, the resident can determine the correspondence to the visitor from the collation result and the call content. it can. If a camera is provided outside the door, the visitor image captured by the camera can be displayed on the display unit 45. Further, when the resident determines that the visitor is an inappropriate person, the resident may be configured to notify the authentication server 30 of an inappropriate visit.

  Further, the visitor correspondence processing unit 46e performs a process of accepting a resident's operation and transmitting a visit purpose achievement notice to the authentication server 30 when the visit purpose is achieved.

  The abnormal end unit 46f notifies the resident of the timeout by the display unit 45 when the verification request unit 46b transmits a verification request to the authentication server 30 and does not receive the verification result within a predetermined time. To do. This is because if the verification result cannot be obtained indefinitely due to a communication abnormality or the like, the visitor cannot reach the destination even though the destination has been reached.

  Next, the operation of the facility management system shown in FIG. 2 will be described. FIG. 6 is a flowchart for explaining the operation of the facility management system shown in FIG. As shown in FIG. 6, the indoor terminal 40 determines whether or not the reading terminal 10 has read the visitor ID from the card 21 (step S101), and if it has not read the visitor ID (step S101; No), A standby operation is performed to determine whether or not the visitor ID has been read again.

  When the visitor ID is read (step S101; Yes), the indoor terminal 40 transmits a verification request including the read visitor ID and the indoor terminal ID of the own terminal to the authentication server 30 (step S102). . And it is determined whether the collation result was received from the authentication server 30 (step S103).

  If the collation result has not been received (step S103; No), the indoor terminal 40 determines whether or not the abnormal termination condition is satisfied (step S104). As a condition for abnormal termination, a case where a predetermined time has elapsed since the transmission of the verification request, a case where occurrence of a communication abnormality, or the like can be used.

  If the condition for abnormal termination is not satisfied (step S104; No), the indoor terminal 40 proceeds to step S103 and determines whether or not a collation result has been received. If the abnormal termination condition is satisfied (step S104; Yes), the abnormal termination content is output to the display unit 45 or the like as a collation result (step S105), and the process is terminated.

  On the other hand, when the verification result is received from the authentication server 30 (step S103; Yes), the indoor terminal 40 outputs a ringing tone by the speaker 43 to notify the visit, and the received verification result is displayed on the display unit 45 or the like. (Step S105)

  Moreover, if the indoor terminal 40 receives operation for achieving the visit purpose from the resident (step S106; Yes), the indoor terminal 40 transmits a visit purpose achievement notification to the authentication server 30 (step S107), and ends the process. In addition, if the operation for achieving the purpose of the visit is not received from the resident (step S106; No), the process is terminated as it is.

  The authentication server 30 determines whether or not a verification request including a visitor ID and an indoor terminal ID has been received from the indoor terminal 40 (step S201). If no verification request has been received (step S201; No), the authentication server 30 again. A standby operation is performed to determine whether or not a verification request has been received.

  If the authentication server 30 receives the verification request (step S201; Yes), the authentication server 30 performs verification processing (step S202). This collation process is a process of collating whether or not the received visitor ID and indoor terminal ID are registered in the registrant database 32a. Both the visitor ID and the indoor terminal ID are registered in the registrant database 32a. If the verification is successful, it is authenticated that the visit is appropriate. If either the visitor ID or the indoor terminal ID is not registered and the verification fails, the authentication server 30 determines that the visit is not an appropriate visit.

  The authentication server 30 transmits the result of the verification process to the indoor terminal 40 (step S203). In addition, when it is verified that the visit is an appropriate visit as a result of the collation, the visitor information corresponding to the visitor ID is included in the collation result.

  Further, the authentication server 30 updates the visit history 32b based on the result of the collation process (step S204). Furthermore, if the authentication server 30 receives the visit purpose achievement notification from the indoor terminal 40 (step S205; Yes), the authentication server 30 updates the visit result of the visit history 32b (step S206), and ends the process. If the authentication server 30 has not received the visit purpose achievement notification from the indoor terminal 40 (step S205; No), the process is terminated.

  Next, the use of the visit history 32b will be described. FIG. 7 is an explanatory diagram for explaining the use of the visit history 32b. The authentication server 30 and the service management apparatus 50 can obtain various types of information by counting the visit history 32b.

  Specifically, if visit destination position information is aggregated for the same visitor ID, a visitor's movement history can be obtained, and it can be determined whether or not a suspicious movement is being performed. In addition, by collecting the collation results and visit results, it is possible to obtain information on unauthorized visitors, terminal abnormalities, and attacks.

  That is, if verification failure is repeated for the same visitor ID, it indicates that the visitor is an unauthorized visitor or that an abnormality has occurred in the card 21. Further, if collation failures are repeated for the same visited ID, it indicates that an abnormality has occurred in the reading terminal 10 or the indoor terminal 40 or that an attack has been made on the visited destination. Furthermore, when the failure to achieve the purpose of the visit is repeated for the same indoor terminal ID, it is suggested that some abnormality has occurred in the resident.

  As described above, the facility management system according to the first embodiment issues a card 21 storing a visitor ID to a visitor, reads the visitor ID from the card 21 held by the visitor, and authenticates the server. By transmitting to 30 and performing authentication, it is possible to determine whether or not the visitor is an appropriate visitor. If the visitor is an appropriate visitor, by transmitting information related to the visitor to the indoor terminal 40 of the residence, the resident can take action after confirming the visitor's information.

  In addition, the visit history can be viewed from the service management device 50, the guardian terminal 70, etc., and the visit history is counted by summing up the visit histories, or an unauthorized visitor, terminal or tag The occurrence of abnormalities and the occurrence of attacks on visited sites can be detected.

  In the first embodiment, both the visitor ID and the indoor terminal ID are registered in the registrant database 32a, and when the verification is successful, it is determined that the visit is an appropriate visit. Even in the case of success, if there is a possibility of unauthorized visitation, the authentication may fail. Specifically, by counting the visit history 32b, visitors who have made illegal movements or illegal visits are extracted and registered in the blacklist, and the visitors who are registered in the blacklist are verified. Even if it succeeds, it may be an authentication failure.

  In addition, depending on the visitor, there is a case where a visit destination is determined or a region of the visit destination is determined. Therefore, it may be determined whether the visit is appropriate by preparing data in which a visitor and a visit destination are associated and referring to this data. If the visit schedule is determined, the visit schedule may be managed as data, and it may be determined whether the visit is appropriate by referring to this data.

  Further, in the first embodiment, the case where the verification result is notified to the indoor terminal 40 installed in the residence has been described, but the notification may be made to the portable terminal carried by the resident.

  In the first embodiment described above, the case where the visitor ID is read from the card 21 by NFC has been described. However, the visitor ID written on the card may be read by image recognition. Therefore, in the second embodiment, a configuration in which a visitor ID is read by image recognition will be described.

  FIG. 8 is an explanatory diagram for explaining visitor authentication according to the second embodiment. As shown in FIG. 8, as shown in FIG. 1, a visitor carries a card 121, and an intercom outer terminal 111 is provided outside a residence that is a visited facility.

  The card 121 has a visitor ID written on its surface. The visitor ID may be expressed as a character string or the like, or may be encoded and expressed as a barcode or a two-dimensional code. When the visitor holds the card 121 over the visiting intercom outer terminal 111, the intercom outer terminal 111 images the card 121 with a camera and transmits an image to the intercom inner terminal 112 in the residence (2).

  The intercom inner terminal 112 includes a display unit, and displays an image received from the intercom outer terminal 111 on the display unit. The resident reads the visitor ID by capturing an image of the visitor ID displayed on the intercom inner terminal 112 by the camera of the resident portable terminal 140 and performing image recognition (3). The resident portable terminal 140 transmits a verification request including the read visitor ID and the portable terminal ID of the own terminal to the authentication server 30 (4).

  The authentication server 30 holds a registrant database 32a in which information about visitors and information about destinations are registered in advance. Here, the visitor ID of the card 121 is registered in the registrant database 32a as information related to the visitor, and the mobile terminal ID of the mobile terminal 140 is registered in the registrant database 32a as information related to the visited place.

  If the authentication server 30 receives the verification request including the visitor ID and the mobile terminal ID from the mobile terminal 140, the authentication server 30 performs verification of the visitor based on the registrant database 32a. As a result of this collation, when it is determined that the visit is an appropriate visit, the authentication server 30 transmits the collation result to the mobile terminal 140 (5). The collation result preferably includes information about the visitor, such as affiliation, name, and visitor face image.

  The portable terminal 140 outputs the verification result received from the authentication server 30 by display or the like. The resident can check the information about the visitor using the mobile terminal 140 and can deal with the visitor. For example, by talking with the visitor through the intercom, it is possible to confirm whether the affiliation or name described by the visitor matches the affiliation or name obtained as a comparison result. Similarly, it can be confirmed whether or not the appearance of the visitor matches the face image obtained as a matching result.

  In this way, the card 121 indicating the visitor ID is issued to the visitor, and the visitor ID is read by image recognition from the card 121 presented by the visitor and transmitted to the authentication server 30 for authentication. Thus, it can be determined whether or not the visitor is an appropriate visitor. If the visitor is an appropriate visitor, by transmitting information related to the visitor to the portable terminal 140, the resident can take action after confirming the visitor's information.

  FIG. 9 is an internal configuration diagram showing an internal configuration of the mobile terminal 140 shown in FIG. As illustrated in FIG. 9, the mobile terminal 140 includes a wireless communication unit 141, a camera 142, an operation unit 144, a display unit 145, a storage unit 147, and a control unit 146.

  The wireless communication unit 141 is a communication interface for performing wireless communication with the authentication server 30. The camera 142 is used to capture an image displayed on the display unit of the intercom inner terminal 112.

  The operation unit 144 is a touch panel, a button, or the like that receives a resident's operation input. The display unit 145 is a liquid crystal display or the like for performing display output, and is used for displaying the collation result received from the authentication server 30. The storage unit 147 is a storage device such as a nonvolatile memory, and stores the mobile terminal ID 147a of the mobile terminal 140. The portable terminal ID 147a is registered in advance in the authentication server 30.

  The control unit 146 is a control unit that controls the mobile terminal 140 as a whole, and includes an image recognition unit 146a, a verification request unit 146b, a verification result reception unit 146c, a verification result notification unit 146d, a visitor correspondence processing unit 146e, and an abnormal termination unit 146f. Have

  The image recognition unit 146a performs a process of reading the visitor ID by performing image recognition on the image captured by the camera 142. When the image recognition unit 146a reads the visitor ID, the verification request unit 146b reads the mobile terminal ID 147a from the storage unit 147, and transmits a verification request including the read visit destination ID and the mobile terminal ID 147a to the authentication server 30. Is a processing unit.

  The verification result receiving unit 146 c is a processing unit that receives the verification result from the authentication server 30. The verification result notification unit 146d controls the display unit 145 to display the received verification result when the verification result reception unit 146c receives the verification result. For this reason, the resident can confirm the information regarding a visitor with the content displayed on the display part 145. FIG.

  The visitor correspondence processing unit 146e receives an inappropriate visit to the authentication server 30 when the resident determines that the visitor is an inappropriate person and performs a predetermined operation on the operation unit 144. Notify that. In addition, when the visit purpose is achieved, the visitor correspondence processing unit 146e accepts a resident's operation and transmits a visit purpose achievement notification to the authentication server 30.

  The abnormal end unit 146f notifies the resident of a timeout by the display unit 145 when the verification request is not received within a predetermined time after the verification request is transmitted to the authentication server 30 by the verification request unit 146b. To do. This is because if the verification result cannot be obtained indefinitely due to a communication abnormality or the like, the visitor cannot reach the destination even though the destination has been reached.

  As described above, the facility management system according to the second embodiment issues a card 121 indicating a visitor ID to the visitor, and reads the visitor ID by image recognition from the card 121 presented by the visitor. By transmitting to the authentication server 30 and performing authentication, it can be determined whether or not the visitor is an appropriate visitor. If the visitor is an appropriate visitor, by transmitting information related to the visitor to the portable terminal 140, the resident can take action after confirming the visitor's information.

  The processing operation of the mobile terminal 140 is the same as that of the indoor terminal 40 of the first embodiment. In addition, the visit history can be browsed from the service management device 50, the guardian terminal 70, etc., whether visitor movement is appropriate based on the summation of visit histories, illegal visitors, abnormal occurrence of terminals and tags, visits The point that it is possible to detect the occurrence of the previous attack is the same as in the first embodiment.

  In addition, even in the case where the verification is successful, if there is a possibility of an illegal visit, it can be configured so that the authentication fails, as in the first embodiment. Similarly to the first embodiment, data that associates a visitor with a visit destination and data that registers a visit schedule are prepared, and it is determined whether the visit is appropriate by referring to these data. You can also.

  In the first and second embodiments described above, the facility management system that authenticates visitors to the residence has been described. In the third embodiment, a facility management system that controls home security will be described. FIG. 10 is an explanatory diagram for explaining home security control according to the third embodiment. As shown in FIG. 10, a visitor carries a card 221, and a reading terminal 210 is provided outside a residence controlled by the security function.

  The card 221 has a near field communication function and holds a controller ID that identifies the controller. When the controller holds the card 221 over the reading terminal 210, the reading terminal 210 reads the controller ID (1) and transmits the read controller ID to the monitoring control terminal 240 (2). The supervisory control terminal 240 transmits a control request including the controller ID and the control terminal ID of the own terminal to the authentication server 230 (3).

  The authentication server 230 holds a registrant database 232a in which information related to the controller and information related to the control target are registered in advance. Here, the controller ID of the card 221 is registered in the registrant database 232a as information related to the controller, and the control terminal ID of the monitoring control terminal 240 is registered in the registrant database 232a as information related to the control target.

  If the authentication server 230 receives the control request including the controller ID and the control terminal ID from the monitoring control terminal 240, the authentication server 230 performs the controller verification based on the registrant database 232a. As a result of this collation, when it is determined that the control is appropriate, the authentication server 230 transmits the collation result to the monitoring control terminal 240 (4). This collation result may include the contents of control.

  When the monitoring control terminal 240 receives the verification result from the authentication server 230, the monitoring control terminal 240 controls the monitoring state of the door monitoring device 281 and the window monitoring device 282 (5). The door monitoring device 281 is a device that monitors attempts to illegally enter a door of a residence. The window monitoring device 282 is a device that monitors an unauthorized intrusion attempt to a residential window.

  In this way, the card 221 storing the controller ID is issued to the controller, the controller ID is read from the card 221 held by the controller, transmitted to the authentication server 230, and authentication is performed. Therefore, the resident can easily control the monitoring state of the door monitoring device 281 and the window monitoring device 282. For example, when the user goes out, the door monitoring device 281 and the window monitoring device 282 are set in a monitoring state by holding the card 221 over the reading terminal 210, and when the user goes home, the door monitoring device 281 and the window monitoring device are set over the reading terminal 210. 282 can be set to a non-monitoring state.

  Next, a system configuration of the facility management system according to the third embodiment will be described. FIG. 11 is a diagram illustrating a system configuration of the facility management system according to the third embodiment. As illustrated in FIG. 11, the facility management system according to the third embodiment includes a plurality of control objects, an authentication server 230, a service management device 250, and a plurality of guardian terminals 270. Further, the control target includes a card 221 and a monitoring control terminal 240, and a reading terminal 210, a door monitoring device 281 and a window monitoring device 282 are connected to the monitoring control terminal 240.

  The authentication server 230 is connected to the monitoring control terminal 240 and the guardian terminal 270 via a network. The authentication server 230 is connected to the service management device 250. The connection between the authentication server 230 and the service management apparatus 250 may also be a connection via a network.

  The authentication server 230 receives registration of the card 221 used for home security control and the monitoring control terminal 240 as a control destination from the monitoring control terminal 240 and the guardian terminal 270. When the authentication server 230 receives a control request including the controller ID and the control terminal ID from the monitoring control terminal 240, the authentication server 230 compares the controller ID and the control terminal ID with the registered information, so that the control request is received. It is determined whether or not it is appropriate. The authentication server 230 stores a control history when receiving a control request including the controller ID and the control terminal ID from the monitoring control terminal 240.

  Further, the authentication server 230 accepts browsing of the control history from the service management device 250 and the guardian terminal 270. The service management device 250 and the guardian terminal 270 that perform browsing are in a state in which necessary information is registered in advance in the authentication server and authentication for browsing is possible. When various services are charged, the authentication server 230 manages the charging information, and accepts browsing of the charging information from the service management apparatus 250 and the guardian terminal 270. For browsing from the service management device 250 or the guardian terminal 270, the range of information that can be browsed for each viewer can be set.

  The service management apparatus 250 is an apparatus for an administrator that manages a home security control service. The service management apparatus 250 can register in advance in the authentication server 230 and perform authentication, thereby browsing various kinds of information held in the authentication server 230 and collecting control history and billing information.

  The guardian terminal 270 is a terminal associated with the control destination. For example, when the control target is a residence where an elderly person lives, the control history can be confirmed from another place by registering the terminal of the related person as the guardian terminal 270. In addition, registration and billing of various information related to the control target can be performed from the guardian terminal 270.

  Next, the internal configuration of the authentication server 230 shown in FIG. 11 will be described. FIG. 12 is an internal configuration diagram showing an internal configuration of the authentication server 230 shown in FIG. As illustrated in FIG. 12, the authentication server 230 includes a communication unit 231, a storage unit 232, and a control unit 233.

  The communication unit 231 is a communication interface for communicating with the monitoring control terminal 240, the service management device 250, and the guardian terminal 270. The storage unit 232 is a storage device such as a hard disk device or a nonvolatile memory, and stores a registrant database 232a and a control history 232b.

  The registrant database 232a is a database that stores information related to a controller who performs control and information related to the monitoring control terminal 240 to be controlled. The control history 232b is data indicating a history of home security control.

  The control unit 233 is a control unit that totally controls the authentication server 230, and includes a controller registration unit 233a, a control target registration unit 233b, a verification processing unit 233c, a verification result notification unit 233d, a control history management unit 233e, and a browsing processing unit 233f. Have

  The controller registration unit 233a is a processing unit that performs processing for registering information related to a controller that performs control in the registrant database 232a. In addition, the control target registration unit 233b is a processing unit that performs processing for registering information on the monitoring control terminal 240 to be controlled in the registrant database 232a.

  The collation processing unit 233c is a processing unit that performs collation based on the registrant database 232a when a control request including a controller ID and a control terminal ID is received from the monitoring control terminal 240. The verification result notification unit 233d is a processing unit that transmits the verification result to the monitoring control terminal 240.

  The control history management unit 233e is a processing unit that updates the control history 232b when a control request including the controller ID and the control terminal ID is received from the monitoring control terminal 240. The browsing processing unit 233f authenticates the service management device 250 and the guardian terminal 270 when receiving access from the service management device 250 and the guardian terminal 270, and provides data such as the control history 232b when the authentication is successful. Is a processing unit.

  Next, data stored in the storage unit 232 illustrated in FIG. 12 will be described. FIG. 13 is an explanatory diagram for describing data stored in the storage unit 232 illustrated in FIG. 12. As illustrated in FIG. 13, the registrant database 232a includes controller data that is information related to a controller that performs control, and control target data that is information related to a control target.

  The controller data includes a device type and a controller ID. In this embodiment, the case where the controller ID is held in the card 221 is described as an example. However, the medium holding the controller ID is not limited to the card, and may be a tag or a portable terminal having an arbitrary shape. Good. The model type indicates the type of medium that holds the controller ID. The model type and the controller ID are transmitted to the authentication server 230 together with the control terminal ID at the time of authentication. At this time, the collation date may be further transmitted.

  The control target data includes device type, control terminal ID, contractor information, user information, and permission controller ID. The device type is the type of the monitoring control terminal 240. The control terminal ID is the ID of the monitoring control terminal 240.

  The contractor information is data indicating the name of the contractor, the telephone number, whether it is an individual or a corporation, and the like. The contractor may be a resident of a controlled residence, or may be another person such as a guardian or a corporation. The user information is data indicating the name of the resident of the residence to be controlled, a telephone number, whether it is an individual or a corporation, and the like.

  The permission controller ID is a controller ID registered in advance as a controller capable of controlling the control target. For example, in the case where the resident has a plurality of residences, the controller IDs for the resident can be registered.

  The control history 232b includes date and time, a controller ID, a control terminal ID, a verification result, and control contents. The date and time indicate the date and time when the control request is made, and the ID included in the control request is stored in the controller ID and the control terminal ID. The collation result indicates whether the collation is successful, and the control content indicates the content of the control performed based on the control request.

  Next, the internal configuration of the monitoring control terminal 240 shown in FIG. FIG. 14 is an internal configuration diagram showing an internal configuration of the monitoring control terminal 240 shown in FIG. As illustrated in FIG. 14, the monitoring control terminal 240 includes a communication unit 241, an operation unit 244, a display unit 245, a control unit 246, and a storage unit 247. The communication unit 241 is a communication interface for communicating with the reading terminal 210 and the authentication server 230.

  The operation unit 244 is a touch panel, a button, or the like that receives a resident's operation input. The display unit 245 is a liquid crystal display or the like for performing display output, and is used for displaying the collation result received from the authentication server 230. The storage unit 247 is a storage device such as a nonvolatile memory, and stores the control terminal ID 247a of the monitoring control terminal 240. The control terminal ID 247a is registered in advance in the authentication server 230.

  The control unit 246 is a control unit that totally controls the monitoring control terminal 240, and includes a reading processing unit 246a, a verification request unit 246b, a verification result reception unit 246c, a device control unit 246d, and an abnormal termination unit 246e.

  The reading processing unit 246a performs processing for acquiring the controller ID read by the reading terminal 210 from the card 221. When the reading processing unit 246a acquires the controller ID, the verification request unit 246b reads the control terminal ID 247a from the storage unit 247 and transmits a control request including the acquired controller ID and control terminal ID 247a to the authentication server 230. Is a processing unit.

  The verification result receiving unit 246 c is a processing unit that receives the verification result from the authentication server 230. When the verification result reception unit 246c receives the verification result, the device control unit 246d controls the operation of the door monitoring device 281 and the window monitoring device 282 based on the received verification result.

  The abnormal termination unit 246e sends a control request to the authentication server 230 by the verification request unit 246b, and if the verification result is not received within a predetermined time, the abnormal end unit 246e uses an indicator or the like provided on the reading terminal 210 to Notify the timeout. This is because it is impossible to know whether the control has been performed unless a collation result is obtained indefinitely due to a communication abnormality or the like.

  In addition, when the collation result received from the authentication server 230 is a collation failure, the abnormal end unit 246e notifies the collation failure using an indicator or the like provided in the reading terminal 210. Thus, by notifying the collation failure, it is possible to cope with re-execution of the control request.

  Next, the operation of the facility management system shown in FIG. 11 will be described. FIG. 15 is a flowchart for explaining the operation of the facility management system shown in FIG. As shown in FIG. 15, the monitoring control terminal 240 determines whether or not the reading terminal 210 has read the controller ID from the card 221 (step S301), and if it has not read the controller ID (step S301; No). A standby operation is performed to determine whether or not the controller ID has been read again.

  When the controller ID is read (step S301; Yes), the monitoring control terminal 240 transmits a control request including the read controller ID and the control terminal ID of the own terminal to the authentication server 230 (step S302). ). And it is determined whether the collation result was received from the authentication server 230 (step S303).

  If the collation result has not been received (step S303; No), the monitoring control terminal 240 determines whether or not the abnormal termination condition is satisfied (step S304). As a condition for abnormal termination, a case where a predetermined time has elapsed since the transmission of the verification request, a case where occurrence of a communication abnormality, or the like can be used.

  If the condition for abnormal termination is not satisfied (step S304; No), the monitoring control terminal 240 proceeds to step S303 and determines whether or not a collation result has been received. If the abnormal termination condition is satisfied (step S304; Yes), the abnormal termination is notified (step S305), and the process is terminated.

  On the other hand, when the verification result is received from the authentication server 230 (step S303; Yes), the monitoring control terminal 240 controls the monitoring state of the door monitoring device 281 and the window monitoring device 282, etc. (step S306), and performs processing. finish.

  The authentication server 230 determines whether or not a control request including the controller ID and the control terminal ID has been received from the monitoring control terminal 240 (step S401). If the control request has not been received (step S401; No), A standby operation for determining whether or not the control request is received again is performed.

  When the authentication server 230 receives the control request (step S401; Yes), the authentication server 230 performs a collation process (step S402). This verification process is a process for verifying whether or not the received controller ID and control terminal ID are registered in the registrant database 232a. Both the controller ID and the control terminal ID are registered in the registrant database 232a. If the verification is successful, the control request is authenticated as an appropriate control request. If either the controller ID or the control terminal ID is not registered and verification fails, the authentication server 230 determines that the control request is not appropriate.

  The authentication server 230 transmits the result of the verification process to the monitoring control terminal 240 (step S403), updates the control history 232b (step S404), and ends the process.

  As described above, the facility management system according to the third embodiment issues the card 221 storing the controller ID to the controller, reads the controller ID from the card 221 held by the controller, and authenticates the server. 230, it is possible to determine whether or not it is an appropriate control request by performing authentication, so the resident can easily control the monitoring state of the door monitoring device 281 and the window monitoring device 282, etc. Can do.

  Further, the control history can be viewed from the service management device 250, the guardian terminal 270, and the like, and an unauthorized control attempt can be detected by counting the control history.

  In the first to third embodiments, the facility management system for residences has been described as an example. However, the present invention is not limited to residential use, and is used for visit management and security management in any facility such as an office. can do.

  As described above, the facility management system and the facility management method according to the present invention are suitable for improving convenience related to visitor identity guarantee and security operation switching.

10, 210 Reading terminal 21, 121, 221 Card 30, 230 Authentication server 31, 41, 231, 241 Communication unit 32a, 232a Registrant database 32, 47, 147, 232, 247 Storage unit 32b Visit history 33, 46, 146 233, 246 Control unit 33a Visitor registration unit 33b Visit destination registration unit 33c, 233c Verification processing unit 33d, 233d Verification result notification unit 33e Visit history management unit 33f, 233f Viewing processing unit 40 Indoor terminal 42 Microphone 43 Speaker 44, 144 244 Operation unit 45, 145, 245 Display unit 46a, 246a Reading processing unit 46b, 146b, 246b Verification request unit 46c, 146c, 246c Verification result receiving unit 46d, 146d Verification result notification unit 46e, 146e Visitor correspondence processing unit 46f 146f, 46e abnormal end portion 47a indoor terminal ID
50, 250 Service management device 60 Visitor registration center 70, 270 Guardian terminal 111 Interphone outer terminal 112 Interphone inner terminal 140 Mobile terminal 141 Wireless communication unit 142 Camera 146a Image recognition unit 147a Mobile terminal ID
232b Control history 233a Controller registration unit 233b Control target registration unit 233e Control history management unit 240 Monitoring control terminal 246d Device control unit 247a Control terminal ID
281 Door monitoring device 282 Window monitoring device

Claims (8)

A facility management system for managing facilities,
Portability identification information holding means carried by a visitor visiting the facility and holding visitor identification information for identifying the visitor ;
Identification information reading means for reading the visitor identification information from the identification information holding means located outside the facility;
Identification information transmitting means for transmitting the visitor identification information read by the identification information reading means to an authentication center;
Authentication means for performing authentication processing of the visitor based on the visitor identification information transmitted to the authentication center;
An authentication result using terminal that is operable inside the facility based on the authentication result by the authentication means, and that notifies the person in the facility of the authentication result of the visitor ,
A visit history management means for managing, as a visit history, location information of a facility visited by the visitor and whether or not the purpose of the visit by the visitor has been achieved;
The facility management system characterized by comprising. It said identification information reading means, wherein provided on the outside of the facility, the facility management system according to claim 1, characterized in that reading the identification information before Symbol visitor identification information Ri by the short-range wireless communication from the holding means . The facility management system according to claim 1 , wherein the visitor identification information is written on the identification information holding means, and the identification information reading means reads the written visitor identification information by image recognition. . The said authentication means outputs at least any one among the said visitor's affiliation, a visitor's name, a date of birth, an image, and an audio | voice as the said authentication result, The Claim 1 or 2 characterized by the above-mentioned Facility management system. The facility management system according to claim 4 , further comprising output range setting means for individually setting information included in the authentication result by the authentication means for each visitor. Based on the previous SL access history, facility management system according to any one of claims 1 to 5, characterized in that the visit further comprising a determining hands stage whether it is appropriate. Claim 1, wherein said information acquired for property state authenticates the authorized information acquirer, further comprising information providing means for providing information authentication result by said authentication means to said information acquirer 6 facility management system according to any one of. A facility management method for managing facilities,
An identification information reading step of reading visitor identification information for identifying a visitor visiting the facility from identification information holding means located outside the facility;
An identification information transmission step of transmitting the visitor identification information read by the identification information reading step to an authentication center;
An authentication step of performing an authentication process of the visitor based on the visitor identification information transmitted to the authentication center;
An authentication result transmitting step for transmitting an authentication result by the authentication step to an authentication result using terminal operable within the facility ;
A facility management step comprising: a visit history management step for managing, as a visit history, location information of the facility visited by the visitor and whether or not the purpose of the visit by the visitor has been achieved. Method.

Images