Reporting system

Abstract

To enable a concerned party to know a situation when a specific user uses an elevator for the specific user.SOLUTION: A reporting system comprises information management data, a face information acquisition part, and a first reporting processing part. A state where face information of an object person and his / her contact address are associated with each other, is stored in the information management data for each object person. The face information acquisition part acquires face information of each user embarking on a ca of an elevator. The first reporting processing part reports a situation of the user to the contact address associated with the matched face information for each object person whose face information acquired by the face information acquisition part among the users embarking on the car matches any of the face information in the information management data.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a notification technique applicable to elevators. [Background technology]

[0002] An emergency call button (such as an intercom) is provided in the elevator car so that a monitoring center can be notified (see, for example, Patent Document 1). Therefore, even if the elevator makes an emergency stop and the user is trapped inside the car, the user can call for rescue from inside the car by notifying the monitoring center using the emergency call button. Furthermore, if the user has a smartphone, the user can notify relevant parties (family, friends, company, etc.) by smartphone that he or she is trapped inside the car. Furthermore, even if the user does not have a smartphone, if the user has stored the contact information of the relevant parties, the user can request the monitor to pass on a message to the contact information when notifying the monitoring center. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2009-202998 A Summary of the Invention [Problem to be solved by the invention]

[0004] On the other hand, if a user is trapped inside a train car, does not have a smartphone and has not memorized the contact information of relevant parties (family, friends, work, etc.), the user may be able to use the emergency call button to notify the monitoring center, but will not be able to contact those involved, which will cause them concern.

[0005] SUMMARY OF THE PRESENT EMBODIMENT An object of the present invention is to enable related parties to know the circumstances under which a specific user used an elevator. [Means for solving the problem]

[0006] The reporting system according to the present invention includes information management data, a face information acquisition unit, and a first report processing unit (aspect 1). Here, the information management data stores face information and contact information for each target person in a state where the face information and contact information are associated with each other. The face information acquisition unit acquires face information of each user who is in the elevator car. The first report processing unit reports the status of each target person who is in the car and whose face information acquired by the face information acquisition unit matches any of the face information in the information management data to the contact information associated with the matching face information.

[0007] According to the above-mentioned aspect 1, by registering the face information and contact information of the target person in the information management data, when each target person uses an elevator, it becomes possible to report the situation of the target person to the contact related person (including the case of reporting the use of the elevator). Examples of related persons include the case where the related person is the family member (guardian, etc.) of the target person, and the case where the related person is the friend, company, cram school, school, etc. of the target person. According to the above-mentioned reporting to the related person, each time the target person uses an elevator, the related person can know that the target person has used the elevator by receiving the report. Furthermore, when some event occurs to the target person while using the elevator, even in a case where it was difficult for the related person to know the situation at that time in the past (when the target person does not have a smartphone and does not remember the contact information of the related person, and therefore there is no means of contacting the related person), according to the above-mentioned aspect 1, the related person can know the situation of the target person by receiving the report.

[0008] In the reporting system according to the above aspect 1, when a user is locked in an elevator, if there is a target user among the users locked in the elevator whose facial information acquired by the facial information acquisition unit matches any of the facial information in the information management data, the first reporting processing unit may report the occurrence of the lock-in to the contact information associated with the facial information in the information management data for each target user (aspect 2).

[0009] In the case where a subject is locked inside a car, it would have been difficult for relevant parties to know that the lock-in had occurred in the past. However, according to the above aspect 2, the relevant parties can know that the subject is locked inside the car by receiving a report.

[0010] The reporting system according to the present invention may include an API, a face information acquisition unit, and a first report processing unit (Aspect 3). Here, when the API receives face information of each elevator user, if the face information matches the face information of a target person, the API returns a contact address associated with the face information. The face information acquisition unit acquires face information of each user who is in the elevator car. The first report processing unit transmits the face information of each user acquired by the face information acquisition unit to the API, and when a contact address is returned from the API as a result, the first report processing unit reports the status of the user to the contact address.

[0011] According to the above aspect 3, even if information management data is not stored, contact information can be obtained from an external device (such as a server) through API integration, making it possible to send notifications to relevant parties in the same way as in the above aspect 1.

[0012] In the reporting system according to the above aspect 3, when a user is trapped in a car, the first reporting processing unit may send facial information of each user trapped in the car to an API, and when a contact information is returned from the API as a result, report the occurrence of the trapping to the contact information (aspect 4).

[0013] According to the above-mentioned fourth aspect, it becomes possible to give the same notification as in the above-mentioned second aspect to the relevant persons.

[0014] The reporting system according to the above-mentioned aspect 4 may have the following configuration (aspect 5). Specifically, when a user is trapped in a car, the first report processing unit may obtain, from the elevator in which the trapping occurred, the destination floor registered in the car at that time. Then, the first report processing unit may transmit the face information of each user acquired by the face information acquisition unit to an API that can link with an external device managed by a resident of the destination floor, among the APIs, and when a contact address is returned from the API as a result, the first report processing unit may report the occurrence of the trapping to the contact address.

[0015] According to the above-mentioned aspect 5, if a user is trapped in a car, it becomes possible to notify the contact points likely to be related to each user at that time of the occurrence of the trapping.

[0016] In the notification system according to any of the above aspects 2, 4, and 5, the first notification processing unit may, after notifying a contact point that a person is trapped, instruct the elevator in which the person is trapped to inform the user who is trapped in the elevator car that the contact point has been notified (aspect 6).

[0017] According to the above-mentioned aspect 6, a user trapped in the elevator can know that his / her situation (being trapped in the elevator) has been reported to the relevant parties by receiving guidance from the elevator. This makes it possible to give the user in the elevator a sense of security that the relevant parties are aware of his / her situation.

[0018] The notification system according to any one of the above aspects 2 and 4 to 6 may further include a second notification processor (aspect 7). Here, when the first notification processor notifies a contact point that a user has been trapped, and then the second notification processor receives a rescue completion signal notifying that the rescue of the user from the trapping has been completed, the second notification processor notifies the same contact point that the rescue of the user from the trapping has been completed.

[0019] According to the above aspect 7, in the event that a subject becomes trapped inside a car, the relevant parties will be notified of the occurrence of the trapping, and then will receive a further report, thereby being able to know that the subject has been rescued from the trapping. Effect of the Invention

[0020] According to the present invention, it becomes possible for related parties to know the circumstances under which a specific user (target person) used an elevator. [Brief description of the drawings]

[0021] [Figure 1] 1 is a conceptual diagram illustrating an elevator to which a reporting system according to an embodiment is applied. [Diagram 2] 2A and 2B are conceptual diagrams illustrating information management data and report management data used in the embodiment. [Diagram 3] 4 is a flowchart showing a first reporting process executed in the embodiment. [Figure 4] 10 is a flowchart showing a second notification process executed in the embodiment. [Diagram 5] 13 is a flowchart showing a first reporting process executed in a second modified example. [Figure 6] FIG. 13 is a conceptual diagram illustrating an elevator to which a reporting system according to a third modified example is applied. [Figure 7] 13 is a flowchart showing a first reporting process executed in a third modified example. [Figure 8]13 is a flowchart showing a first reporting process executed in a fourth modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] [1] Implementation Example 1 is a conceptual diagram illustrating an elevator 1 to which a reporting system according to an embodiment is applied. As shown in this diagram, an emergency call button 11 is usually provided in a car G of the elevator 1 so that the elevator 1 can report to a monitoring center 2. The elevator 1 and the monitoring center 2 are also connected to each other via a network so that information communication (including telephone calls) between them is possible.

[0023] Therefore, even if the elevator 1 makes an emergency stop and the user is trapped inside the car G, the user can request rescue from inside the car G by reporting to the monitoring center 2 using the emergency call button 11. In addition, if the user has a smartphone, the user can contact relevant parties (family, friends, company, etc.) by smartphone to inform them that he or she is trapped inside the car G. Furthermore, even if the user does not have a smartphone, if the user has stored the contact information (such as telephone numbers) of the relevant parties, the user can request the monitor to pass on a message to the contact information when reporting to the monitoring center 2.

[0024] On the other hand, if a user is trapped inside the elevator G, and that user does not have a smartphone and has not memorized the contact information of relevant parties (family, friends, work, etc.), then although the user can use the emergency call button 11 to notify the monitoring center 2, they will not be able to contact the relevant parties, which will cause them concern.

[0025] Therefore, in this embodiment, in order to allow relevant parties to be notified of the occurrence of entrapment even in such cases, a reporting system that makes this possible is composed of a face information acquisition unit 12 installed in the car G of the elevator 1 and a control device 20 installed in the monitoring center 2 (see Figure 1).

[0026] The face information acquisition unit 12 is a part configured with an imaging device such as a camera, and acquires face information Pf of each user who gets on the car G.

[0027] Specifically, the face information acquisition unit 12 captures an image of the face of a user who is riding in the elevator G by photographing the inside of the elevator G. Then, the face information acquisition unit 12 performs image processing on the acquired image to extract face information Pf (such as facial features) of each user appearing in the image.

[0028] The face information acquisition unit 12 may acquire face information Pf of each user only when a user is trapped in the car G by a command from the control device 20 of the monitoring center 2. Furthermore, when such a trapping occurs, the elevator 1 may provide the following guidance to the user in the car G through the communication device 13 and the display device 14 (see FIG. 1) in the car G in response to a command from the control device 20 of the monitoring center 2. Specifically, the elevator 1 may guide the user in the car G to turn his / her face toward the face information acquisition unit 12 (such as a camera) so that the face information Pf of each user trapped in the car G can be accurately acquired by the face information acquisition unit 12.

[0029] The facial information Pf of each user acquired by the facial information acquisition unit 12 is used for control processing (specifically, first reporting processing) performed by the control device 20 of the monitoring center 2, which will be described later. Therefore, when the facial information acquisition unit 12 acquires the facial information Pf of each user in the car G, the facial information Pf is transmitted to the monitoring center 2 through the control device 10 of the elevator 1. At this time, the control device 10 of the elevator 1 transmits to the monitoring center 2, together with the facial information Pf, identification information Pe of the elevator 1 that it controls, so that the control device 20 of the monitoring center 2 recognizes which elevator 1 is the sender of the facial information Pf.

[0030] The extraction of the face information Pf from the image captured inside the car G may be executed by the control device 20 of the monitoring center 2. In that case, the control device 10 of the elevator 1 transmits the image captured inside the car G by the face information acquisition unit 12 to the monitoring center 2.

[0031] In the following, for the sake of simplicity, it is assumed that the image acquired by the facial information acquisition unit 12 always includes the face of each user in the elevator G, and that facial information Pf of that user is always extracted from the image.

[0032] The control device 20 includes a storage unit 21 and a control unit 22 (see FIG. 1). The storage unit 21 is a part configured with a storage device such as a ROM or a RAM. The control unit 22 is a part configured with a processing device such as a CPU or an MPU.

[0033] Information management data Dp and report management data Dq are stored in the storage unit 21. Figures 2(A) and 2(B) are conceptual diagrams illustrating the information management data Dp and report management data Dq used in this embodiment, respectively.

[0034] In the information management data Dp (see FIG. 2(A)), the facial information Pf and contact information Ph of each subject are stored in a mutually associated state. Specifically, the subject or a related person registers the facial information Pf and contact information Ph of the subject in advance, and the information is stored in the information management data Dp in a mutually associated state. Here, a related person is a person who has a relationship with the subject that requires knowledge of the subject's situation, such as a manager who manages the subject (such as a guardian for a child or a family member of an elderly person). The contact information Ph associated with the facial information Pf is the contact information of such a related person, and is used to notify the related person of the entrapment when the subject is locked in the car G.

[0035] In the example of FIG. 2(A), a case is shown in which an e-mail address of a related person is registered as the contact point Ph. As a more specific example, the contact point Ph is an e-mail address that can receive e-mails on a mobile terminal device 3 (such as a smartphone; see FIG. 1) carried by the related person. Note that the contact point Ph is not limited to an e-mail address, and may be a telephone number, an SNS account, or the like, as long as it is possible to contact the related person. Furthermore, the related person may be the target person's friend, company, cram school, school, etc.

[0036] Furthermore, in the information management data Dp, information on each target person to be notified of when a report is sent to relevant parties may be registered and stored in advance together with face information Pf and contact information Ph. The example of Fig. 2(A) shows a case where the target person's name is registered in advance together with face information Pf and contact information Ph and stored in the information management data Dp.

[0037] Such information management data Dp does not need to be stored in the storage unit 21 for each elevator 1 to be monitored, but can be stored in the storage unit 21 as one piece of data common to those elevators 1.

[0038] The report management data Dq (see FIG. 2(B)) stores information that enables a second report to be sent to the contact Ph stored in the information management data Dp when the rescue of the trapped user is completed, in order to inform the contact Ph. Specifically, when a user is trapped in a car G of any of the elevators 1 to be monitored, if there is a target person preregistered in the information management data Dp among the users trapped in the car G, a report is sent to the contact Ph for each target person, and the contact Ph is stored in the report management data Dq in a state associated with the identification information Pe of the elevator 1 in which the trapping occurred. Note that the example of FIG. 2(B) shows a case in which, in addition to the contact Ph, the name of the target person and the report date and time are stored in association with the identification information Pe.

[0039] When a user is locked in the elevator G, and there is a target user whose face information Pf acquired by the face information acquisition unit 12 matches any of the face information Pf in the information management data Dp among the users locked in the elevator G, the control unit 22 notifies the contact Ph associated with the face information Pf in the information management data Dp of the lock-in for each target user (first notification process). Furthermore, after notifying the contact Ph of the lock-in, when the control unit 22 receives a rescue completion signal Sy notifying that the user has been rescued from the lock-in, the control unit 22 notifies the same contact Ph as the contact Ph that the user has been rescued from the lock-in that the user has been rescued from the lock-in (second notification process). The first and second notification processes will be described in detail later.

[0040] In this embodiment, the first notification process and the second notification process are executed by a first notification processing section 221 and a second notification processing section 222 constructed in the control section 22 (see FIG. 1). Specifically, these processing sections are configured as software by having the control section 22 execute a program. Such a program may be stored in a portable storage medium (e.g., a flash memory or the like) in a readable state, read from the storage medium and installed and stored in the storage section 21 of the control device 20, or may be stored in another server or the like in a downloadable state, downloaded from the server and installed and stored in the storage section 21. The above-mentioned processing sections may be configured as hardware by constructing a circuit in the control device 20.

[0041] 3 is a flow chart showing the first notification process executed by the control device 20 of the monitoring center 2 in this embodiment. This first notification process is started when a user is locked into a car G of any of the elevators 1 to be monitored. Specifically, the first notification process is started when the control device 20 of the monitoring center 2 receives a lock-in occurrence signal Sx notifying that a lock-in has occurred, and identification information Pe of the elevator 1 in which the lock-in has occurred. Hereinafter, these pieces of information will be collectively referred to as "received information Pr1."

[0042] As an example, the control device 20 receives the trapped-in occurrence signal Sx and the identification information Pe in the following manner. First, when the elevator 1 is stopped in an emergency and a user in the car G notifies the monitoring center 2 using the emergency call button 11, the identification information Pe of the elevator 1 that has been stopped in an emergency is transmitted to the monitoring center 2. The supervisor who receives the notification talks to the user in the car G and attempts to move the car G to the nearest floor by remotely operating the elevator 1 identified by the identification information Pe transmitted at that time. If the remote operation to move to the nearest floor is successful, the user in the car G is rescued in a short time after the emergency stop. On the other hand, if the rescue by such remote operation fails, the user will be trapped in the car G. In that case, the supervisor presses a button or the like that notifies that the user is trapped, and the trapped-in occurrence signal Sx is output. Then, the trapped-in occurrence signal Sx is received by the control device 20 together with the identification information Pe of the elevator 1 in which the user is trapped.

[0043] In addition, the series of steps performed by the monitoring center 2 during an emergency stop of the elevator 1, from receiving the identification information Pe to outputting the entrapment occurrence signal Sx, is not limited to being performed by the operation of a monitor, but may be appropriately changed to an automated one by executing a program in the control device 20.

[0044] When the first notification process is started, the control device 20 uses the identification information Pe in the received information Pr1 to identify the elevator 1 in which the entrapment has occurred, and acquires face information Pf of each user trapped in the car G of the elevator 1 from the face information acquisition unit 12 via the control device 10 of the elevator 1 (step S11). In this step S11, the control device 20 acquires face information Pf from all users trapped in the car G.

[0045] At this time, the control device 20 may instruct the control device 10 of the elevator 1 to provide the following guidance to users in the car G through the communication device 13 and the display device 14 (see FIG. 1) in the car G. Specifically, the control device 20 may instruct the control device 10 of the elevator 1 to guide users in the car G to turn their faces toward the face information acquisition unit 12 (such as a camera) so that the face information Pf of each user trapped in the car G can be accurately acquired by the face information acquisition unit 12.

[0046] Next, the control device 20 performs face authentication for each user trapped in the elevator G using the face information Pf of the user acquired in step S11 (step S12). As a result, the control device 20 extracts targets who have been pre-registered in the information management data Dp from among the users trapped in the elevator G. Specifically, the control device 20 compares the face information Pf acquired in step S11 with the face information Pf stored in the information management data Dp one by one. Then, the control device 20 extracts users whose face information Pf matches in the comparison (i.e., users whose face authentication has been successful) as targets who have been pre-registered in the information management data Dp.

[0047] Thereafter, the control device 20 judges whether or not there is a user (a target person pre-registered in the information management data Dp) whose face has been successfully authenticated in step S12 among the users locked in the car G (step S13). Specifically, the control device 20 judges whether or not a target person pre-registered has been extracted by executing step S12.

[0048] When the control device 20 determines in step S13 that "there was a user whose face was successfully authenticated (Yes)," it extracts, for each user whose face was successfully authenticated, the contact information Ph (contact information Ph of related parties) associated with the face information Pf of the user in the information management data Dp (step S14). Then, the control device 20 notifies the extracted contact information Ph that a person has been locked in the car G (step S15).

[0049] As a result, when a subject who has been preregistered in the information management data Dp is locked in a car G, the fact that the subject has been locked in the car G can be reported to the contact information Ph of the relevant person registered in the information management data Dp. Therefore, when a user is locked in a car G, even in a case where it would have been difficult for the relevant person to know that the user has been locked in the car G in the past, the relevant person can know that the subject who has been preregistered in the information management data Dp is locked in the car G by receiving the report.

[0050] In step S14, the control device 20 may extract, for each user whose face has been successfully authenticated, other information (such as name (see FIG. 2(A))) associated with the face information Pf of the user in the information management data Dp, together with the contact information Ph. In step S15, the control device 20 may notify the contact information Ph extracted in step S14 that a person has been locked in the car G, and may transmit the other information (such as name) extracted in step S14 to the contact information Ph. The control device 20 may further transmit information on the location of the elevator 1 identified by the identification information Pe in the received information Pr1 (such as the building name) to the contact information Ph extracted in step S14. This allows the relevant parties to more clearly recognize who is locked in and where they are locked in.

[0051] After step S15, the control device 20 stores the contact information Ph extracted in step S14 for each user who has been successfully face-authenticated in step S12 in the notification management data Dq in association with the identification information Pe in the received information Pr1 (step S16). The information stored in the notification management data Dq is used in the second notification process described below.

[0052] On the other hand, if the control device 20 determines in step S13 that "there was no user whose face was successfully authenticated (No)", it ends the first notification process without performing the above-mentioned steps S14 to S16.

[0053] 4 is a flow chart showing the second notification process executed by the control device 20 of the monitoring center 2 in this embodiment. This second notification process is started when rescue of a user from the trapped-in elevator 1 is completed. Specifically, the second notification process is started when the control device 20 of the monitoring center 2 receives a rescue completion signal Sy notifying that rescue of the user from the trapped-in elevator has been completed, and identification information Pe of the elevator 1 in which the rescue was performed. Hereinafter, these pieces of information will be collectively referred to as "received information Pr2."

[0054] As an example, the control device 20 receives the rescue completion signal Sy and the identification information Pe in the following manner. When a person is trapped in the car G of the elevator 1, a maintenance worker receives a call from the monitoring center 2, heads to the elevator 1 where the trapping occurred, and rescues the user from the trapping. After that, the maintenance worker transmits the rescue completion signal Sy and the identification information Pe of the elevator 1 where the rescue was performed from a terminal device carried by the maintenance worker to the monitoring center 2 to inform the monitoring center 2 that the rescue has been completed. Then, the rescue completion signal Sy is received by the control device 20 together with the identification information Pe of the elevator 1 where the rescue was performed.

[0055] When the second notification process is started, the control device 20 uses the identification information Pe in the received information Pr2 to extract from the notification management data Dq the contact Ph that notified relevant parties (step S15 in Figure 3) when a person was trapped in the elevator 1 identified by the identification information Pe (step S21).

[0056] After that, the control device 20 judges whether or not there was any contact information Ph that could be extracted in step S21 (step S22). Based on this judgment, the control device 20 can judge whether or not there was a target person who was pre-registered in the information management data Dp among the users rescued from the confinement (in other words, a user who was notified to the relevant parties that he or she was confined).

[0057] Specifically, when the control device 20 determines in step S22 that "there was a contact point Ph that could be extracted (Yes)," it can determine that among the users rescued from confinement, there was a target person who was preregistered in the information management data Dp (in other words, a user who was notified to the relevant parties that the confinement had occurred). In this case, the control device 20 notifies the contact points Ph extracted in step S21 that the rescue from confinement has been completed (step S23), in order to further inform the relevant parties who learned of the confinement through the notification that the target person had been rescued from confinement.

[0058] Thereafter, the control device 20 deletes the contact Ph to which the notification was made in step S15 and all information associated with it from the notification management data Dq (step S24).

[0059] On the other hand, if the control device 20 determines in step S22 that "there was no contact information Ph that could be extracted (No)", then it can be determined that among the users rescued from being trapped, there was no target person who had been preregistered in the information management data Dp (in other words, a user who had been notified to relevant parties that they had been trapped). In this case, the control device 20 ends the second notification process without performing the above-mentioned steps S23 and S24.

[0060] As a result, for a subject who has been preregistered in the information management data Dp, in the event that he or she is locked in the car G, it is possible to notify the relevant persons registered in the information management data Dp of the completion of the rescue when the rescue from the lock-in is completed after notifying the relevant persons. Therefore, after receiving the notification that the lock-in has occurred, the relevant persons can know that the subject has been rescued from the lock-in by receiving a further notification.

[0061] In this way, according to the reporting system of the present embodiment, by pre-registering the face information Pf and the contact information Ph of the target person in the information management data Dp, when each target person uses the elevator 1 (in this embodiment, when the target person is locked in during use), it is possible to report the situation of the target person to the relevant person in the contact information Ph. Therefore, for a specific user (a target person pre-registered in the information management data Dp), the relevant person can know the situation when the user uses the elevator 1. Specifically, when some event occurs to the target person while using the elevator 1, even in a case where it was difficult for the relevant person to know the situation at that time in the past (when the target person does not have a smartphone and does not remember the contact information of the relevant person, and therefore has no means of contacting the relevant person), according to the reporting system of the present embodiment, the relevant person can know the situation of the target person by receiving a report.

[0062] [2] Variations [2-1] First modified example In the above-described embodiment, the reporting system is not limited to reporting when a person is trapped inside the elevator car G, but can also be applied to reporting to relevant parties (registered contacts Ph) that a person who has been pre-registered in the information management data Dp has used the elevator 1 (specifically, when boarding the elevator car G) (the usage history of the elevator 1).

[0063] According to the first variant, each time a subject who has been pre-registered in the information management data Dp uses elevator 1, relevant parties can receive a report and become aware that the subject has used elevator 1.

[0064] The reporting system of the first modification can be used for such purposes as contacting a parent when a child uses the elevator 1 (for example, for a parent to confirm that a child has gone to school or cram school as scheduled, or has returned from school or cram school). The reporting system of the first modification can also be used for such purposes as for a family member to confirm that an elderly person has left at the scheduled time when they need to go to the hospital. In this way, the reporting system of the first modification can also be used for such purposes as for related parties to confirm the behavioral history of a target person.

[0065] [2-2] Second variant 5 is a flow chart showing the first notification process executed by the control device 20 of the monitoring center 2 in the second modified example. Here, the first modified example is a modified example of the embodiment described above. In this modified example, after sending a notification to the contact point Ph in step S15, the control device 20 instructs the elevator 1 identified by the identification information Pe in the received information Pr1 to inform the user in the car G where the entrapment has occurred that the notification has been sent to the contact point Ph through the communication device 13, the display device 14, or a speaker (not shown) installed in the car G (step S30).

[0066] According to the second modification, a user trapped in the car G can know that his / her situation (being trapped in the car G) has been reported to the relevant parties by receiving guidance from the elevator 1. This makes it possible to give the user in the car G a sense of security that the relevant parties are aware of his / her situation.

[0067] [2-3] Third variant In any of the above-described embodiments, the first variant, and the second variant, the reporting system may obtain the contact information Ph from the cloud through API integration instead of extracting the contact information Ph from the information management data Dp stored in the memory unit 21 provided in the control device 20 of the monitoring center 2.

[0068] FIG. 6 is a conceptual diagram illustrating an elevator 1 to which a reporting system according to a third modified example is applied. As shown in this diagram, the reporting system may include an API 4 instead of the information management data Dp. Here, the API 4 is an interface that links the control device 20 of the monitoring center 2 with an external device 5 on the cloud (such as a server managed by a school, a cram school, or a government office). When the API 4 receives face information Pf of each user of the elevator 1 from the control device 20 and the face information Pf matches face information Pf of a target person preregistered in the external device 5, the API 4 returns to the control device 20 the contact information Ph associated with the face information Pf in the external device 5.

[0069] 7 is a flowchart showing the first reporting process executed by the control device 20 of the monitoring center 2 in the third modified example. In this modified example, the control device 20 acquires face information Pf of each user in the car G in step S11, and then transmits the face information Pf to the API 4 (step S31).

[0070] When the API 4 receives face information Pf from the control device 20 (step S41), the API 4 causes the external device 5 linked via the API 4 to execute face authentication using the face information Pf and extract the contact information Ph if the face authentication is successful. Then, when the external device 5 succeeds in face authentication and can extract the contact information Ph, the API 4 receives the contact information Ph from the external device 5 and returns the contact information Ph to the control device 20 (step S42). On the other hand, when the external device 5 fails in face authentication, the API 4 returns an error signal Sz to the control device 20 (step S42).

[0071] After step S31, when there is a reply from the API 4 (receiving information from the API 4; step S32), the control device 20 judges whether the received information is a contact point Ph or an error signal Sz (step S33). If the control device 20 judges in step S33 that the information is a "contact point Ph," it sends a report to the contact point Ph (step S15) and stores the information in the report management data Dq (step S16). On the other hand, if the control device 20 judges in step S33 that the information is an "error signal Sz," it ends the first report process without performing steps S15 and S16.

[0072] According to the third variant, even if the control device 20 does not have information management data Dp, it can obtain contact information Ph from an external device 5 (such as a server) through API integration, making it possible to send notifications to relevant parties in the same manner as in the above-mentioned embodiment and the first variant.

[0073] The external device 5 is not limited to a server managed by a school, a cram school, a government office, etc., but may be a server on a cloud where personal schedule management data is stored. In this case, the control device 20 can obtain the contacts Ph extracted from the personal schedule management data by API linkage.

[0074] [2-4] Fourth variant 8 is a flowchart showing the first reporting process executed by the control device 20 of the monitoring center 2 in the fourth modified example. Here, the fourth modified example is a further modified example of the above-mentioned third modified example.

[0075] In this modified example, after acquiring the facial information Pf in step S11, the control device 20 acquires the destination floor Fd (registered destination floor Fd) registered at that time in the elevator G where the entrapment occurred from the elevator 1 identified by the identification information Pe in the received information Pr1 in order to know the destination floor Fd of the user trapped in the elevator G (step S40).

[0076] In the subsequent step S31, the control device 20 transmits the facial information Pf acquired in step S11 to one of the multiple API 4 that can link with an external device 5 managed by a resident of the destination floor Fd acquired in step S40 (a tenant or company such as a sports club, qualification school, English conversation school, etc.).

[0077] When the API4 receives face information Pf from the control device 20 (step S41), the API4 causes the external device 5 linked via the API4 to execute face authentication using the face information Pf and extract the contact information Ph when the face authentication is successful. When the external device 5 has face information Pf that has been successfully authenticated as a result of responding to a command from the API4, the API4 extracts the contact information Ph associated with the face information Pf and passes it to the API4. At this time, the external device 5 may pass the reception or window of the company or tenant that manages the external device 5 to the API4 as the contact information Ph. Thereafter, the API4 receives the contact information Ph from the external device 5 and returns the contact information Ph to the control device 20 (step S42). On the other hand, when the external device 5 fails in face authentication, the API4 returns an error signal Sz to the control device 20 (step S42).

[0078] According to the fourth modified example, if a user is locked inside the car G, it becomes possible to notify the contact Ph that is likely to be related to each user at that time of the lock-in occurrence.

[0079] The above-mentioned embodiments and the description of the modifications should be considered as illustrative in all respects and not restrictive. The scope of the present invention is indicated by the claims, not by the above-mentioned embodiments and modifications. Furthermore, the scope of the present invention is intended to include all modifications within the meaning and scope of the claims.

[0080] Furthermore, from the above-mentioned embodiment and modified examples, the subject of the invention is not limited to the reporting system, but may be extracted individually or partially from devices constituting the reporting system, control processes and programs executed by the reporting system, etc. Furthermore, a part or the whole of the overall configuration including the elevator 1 to which the reporting system is applied may be extracted as the subject of the invention. [Explanation of symbols]

[0081] 1. Elevator 2. Monitoring Center 3. Mobile terminal devices 4. API 5 External device G Car 10 Control device 11 Emergency call button 12 Face information acquisition unit 13 Telephone device 14 Display device 20 Control device 21 Memory section 22 Control section Dp Information Management Data Dq Report management data Fd Destination floor Pe Identification Information Pf Face information Ph Contact Sx Confinement occurrence signal Sy rescue completion signal Sz Error signal 221 First Report Processing Department 222 2nd Report Processing Department Pr1, Pr2 received information

Claims

1. information management data in which face information and contact information of each subject are associated with each other; A face information acquisition unit that acquires face information of each user who gets into the elevator car; a first notification processing unit that notifies the contact point associated with the matching face information of each target person among the users whose face information acquired by the face information acquisition unit matches any of the face information in the information management data of the user's situation; A reporting system comprising:

2. The reporting system of claim 1, wherein, when a user is locked into the elevator, if there is a target user among the users whose facial information acquired by the facial information acquisition unit matches any of the facial information in the information management data, the first reporting processing unit reports the occurrence of the lock-in to the contact information associated with the facial information in the information management data for each target user.

3. an API that, when receiving face information of each elevator user, returns a contact address associated with the face information if the face information matches the face information of a target person; A face information acquisition unit that acquires face information of each user who gets into the elevator car; a first notification processing unit that transmits the facial information of each user acquired by the facial information acquisition unit to the API, and when the contact information is returned from the API as a result, notifies the contact information of the status of the user; A reporting system comprising:

4. The reporting system of claim 3, wherein when a user becomes trapped in the elevator, the first reporting processing unit transmits facial information of each user trapped in the elevator to the API, and when the API returns the contact information as a result, the first reporting processing unit reports the occurrence of the trapping to the contact information.

5. The first notification processing unit is When a user is trapped in the elevator, a destination floor currently registered in the elevator in which the user is trapped is obtained from the elevator in which the user is trapped; The reporting system according to claim 4, wherein the facial information of each user acquired by the facial information acquisition unit is sent to an API among the APIs that can link with an external device managed by a resident of the destination floor, and if the API returns the contact information as a result, the occurrence of the entrapment is reported to the contact information.

6. The notification system of any of claims 2, 4, and 5, wherein the first notification processing unit, after notifying the contact point that the entrapment has occurred, instructs the elevator in which the entrapment has occurred to inform the user who is trapped in the elevator car that the contact point has been notified.

7. a second notification processing unit that, when receiving a rescue completion signal notifying that the rescue of the user from the entrapment has been completed after the first notification processing unit has notified the contact point of the occurrence of the entrapment, notifies the same contact point as the first notification processing unit that the rescue of the user from the entrapment has been completed; The notification system according to claim 2, 4, or 5, further comprising:

Images