Reporting System
The notification system uses face information acquisition and management data to automatically notify pre-registered contacts when a user is trapped in an elevator, addressing the challenge of users lacking a smartphone or contact information, ensuring timely awareness and safety.
Patent Information
- Application Number
- JP2023171844
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-10-03
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2043-10-03
AI Technical Summary
Users trapped in an elevator without a smartphone and unable to remember contact information for relatives or friends cannot effectively notify them of their situation, causing concern for those who may not be aware of their emergency.
A notification system that utilizes face information acquisition and management data to associate facial information with contact information, enabling automatic notification to pre-registered contacts when a user is trapped in an elevator, and includes an API for external data collaboration.
Enables timely notification to pre-registered contacts even if the user lacks a smartphone, ensuring they are aware of the user's situation and facilitating rescue, thereby reducing worry and ensuring safety.
Smart Images

Figure 0007582420000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to a notification technique applicable to elevators. [Background technology]
[0002] An emergency call button (e.g., 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 a user becomes trapped inside the car, the user can call the monitoring center using the emergency call button and request rescue from inside the car. Furthermore, if the user has a smartphone, the user can use the smartphone to notify relevant parties (family, friends, company, etc.) that they are trapped inside the car. Furthermore, even if the user does not have a smartphone, if the user has stored the contact information of relevant parties, the user can request the monitor to pass on a message to those contacts when notifying the monitoring center. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-202998 Summary of the Invention [Problem to be solved by the invention]
[0004] On the other hand, if a user is trapped inside a car and does not have a smartphone and does not have the contact information of relevant parties (family, friends, company, etc.) memorized, they can use the emergency call button to notify the monitoring center, but they will not be able to contact the relevant parties, which will cause them concern.
[0005] Therefore, 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, for each target person, facial information and contact information of that target person, in a mutually associated state. The face information acquisition unit acquires face information of each user who has boarded the elevator car. For each target person among the users who have boarded the car, whose facial information acquired by the face information acquisition unit matches any of the facial information in the information management data, the first report processing unit reports the status of that user to the contact information associated with the matching facial information.
[0007] According to the above-described aspect 1, by registering the facial information and contact information of each subject in the information management data, when each subject uses an elevator, the subject's situation can be reported to the relevant contacts (including when the subject has used the elevator). Examples of relevant contacts include the subject's family (e.g., guardian), or the subject's friends, company, cram school, school, etc. According to the above-described reporting to relevant contacts, each time the subject uses an elevator, the relevant contacts can receive a report and know that the subject has used the elevator. Furthermore, even in cases where an incident occurs to the subject while using an elevator and it would have been difficult for the relevant contacts to know the situation at the time (such as when the subject does not have a smartphone and does not remember the contact information of the relevant contacts, making it impossible for the relevant contacts to know the situation), the above-described aspect 1 allows the relevant contacts to know the subject's situation by receiving a report.
[0008] In the reporting system according to the above aspect 1, when a user is trapped in a car, if there is a target user among the trapped 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 may report the occurrence of the trapping 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 person is locked in a car, it would have been difficult for the relevant parties to know that the person has been locked in the car in the past. However, according to the above-mentioned aspect 2, the relevant parties can know that the person is locked in 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 and the face information matches the face information of a target person, the API replies with the contact information 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 the API returns a contact information as a result, the first report processing unit notifies the user's status to the contact information.
[0011] According to the above aspect 3, even if information management data is not held, 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 if a contact information is returned from the API as a result, the first reporting processing unit may report the trapping to that contact information (aspect 4).
[0013] According to the above-mentioned fourth aspect, it is possible to send the same notification as in the above-mentioned second aspect to the relevant parties.
[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 currently registered in the car. Then, the first report processing unit may transmit the facial information of each user acquired by the facial information acquisition unit to an API that can link with an external device managed by a resident of the destination floor, and when a contact information is returned from the API as a result, the first report processing unit may report the trapping to the contact information.
[0015] According to the above-mentioned aspect 5, when a user is trapped in a car, it becomes possible to notify the contacts likely to be related to each user at that time that the trapping has occurred.
[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 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 car can know that his / her situation (being trapped in the elevator car) has been reported to the relevant parties by receiving a message from the elevator. This makes it possible to give the user in the elevator car 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, after the first notification processor notifies a contact point that a user has been trapped, when the second notification processor receives a rescue completion signal notifying that the user has been rescued from the trapping, 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-mentioned aspect 7, in the event that a subject is trapped inside a car, the relevant parties will be notified of the trapping, and then will receive a further notification, thereby being able to know that the subject has been rescued from the trapping. [Effects 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 explanation 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. [Figure 2] 2A and 2B are conceptual diagrams illustrating information management data and report management data used in the embodiment. [Figure 3] 4 is a flowchart showing a first notification process executed in the embodiment. [Figure 4] 10 is a flowchart showing a second notification process executed in the embodiment. [Figure 5] 10 is a flowchart showing a first notification process executed in a second modified example. [Figure 6] FIG. 10 is a conceptual diagram illustrating an elevator to which a reporting system according to a third modified example is applied. [Figure 7] 10 is a flowchart showing a first notification process executed in a third modified example. [Figure 8]10 is a flowchart showing a first notification process executed in a fourth modified example. DETAILED DESCRIPTION OF THE INVENTION
[0022] [1] Implementation 1 is a conceptual diagram illustrating an elevator 1 to which a notification system according to an embodiment is applied. As shown in this diagram, an emergency call button 11 is usually provided inside a car G of the elevator 1 so that the elevator 1 can make a notification 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. Furthermore, if the user has a smartphone, the user can use the smartphone to notify relevant parties (family, friends, company, etc.) that he or she is trapped inside the car G. Furthermore, even if the user does not have a smartphone, if the user has memorized the contact information (telephone numbers, etc.) of 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 does not have a smartphone and does not have the contact information of relevant parties (family, friends, company, etc.) memorized, the user can use the emergency call button 11 to notify the monitoring center 2, but 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, the notification system that makes this possible is composed of a face information acquisition unit 12 installed in the elevator 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 elevator G.
[0027] Specifically, the face information acquisition unit 12 captures an image of the inside of the elevator car G, thereby acquiring an image showing the face of a user riding in the elevator car G. Then, the face information acquisition unit 12 performs image processing on the acquired image, thereby extracting face information Pf (such as facial features) of each user appearing in the image.
[0028] The face information acquisition unit 12 may acquire the face information Pf of each user only when a user is trapped in the car G in response to 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 users 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, in order to enable the face information acquisition unit 12 to accurately acquire the face information Pf of each user trapped in the car G, the elevator 1 may guide the users in the car G to turn their faces toward the face information acquisition unit 12 (such as a camera).
[0029] The facial information Pf of each user acquired by the facial information acquisition unit 12 is used in 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 via the control device 10 of the elevator 1. At this time, the control device 10 of the elevator 1 transmits the identification information Pe of the elevator 1 it controls together with the facial information Pf to the monitoring center 2, so that the control device 20 of the monitoring center 2 can recognize which elevator 1 is the sender of the facial information Pf.
[0030] The extraction of the facial information Pf from the image captured inside the car G may be executed by the control device 20 of the monitoring center 2. In this case, the control device 10 of the elevator 1 transmits the image captured by the facial information acquisition unit 12 of the elevator 1 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 storage devices such as ROM and RAM. The control unit 22 is a part configured with processing devices such as CPU and MPU.
[0033] Information management data Dp and notification 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 the notification 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 target person are stored in a mutually associated state. Specifically, the target person or a related person registers the target person's facial information Pf and contact information Ph in advance, and the information is stored in the information management data Dp in a mutually associated state. Here, a related person is someone who has a relationship with the target person that requires knowledge of the target person's situation, such as a manager who manages the target person (such as a guardian for a child or a family member for 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 that the target person is trapped in the elevator G.
[0035] The example in FIG. 2(A) shows a case where the email address of the person concerned is registered as the contact Ph. As a more specific example, the contact Ph is an email address that can be received on a mobile terminal device 3 (such as a smartphone; see FIG. 1) owned by the person concerned. Note that the contact Ph is not limited to an email address, and may be a phone number, a social media account, or the like, as long as it allows contacting the person concerned. Furthermore, the person concerned may be a friend, company, cram school, school, etc. of the target person.
[0036] Furthermore, information about each target person to be notified when a report is sent to relevant parties may be registered and saved in advance in the information management data Dp along 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 saved 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 notification management data Dq (see FIG. 2(B)) stores information that, when a notification is sent to the contact information Ph stored in the information management data Dp, enables another notification to be sent to the contact information Ph to inform the user that the rescue of the trapped user has been completed. Specifically, when a user is trapped in a car G of any of the monitored elevators 1, if any of the trapped users is a target person who has been pre-registered in the information management data Dp, a notification is sent to the contact information Ph for each target person, and the contact information Ph is stored in the notification management data Dq in association 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 information Ph, the target person's name and the date and time of the notification are stored in association with the identification information Pe.
[0039] When a user is trapped in a car G, and there is a target user among the trapped users whose facial information Pf acquired by the facial information acquisition unit 12 matches any of the facial information Pf in the information management data Dp, the control unit 22 notifies the contact Ph associated with the facial information Pf in the information management data Dp of the occurrence of the trapping for each target user (first notification processing). Furthermore, after notifying the contact Ph of the occurrence of the trapping, when the control unit 22 receives a rescue completion signal Sy notifying that the user has been rescued from the trapping, the control unit 22 notifies the same contact Ph as the contact Ph that received the rescue completion signal Sy, notifying that the user has been rescued from the trapping (second notification processing). The first notification processing and the second notification processing 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 unit 221 and a second notification processing unit 222 built in the control unit 22 (see FIG. 1). Specifically, these processing units are configured as software by causing the control unit 22 to execute a program. Such a program may be stored in a readable state on a portable storage medium (for example, a flash memory, etc.), read from the storage medium, installed, and stored in the storage unit 21 of the control device 20, or may be stored in a downloadable state on another server, downloaded from the server, installed, and stored in the storage unit 21. The above-mentioned processing units may be configured as hardware by building circuits in the control device 20.
[0041] 3 is a flowchart showing the first notification process executed by the control device 20 of the monitoring center 2 in this embodiment. This first notification process is initiated when a user is trapped in a car G of any of the elevators 1 to be monitored. Specifically, the first notification process is initiated when the control device 20 of the monitoring center 2 receives a trapping occurrence signal Sx notifying that a trapping has occurred and identification information Pe of the elevator 1 in which the trapping 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-person occurrence signal Sx and the identification information Pe in the following manner. First, when the elevator 1 makes an emergency stop and a passenger in the car G notifies the monitoring center 2 using the emergency call button 11, the identification information Pe of the emergency-stopped elevator 1 is transmitted to the monitoring center 2. The supervisor who receives the notification communicates with the passenger 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 the car G to the nearest floor is successful, the passenger in the car G is rescued within a short time after the emergency stop. On the other hand, if the remote rescue fails, the passenger will be trapped in the car G. In that case, the supervisor presses a button or the like to notify that a trap has occurred, and the trapped-person occurrence signal Sx is output. The trapped-person occurrence signal Sx is then received by the control device 20 together with the identification information Pe of the elevator 1 in which the trapping has occurred.
[0043] In addition, the series of steps from receiving the identification information Pe to outputting the trapped-in occurrence signal Sx that are performed at the monitoring center 2 when the elevator 1 is stopped in an emergency is not limited to being performed by the operation of a monitor, but may be appropriately changed to an automated process by having the control device 20 execute a program.
[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 that elevator 1 from the face information acquisition unit 12 via the control device 10 of that 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 the users in the car G via 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 the users in the car G to turn their faces towards the face information acquisition unit 12 (such as a camera) so that the face information acquisition unit 12 can accurately acquire the face information Pf of each user trapped in the car G.
[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, from among the users trapped in the elevator G, subjects who have been pre-registered in the information management data Dp. Specifically, the control device 20 compares the face information Pf acquired in step S11 one by one with the face information Pf stored in the information management data Dp. Then, the control device 20 extracts users whose face information Pf matches in the comparison (i.e., users whose face authentication was successful) as subjects who have been pre-registered in the information management data Dp.
[0047] Thereafter, the control device 20 determines whether or not any of the users trapped in the elevator car G has successfully passed face authentication in step S12 (a target person who has been pre-registered in the information management data Dp) (step S13). Specifically, the control device 20 determines whether or not a pre-registered target person has been extracted by executing step S12.
[0048] If 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 user's face information Pf in the information management data Dp (step S14).The control device 20 then notifies the extracted contact information Ph that a person has been locked into the elevator car G (step S15).
[0049] As a result, if a target person who has been pre-registered in the information management data Dp becomes trapped in a car G, it becomes possible to notify the contact information Ph of the relevant person who is registered in the information management data Dp that the target person has been trapped in the car G. Therefore, even if a user becomes trapped in a car G and it would have been difficult for the relevant person to know that the user has been trapped in the car G in the past, the relevant person can know that the target person who has been pre-registered in the information management data Dp has been trapped in the car G by receiving the notification.
[0050] In step S14, for each user whose face has been successfully authenticated, the control device 20 may extract, along with the contact information Ph, other information (such as name (see FIG. 2(A))) associated with the user's face information Pf in the information management data Dp. Then, in step S15, the control device 20 may notify the contact information Ph extracted in step S14 that a person has been trapped in the car G, and may also send the other information (such as name) extracted in step S14 to the contact information Ph. The control device 20 may also send information about the installation 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 identify who is trapped and where they are trapped.
[0051] After step S15, the control device 20 stores the contact information Ph extracted in step S14 for each user whose face authentication in step S12 was successful 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 authentication was successful (No)", it ends the first notification process without performing steps S14 to S16 described above.
[0053] 4 is a flowchart 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 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 trapped user 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 passenger 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 passenger from the trapping. After that, the maintenance worker transmits the rescue completion signal Sy and the identification information Pe of the elevator 1 that performed the rescue from his / her own terminal device to the monitoring center 2 to notify the monitoring center 2 that the rescue has been completed. The rescue completion signal Sy is then received by the control device 20 together with the identification information Pe of the elevator 1 that was rescued.
[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] Thereafter, the control device 20 determines whether or not there was any contact information Ph extracted in step S21 (step S22). Based on this determination, the control device 20 can determine whether or not any of the users rescued from being trapped were previously registered in the information management data Dp (in other words, whether or not any of the users who were notified of the occurrence of being trapped were registered in the information management data Dp).
[0057] Specifically, if 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 pre-registered in the information management data Dp (in other words, a user who was notified of the occurrence of confinement to relevant parties). 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 occurrence of confinement through the notification that the target person has been rescued from confinement.
[0058] Thereafter, the control device 20 deletes the contact point Ph that made the report in step S15 and all the information associated with it from the report 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 none of the users rescued from being trapped were previously registered in the information management data Dp (in other words, users who had been notified of their trapping to relevant parties). In this case, the control device 20 ends the second notification process without performing steps S23 and S24 described above.
[0060] As a result, in the event that a subject who has been pre-registered in the information management data Dp is trapped in a car G, it is possible to notify the relevant parties registered in the information management data Dp of the completion of the rescue when the subject is rescued from the trapping. Therefore, after receiving the notification that the trapping has occurred, the relevant parties can receive the further notification and thereby know that the subject has been rescued from the trapping.
[0061] As described above, according to the reporting system of the present embodiment, by pre-registering the target person's face information Pf and contact information Ph in the information management data Dp, when each target person uses the elevator 1 (in the present embodiment, if the target person is trapped while using the elevator 1), the target person's situation can be reported to the relevant parties in the contact information Ph. Therefore, for a specific user (a target person pre-registered in the information management data Dp), the relevant parties can know the situation when the user uses the elevator 1. Specifically, even if an incident occurs to a target person while using the elevator 1 and it would have been difficult for the relevant parties to know the situation at that time in the past (for example, if the target person does not have a smartphone and does not remember the contact information of the relevant parties, and therefore has no means of contacting the relevant parties), the reporting system of the present embodiment allows the relevant parties to know the target person's situation by receiving a report.
[0062] [2] Variation [2-1] First modified example In the above-described embodiment, the notification system is not limited to issuing a notification when a person is trapped inside the elevator car G, but can also be applied to notifying 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 getting on the elevator car G) that the person has used the elevator 1 (the usage history of the elevator 1).
[0063] According to the first variant, whenever a person who has been pre-registered in the information management data Dp uses elevator 1, the relevant parties can receive a notification and become aware that the person has used elevator 1.
[0064] The reporting system of the first modified example can be used for purposes such as contacting parents when a child uses the elevator 1 (for example, for parents to confirm that their child has gone to school or cram school as scheduled, or has returned from school or cram school). The reporting system of the first modified example can also be used for purposes such as family members confirming 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 modified example can also be used for purposes such as related parties checking the behavioral history of a target person.
[0065] [2-2] Second variant 5 is a flowchart 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 notifying 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 notify the user in the car G in which the trapped occupant has been trapped through the communication device 13, the display device 14, or a speaker (not shown) installed in the car G that the contact point Ph has been notified (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 contacts Ph from the cloud through API integration instead of extracting the contacts 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 modification is applied. As shown in this diagram, the reporting system may include an API 4 instead of 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, cram school, or 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 pre-registered 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 notification 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 elevator 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), it causes the external device 5 linked via itself to perform face authentication using the face information Pf and, if the face authentication is successful, extract the contact information Ph. Then, if 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, if 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 determines whether the received information is a contact point Ph or an error signal Sz (step S33). If the control device 20 determines in step S33 that the information is a "contact point Ph," it sends a notification to the contact point Ph (step S15) and saves the information in the notification management data Dq (step S16). On the other hand, if the control device 20 determines in step S33 that the information is an "error signal Sz," it ends the first notification 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, thereby making it possible to send notifications to relevant parties in the same way 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 also be a cloud server that stores personal schedule management data. In this case, the control device 20 can acquire contacts Ph extracted from the personal schedule management data through API linkage.
[0074] [2-4] Fourth Variation 8 is a flowchart showing the first notification 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 third modified example described above.
[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 API4s that can cooperate 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, or English conversation school).
[0077] When the API 4 receives face information Pf from the control device 20 (step S41), it causes the external device 5, which is linked via the API 4, to perform face authentication using the face information Pf and extract contact information Ph if the face authentication is successful. If the external device 5 has face information Pf for which face authentication has been successful as a result of responding to a command from the API 4, it extracts contact information Ph associated with the face information Pf and passes it to the API 4. At this time, the external device 5 may pass the reception or counter of the company or tenant that manages the external device 5 to the API 4 as the contact information Ph. Thereafter, 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, if the external device 5 fails in face authentication, the API 4 returns an error signal Sz to the control device 20 (step S42).
[0078] According to the fourth variant, if a user is trapped in the car G, it is possible to notify the contact Ph that is likely to be related to each user at that time of the occurrence of the trapping.
[0079] The above-described embodiments and modifications should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined not by the above-described embodiments and modifications, but by the claims. Furthermore, the scope of the present invention is intended to include all modifications that are equivalent to the scope of the claims and fall within the scope thereof.
[0080] Furthermore, from the above-described embodiments and modifications, the subject matter of the invention is not limited to the notification system, but may also include devices constituting the notification system, control processes and programs executed by the notification system, etc., or some of these may be extracted partially. Also, some or all of the overall configuration including elevator 1 to which the notification system is applied may be extracted as the subject matter 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 Unit 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 Second Report Processing Department Pr1, Pr2 received information
Claims
1. 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; Equipped with 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 transmits the facial information of each user acquired by the facial information acquisition unit to an API among the APIs that can link with an external device managed by the occupant of the destination floor, and if the API returns the contact information as a result, the system reports the occurrence of the entrapment to the contact information.
2. The notification system of claim 1, wherein the first notification processing unit notifies the contact point that the entrapment has occurred, and then instructs the elevator in which the entrapment has occurred to inform a user who is trapped in the elevator car that the contact point has been notified.
3. 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 reporting system according to claim 1 or 2, further comprising:
Citation Information
Patent Citations
Elevator monitor, elevator monitoring program, and storage medium
JP2005154092A
Security camera system for elevator
JP2005255274A
Information delivery system using face picture identification
JP2006107187A
Remote monitoring system of elevator
JP2008120581A
Emergency informing device of elevator
JP2009202998A
