JP6463401B2 - Notification device, notification method, program, and notification system - Google Patents

Description

  The present invention relates to a technique for assigning a destination floor to each car of a plurality of elevators.

  Conventionally, an elevator group management apparatus for efficiently operating a plurality of elevators is known. For example, in the elevator group management apparatus described in Patent Literature 1, when a hall call registration is performed by a passenger, the passenger is assigned to the passenger group, and among the registered passenger groups, the passenger group that is not assigned to the car is regularly added. A basket is assigned. In this elevator group management device, a car is assigned to a passenger group regardless of the number of passengers constituting the passenger group.

International Publication No. 2010/032625

  An object of the present invention is to improve the transportation capacity of each elevator as compared with a case where a car is assigned to a destination floor without considering the number of users heading to the destination floor.

  In order to solve the above problems, a notification device according to the present invention includes a destination floor specifying unit that specifies a destination floor of each user who intends to use any of a plurality of elevators, and a destination floor for each destination floor. A waiting number management unit that counts the number of users heading to the destination floor, and when the number of users heading to the first destination floor reaches a predetermined number, the plurality of the plurality of users with respect to the first destination floor A car allocating unit for allocating any first car of the elevator and a user heading to the first destination floor are notified that the first car has been allocated to the first destination floor. A notification unit.

  In a preferred aspect, the notification device further includes a passenger number specifying unit that specifies the number of users who have boarded the first car, and the waiting number management unit uses the number counted for the first destination floor. The specified number of persons is subtracted from the number of persons.

  In a further preferred aspect, the notification device further includes a waiting state monitoring unit that monitors a waiting time of each user, and the car allocating unit has a waiting time of a first user among the users. When the predetermined time is reached, the second car of any of the plurality of elevators is assigned to the second destination floor to which the first user goes, and the notification unit The first user is notified that the second car has been assigned to the destination floor.

  In a further preferred aspect, the notification device is configured such that when the number of users heading to the second destination floor does not reach a predetermined number, a second user who is different from the first user heads. A destination floor determining unit that identifies the destination floor, wherein the car allocating unit allocates the second car to the second and third destination floors, and the notification unit includes the second and second destination floors. The first and second users are notified that the second car has been assigned to the third destination floor.

  In a further preferred aspect, the notification device excludes a passenger identification unit that identifies a user who has boarded the first car and the identified user from the waiting time monitoring target by the waiting state monitoring unit. And a waiting state management unit.

  In a further preferred aspect, the notification device further includes an attribute specifying unit that specifies an attribute of each user, and when the attribute of a third user among the users satisfies a predetermined condition, A third car of any of the plurality of elevators is assigned to a fourth destination floor to which a third user heads, and the notification unit is configured to send the third car to the fourth destination floor. The third user is notified that a car has been allocated.

  The notification method according to the present invention includes a step in which the destination floor specifying unit specifies a destination floor of each user who intends to use any of the plurality of elevators, and a waiting number management unit is provided for each destination floor. And the step of counting the number of users heading to the destination floor, and the car allocating unit, when the number of users heading to the first destination floor reaches a predetermined number, Assigning the first car of any of the plurality of elevators to the first destination floor that the notifying unit has assigned the first car to the first destination floor. And a step of notifying a user heading for.

  The program according to the present invention is directed to a destination floor specifying unit that specifies a destination floor of each user who intends to use one of a plurality of elevators, and a destination floor for each destination floor. The waiting number management unit that counts the number of users, and when the number of users heading to the first destination floor reaches a predetermined number of the plurality of elevators with respect to the first destination floor A car allocating unit for allocating any first car, and a notifying unit for notifying a user heading for the first destination floor that the first car has been allocated to the first destination floor It is a program to make it.

  The notification system according to the present invention is a notification system including a photographing device, a notification device, and an output device, and the photographing device photographs each user who intends to use one of a plurality of elevators. The notification device includes a destination floor specifying unit that specifies the destination floor of each user specified by analyzing an image captured by the imaging device, and a user heading to the destination floor for each destination floor Any of the plurality of elevators for the first destination floor when the number of users waiting for the first destination floor and the number of users heading to the first destination floor reach a predetermined number A car allocating unit for allocating the first car and the user arriving at the first destination floor via the output device that the first car has been allocated to the first destination floor. A notification unit for notification.

  According to the present invention, the transportation capacity of each elevator can be improved as compared with the case where a car is assigned to the destination floor without considering the number of users heading to the destination floor.

1 is a diagram illustrating an example of a configuration of a notification system 1. FIG. 4 is a plan view showing an installation example of each device other than the notification device 10. FIG. It is a figure which shows an example of user information DB121. It is a figure which shows an example of waiting number management DB122. It is a figure which shows an example of waiting condition management DB123. It is a figure which shows an example of operation condition DB124. It is a figure which shows an example of destination floor management DB125. It is a figure which shows an example of the screen which notifies the correspondence of a destination floor and a car displayed on the display. It is a flowchart which shows an example of a floor demand specific process. It is a flowchart which shows an example of a car allocation process. It is a flowchart which shows an example of a 1st car allocation process. It is a flowchart which shows an example of a 2nd car allocation process. It is a flowchart which shows an example of a destination floor determination process. It is a flowchart which shows an example of a waiting condition and the number of persons correction process. It is a figure which shows an example of the screen which notifies the correspondence of a destination floor and a car displayed on the display.

1. Embodiment 1-1. Configuration FIG. 1 is a diagram illustrating an example of a configuration of a notification system 1 according to an embodiment of the present invention. The notification system 1 is a system for assigning a user's destination floor to each car of a plurality of elevators and notifying the user of a correspondence relationship between the car and the destination floor. As shown in the figure, the notification system 1 includes a notification device 10, two entrance cameras 20, six landing cameras 30, a display 40, and a speaker 50. The notification device 10 and other devices are connected by wire or wireless.

  The notification device 10 is a computer including an arithmetic processing device 11 such as a CPU, a storage device 12 such as a ROM, a RAM, and an HDD, and an input / output interface 13. The notification device 10 assigns the user's destination floor to each car of the plurality of elevators based on the images taken by the entrance camera 20 and the landing camera 30, and displays the correspondence relationship between the car and the destination floor with the display 40 and the speaker 50. Use to notify users. Details of the notification device 10 will be described later. As a modification, the notification device 10 may be configured by a plurality of servers connected to each other via a communication line.

  The entrance camera 20 is a photographing device for photographing a face of a user who intends to use an elevator. The entrance camera 20 is installed, for example, on a passage through which a user who wants to use an elevator passes.

  The hall camera 30 is a photographing device for photographing a face of a user who is about to get on the elevator car. The hall camera 30 is installed in an elevator hall for each elevator, for example.

  The display 40 is an image output device for outputting an image for notifying the correspondence of each elevator car and the destination floor. For example, a liquid crystal display or an organic EL display. The display 40 is installed at a position that is easy for a user who wants to use the elevator.

  The speaker 50 is an audio output device for outputting audio information for notifying the correspondence between each elevator car and the destination floor. The speaker 50 is installed, for example, so that sound reaches a user who wants to use an elevator.

  FIG. 2 is a plan view illustrating an installation example of each device other than the notification device 10. The installation location shown in the figure is an elevator hall provided on the first floor of the building for getting on and off the 18 elevators E1 to E18. Of the 18 elevators E1 to E18 that get on and off at this elevator hall, the elevators E1 to E6 are elevators for lower floors (1 to 10 floors), and the elevators E7 to E12 are for middle floors (11 to 20 floors). It is an elevator, and elevators E13 to E18 are elevators for higher floors (21 to 30 floors). In description of this embodiment, the case where a user's destination floor is allocated to each cage | basket | car of elevators E13-E18 for higher floors among these elevators is assumed. In the following description, the elevators E13 to E18 for higher floors are collectively referred to as “elevator E”.

  In the elevator hall, the two entrance cameras 20 are installed on the ceiling near the entrance gate G and photograph the face of the user passing through the entrance gate G. Here, the entrance gate G is an entrance gate through which a user who uses the elevator E for the higher floor passes to go to the landing of the elevator E for the higher floor. In addition, the user who passes this entrance gate G is restricted only to the user of the elevator E for high floors, and the user who uses the elevator for low floors or a middle floor does not pass this entrance gate G. To do. In the elevator hall, the six hall cameras 30 are each installed on the ceiling of the elevator E for the higher floors and photograph the face of the user who is going to get on the elevator E car. The display 40 and the speaker 50 are installed at a position where a user who passes through the entrance gate G and goes to the elevator E landing can view the output information.

  The storage device 12 of the notification device 10 described above stores a user information DB 121, a waiting number management DB 122, a waiting state management DB 123, an operation state DB 124, and a destination floor management DB 125.

  FIG. 3 is a diagram illustrating an example of the user information DB 121. The user information DB 121 is a database that stores in advance information on users who use the elevator E. Each record of the user information DB 121 includes a user ID that is user identification information, feature point position data of the user's face, and the user's affiliation floor.

  FIG. 4 is a diagram illustrating an example of the waiting number management DB 122. The waiting number management DB 122 is a database for managing the number of users waiting for the elevator E for each destination floor of the elevator E. Each record of the waiting number management DB 122 is composed of a destination floor and the number of users heading to the destination floor.

  FIG. 5 is a diagram illustrating an example of the waiting status management DB 123. The waiting status management DB 123 is a database for managing the waiting status of each user waiting for the elevator E. Each record of the waiting state management DB 123 is assigned a car to the user ID, the user's destination floor, the time specified by the user specifying unit 1101 described later, and the user's destination floor. And a car allocation flag indicating whether or not there is.

  FIG. 6 is a diagram illustrating an example of the operation status DB 124. The operation status DB 124 is a database for managing the operation status of each elevator E. Specifically, it manages the operation status such as the current position of the car, whether it is moving up and down, registration status of hall call and car call, and open / close status of doors. Each record of the operation status DB 124 includes a car ID that is identification information of the elevator E car and an operation status of the elevator E. The operation status stored in the operation status DB 124 is periodically acquired from an elevator control server (not shown) that controls the operation of the elevator E.

  FIG. 7 is a diagram illustrating an example of the destination floor management DB 125. The destination floor management DB 125 is a database for managing the destination floor of the car of each elevator E. Each record of the destination floor management DB 125 includes a car ID, a car destination floor, and a user ID of a user who is scheduled to get on the car.

  Next, the arithmetic processing unit 11 of the notification device 10 includes a user specifying unit 1101, a destination floor specifying unit 1102, a waiting number managing unit 1103, a waiting state managing unit 1104, a waiting number monitoring unit 1105, and a car specifying. Unit 1106, car allocation unit 1107, notification unit 1108, waiting status monitoring unit 1109, destination floor determination unit 1110, car arrival monitoring unit 1111, passenger identification unit 1112, flag correction unit 1113, waiting number of people A function of a correction unit 1114 is provided. These functions are realized when the arithmetic processing unit 11 executes a program stored in the storage device 12.

  The user identifying unit 1101 identifies a user who has been photographed by the entrance camera 20 and passes through the entrance gate G using a known face authentication technique. For example, a face area is detected in an image output from the entrance camera 20, and positions of feature points such as a pupil center, a nose wing, and a mouth end are detected from the face area, and each of the feature point positions stored in the user information DB 121 is detected. The user who intends to use the elevator E is identified.

  The destination floor specifying unit 1102 specifies the destination floor of the user specified by the user specifying unit 1101 with reference to the user information DB 121.

  When the destination floor is specified by the destination floor specifying unit 1102, the waiting number management unit 1103 increments the count of the specified destination floor in the waiting number management DB 122. In addition, when the correspondence relationship between the destination floor and the car is newly registered in the destination floor management DB 125, the waiting number management unit 1103 resets the waiting number on the destination floor in the waiting number management DB 122. When the waiting number correction instruction is output from the flag correction unit 1113, the waiting number management unit 1103 changes the waiting number in the waiting number management DB 122 according to the correction instruction. The waiting number management unit 1103 assigns to the destination floor specified by the passenger specifying unit 1112 from the waiting number on the destination floor by executing the above-described process of resetting the waiting number and the process of changing the waiting number. Reduce the number of users who actually get on the basket.

  When the user is specified by the user specifying unit 1101 and the destination floor of the user is specified by the destination floor specifying unit 1102, the waiting status management unit 1104 has the user ID, the specific time, and the destination floor of the user. The car assignment flag “NO” is stored in the waiting situation management DB 123 in association with each other. In addition, when the correspondence relationship between the destination floor and the car is newly registered in the destination floor management DB 125, the waiting state management unit 1104 associates the destination floor with the car assignment flag “NO” in the waiting state management DB 123. Change the car allocation flag of the existing user to “YES”. Further, when the flag correction instruction is output from the flag correction unit 1113, the waiting situation management unit 1104 corrects the car assignment flag in the waiting situation management DB 123 according to the correction instruction. The waiting state management unit 1104 is assigned to the destination floor specified by the passenger specifying unit 1112 by executing the process of changing the car assignment flag to “YES” and the process of correcting the car assignment flag. A user who actually gets in the basket is excluded from the waiting time monitoring target by the waiting state monitoring unit 1109.

  The waiting number monitoring unit 1105 refers to the waiting number management DB 122 and determines whether the waiting number has reached a predetermined number for any destination floor. Here, the predetermined number of persons is the number of persons set according to the capacity of the car. For example, when the capacity of the car is 20, the number is set to 20 persons.

  When the waiting number monitoring unit 1105 determines that the waiting number has reached a predetermined number, the car specifying unit 1106 refers to the operation status DB 124 and the destination floor management DB 125, and the car is not assigned to the destination floor. The car with the shortest estimated arrival time to the elevator hall is identified. As a method for calculating the predicted arrival time, a known method may be used (see, for example, Japanese Patent Application Laid-Open No. 2005-200136). The car identifying unit 1106 also identifies the car when the destination floor is determined by the destination floor determining unit 1110.

  The car assigning unit 1107 assigns the car specified by the car specifying unit 1106 to the destination floor determined by the waiting number monitoring unit 1105 that the waiting number has reached a predetermined number. Specifically, the destination floor and the car ID of the car are associated with each other and stored in the destination floor management DB 125. At that time, the car allocation unit 1107 is a user associated with the destination floor and the car allocation flag “NO” in the waiting situation management DB 123 (in other words, a user heading for the destination floor, A user ID of a user to whom a car is not assigned is also stored in the destination floor management DB 125 in association with the destination floor as a scheduled passenger. The car assigning unit 1107 also assigns the car specified by the car specifying unit 1106 to the destination floor determined by the destination floor determining unit 1110. In addition, when the car arrival monitoring unit 1111 determines that the elevator E has arrived, the car assignment unit 1107 deletes the information on the destination floor and the information on the passenger who is expected to be associated with the car in the destination floor management DB 125. .

  When the correspondence between the destination floor and the car is newly registered in the destination floor management DB 125, the notification unit 1108 uses the display 40 and the speaker 50 to notify the user that the car has been assigned to the destination floor. Notify FIG. 8 is a diagram showing an example of a screen for notifying the correspondence between the destination floor and the car displayed on the display 40. In the screen shown in the figure, for example, it is notified that “13” elevator cars are assigned to the destination floor “30F”. On the other hand, from the speaker 50, for example, a voice message “If you are going to the 30th floor, please wait in front of the No. 13 unit” is output. The voice message may be stored in the storage device 12 in advance or may be generated by voice synthesis.

  The waiting state monitoring unit 1109 refers to the waiting state management DB 123 to determine whether or not the waiting time of any user registered in the DB has reached a predetermined time. At that time, the waiting state monitoring unit 1109 determines whether or not the waiting time of the user has reached a predetermined time by comparing the user specific time registered in the waiting state management DB 123 with the current time. To do. Here, the predetermined time is set to a generally allowable time (for example, 3 minutes) as the waiting time of the elevator E.

  The destination floor determination unit 1110 performs a destination floor determination process to determine a user to be shared with a user whose waiting time has been determined to have reached a predetermined time by the waiting state monitoring unit 1109. Specifically, first, one or more users with long waiting times are specified with reference to the waiting state management DB 123. The users specified here are users whose destination floors are different from each other, and whose destination floors are different from those of users whose waiting time has reached a predetermined time, and are associated with the car assignment flag “NO”. It is a user. A user with a longer waiting time is identified preferentially. Next, the waiting number management DB 122 is referred to and the waiting number of the specified user on the destination floor is specified. And when the total number of waiting people specified and the number of waiting people on the destination floor of the user whose waiting time has reached a predetermined time falls within a predetermined range, the number of all the destination floors is less than the predetermined number. In some cases, all these destination floors are determined as the destination floor of the car. Here, the predetermined range is a range set based on the capacity of the car. For example, when the capacity of the car is 20 people, the predetermined range is set to 15 to 20 people. Further, the predetermined number is an allowable number of floor stops of the car, and is set to “3”, for example.

  The car arrival monitoring unit 1111 determines whether or not the car of the elevator E has arrived at the elevator hall with reference to the operation status DB 124.

  When it is determined by the car arrival monitoring unit 1111 that the car has arrived at the elevator hall, the passenger specifying unit 1112 uses a well-known face authentication technique to capture a user who has taken the car, which is taken by the landing camera 30. Identify. For example, the face area is detected in the image output from the hall camera 30 corresponding to the car, and the positions of the feature points such as the pupil center, the nose wings, and the mouth end are detected from the face area and stored in the user information DB 121. By collating with each of the feature point positions, the user who gets on the car is specified. Passenger specific part 1112 specifies a user's individual, and also specifies the number of users.

  The flag correcting unit 1113 refers to the destination floor management DB 125, and uses the user ID of the user specified by the passenger specifying unit 1112 and the use of the passenger who is determined to have arrived by the car arrival monitoring unit 1111 The user ID is compared, and a flag correction instruction is generated based on the comparison result. Specifically, when the user specified by the passenger specifying unit 1112 is not registered as a scheduled passenger of the car in the destination floor management DB 125 (that is, when a user who is not scheduled to get in gets on) In the waiting situation management DB 123, a flag correction instruction is generated that instructs to change the car assignment flag of the user to “YES”. On the contrary, when the user registered as the scheduled passenger of the car in the destination floor management DB 125 is not specified by the passenger specifying unit 1112 (that is, when the scheduled passenger does not get on), In the waiting state management DB 123, a flag correction instruction is generated that instructs the user to change the car assignment flag to “NO”. The generated flag correction instruction is output to the waiting state management unit 1104.

  The waiting number correction unit 1114 refers to the destination floor management DB 125, the number of users specified by the passenger specifying unit 1112, and the number of passengers scheduled to board the car determined to have arrived by the car arrival monitoring unit 1111. And the waiting number correction instruction is generated based on the comparison result. At that time, the number of people is compared for each destination floor. Specifically, the number of users specified by the passenger specifying unit 1112 for a certain destination floor is more than the number of passengers scheduled to be associated with that destination floor in the destination floor management DB 125. When there are many users (that is, when more users than expected are on board), the waiting number management DB 122 generates a waiting number correction instruction instructing to subtract the waiting number on the destination floor by the difference. Conversely, when the number of users specified by the passenger specifying unit 1112 for a certain destination floor is smaller than the number of passengers scheduled to be associated with that destination floor in the destination floor management DB 125 In this case (that is, when there are fewer users than planned), the waiting number management DB 122 generates a waiting number correction instruction instructing to add the waiting number on the destination floor by the difference. The generated waiting number correction instruction is output to the waiting number management unit 1103.

1-2. Operation Processing performed by the notification device 10 will be described. Specifically, a floor demand specifying process for specifying demand for each destination floor of the elevator E, a car assignment process for allocating a car to the user's destination floor and notifying the user of the correspondence between the destination floor and the car, The waiting situation / number of people correction process for correcting the waiting situation of the user and the number of waiting people after the car departs from the landing will be described.

1-2-1. Floor demand specifying process FIG. 9 is a flowchart showing an example of the floor demand specifying process. The floor demand specifying process is executed in a predetermined time zone when the elevator hall is crowded with users of the elevator E. For example, it is executed during work hours.

The user specifying unit 1101 of the notification device 10 specifies the user who appears in the image output from the entrance camera 20 using the face authentication technique (Sa1). When the user is specified, the destination floor specifying unit 1102 specifies the destination floor of the user with reference to the user information DB 121 (Sa2). When the destination floor is specified, the waiting number management unit 1103 increments the count of the destination floor in the waiting number management DB 122 (Sa3). When the count of the destination floor is incremented, the waiting state management unit 1104, the user ID of the user specified in step Sa1, the specific time, the destination floor specified in step Sa2, and the car assignment flag “ “NO” is associated and stored in the waiting state management DB 123 (Sa4). When the storage of the waiting state is completed, it is determined whether or not a predetermined process end time has been reached (Sa5). If the process end time has not been reached (NO in Sa5), step Sa1 is executed again, and the process is completed. If the end time has been reached (YES at Sa5), the floor demand specifying process ends.
The above is the description of the floor demand specifying process.

1-2-2. FIG. 10 is a flowchart showing an example of the car assignment process. The car allocation process is executed in parallel with the floor demand specifying process.

  The waiting number monitoring unit 1105 of the notification device 10 refers to the waiting number management DB 122 to determine whether the waiting number has reached a predetermined number for any destination floor (Sb1). As a result of this determination, if the waiting number has not reached the predetermined number for any destination floor (NO in Sb1), step Sb3 is executed. On the other hand, as a result of this determination, when the number of waiting persons reaches a predetermined number for any one of the destination floors (YES in Sb1), the first car allocation process is executed. FIG. 11 is a flowchart illustrating an example of the first car allocation process.

In the first car assignment process, the car identifying unit 1106 refers to the operation status DB 124 and the destination floor management DB 125, and is the car that is not assigned to the destination floor, and has the shortest estimated arrival time at the landing. A car is specified (Sb21). When the car is specified, the car assignment unit 1107 associates the destination floor determined to have reached the predetermined number of people in step Sb1 with the car ID of the car specified in step Sb21 to associate the car with the destination floor. Store in the management DB 125 (Sb22). At that time, the car allocation unit 1107 is a user associated with the destination floor and the car allocation flag “NO” in the waiting situation management DB 123 (in other words, a user heading for the destination floor, A user ID of a user to whom a car is not assigned is also stored in the destination floor management DB 125 in association with the destination floor as a scheduled passenger. When the correspondence between the destination floor and the car is newly registered in the destination floor management DB 125, the notification unit 1108 uses the display 40 and the speaker 50 to notify the user that the car has been assigned to the destination floor. (Sb23). When the correspondence is notified, the waiting number management unit 1103 resets the waiting number on the destination floor in the waiting number management DB 122 (Sb24). When the waiting number is reset, the waiting situation management unit 1104 changes the car assignment flag of the user associated with the destination floor and the car assignment flag “NO” in the waiting situation management DB 123 to “YES”. (Sb25).
The above is the description of the first car allocation process.

  When the first car allocation process is completed, the waiting state monitoring unit 1109 refers to the waiting state management DB 123 to determine whether the waiting time of any user registered in the DB has reached a predetermined time. Is determined (Sb3). As a result of this determination, when the waiting time of any user has not reached the predetermined time (NO in Sb3), step Sb5 is executed. On the other hand, as a result of this determination, when the waiting time of any user reaches a predetermined time (YES in Sb3), the second car allocation process is executed. FIG. 12 is a flowchart illustrating an example of the second car allocation process.

  In the second car allocation process, the destination floor determination unit 1110 executes the destination floor determination process in order to determine a user to be shared with the user whose waiting time has been determined to have reached a predetermined time in step Sb3. (Sb41). FIG. 13 is a flowchart illustrating an example of the destination floor determination process.

In the destination floor determination process, the destination floor determination unit 1110 refers to the waiting number management DB 122 and the waiting state management DB 123 to identify the waiting number of users on the destination floor whose waiting time has reached a predetermined time (Sb411). ). When the number of waiting people is specified, the destination floor and the number of waiting people are recorded in the RAM. Next, the destination floor determination unit 1110 refers to the waiting situation management DB 123 and identifies another user who has a long waiting time (Sb412). The user specified here is a user whose destination floor is not recorded in the RAM and is associated with the car assignment flag “NO”. Further, the user is an unspecified user in the destination floor determination process. When another user is specified, the waiting number management DB 122 and the waiting state management DB 123 are referred to, and the waiting number on the destination floor of the other user is specified (Sb413). When the number of waiting people is specified, the destination floor and the number of waiting people are recorded in the RAM. Next, the destination floor determination unit 1110 determines whether or not the total number of waiting people recorded in the RAM is larger than the upper limit of the predetermined range (Sb414). As a result of this determination, if the total number of waiting people is larger than the upper limit of the predetermined range (YES in Sb414), the set of the destination floor and waiting number recorded in the RAM in the immediately preceding step Sb413 is deleted from the RAM ( Sb415), Step 412 is executed again. On the other hand, if the result of this determination is that the total number of waiting people is less than or equal to the upper limit of the predetermined range (NO in Sb414), it is determined whether or not the total number of waiting people is smaller than the lower limit of the predetermined range (Sb416). . As a result of the determination, when the total number of waiting persons is equal to or greater than the lower limit of the predetermined range (NO in Sb416), the destination floor recorded in the RAM is determined as the destination floor of the car (Sb417), and the destination floor determination process Ends. On the other hand, if the result of this determination is that the total number of waiting people is smaller than the lower limit of the predetermined range (YES in Sb416), it is determined whether or not the number of destination floors recorded in the RAM is greater than or equal to the predetermined number. (Sb418). In other words, it is determined whether or not the planned stop floor number of the car is greater than or equal to a predetermined floor number. If the result of this determination is that the number of destination floors is greater than or equal to a predetermined number (YES in Sb418). Step Sb417 is executed. On the other hand, as a result of this determination, when the number of destination floors is less than the predetermined number (NO in Sb418), step 412 is executed again.
This completes the description of the destination floor determination process.

When the destination floor determination process ends, the car identification unit 1106 refers to the operation status DB 124 and the destination floor management DB 125, and is the car that is not assigned to the destination floor, and has the shortest predicted arrival time at the landing. A car is specified (Sb42). When the car is specified, the car assignment unit 1107 stores the destination floor determined in step Sb417 and the car ID specified in step Sb42 in association with each other in the destination floor management DB 125 (Sb43). At that time, the car allocation unit 1107 is a user associated with the destination floor and the car allocation flag “NO” in the waiting situation management DB 123 (in other words, a user heading for the destination floor, A user ID of a user to whom a car is not assigned is also stored in the destination floor management DB 125 in association with the destination floor as a scheduled passenger. When the correspondence between the destination floor and the car is newly registered in the destination floor management DB 125, the notification unit 1108 uses the display 40 and the speaker 50 to notify the user that the car has been assigned to the destination floor. (Sb44). When the correspondence is notified, the waiting number management unit 1103 resets the waiting number on the destination floor in the waiting number management DB 122 (Sb45). When the waiting number is reset, the waiting situation management unit 1104 changes the car assignment flag of the user associated with the destination floor and the car assignment flag “NO” in the waiting situation management DB 123 to “YES”. (Sb46).
The above is the description of the second car allocation process.

When the second car assignment process ends, it is determined whether or not a predetermined process end time has been reached (Sb5). If the process end time has not been reached (NO in Sb5), step Sb1 is executed again. When the processing end time is reached (YES in Sb5), the car assignment process ends.
This completes the description of the car assignment process.

1-2-3. FIG. 14 is a flowchart illustrating an example of the waiting situation / number of people correction process. The waiting state / number of people correction process is executed in parallel with the floor demand specifying process and the car allocation process.

The car arrival monitoring unit 1111 of the notification device 10 refers to the operation status DB 124 and determines whether or not the car of the elevator E has arrived at the landing (Sc1). As a result of the determination, when the car arrives at the landing (YES in Sc1), the passenger identification unit 1112 identifies the user who takes the car taken by the landing camera 30 using the face authentication technology (Sc2). ). When the boarding user is specified, the flag correction unit 1113 refers to the destination floor management DB 125 and the user ID of the user specified in step Sc2 and the car determined to have arrived in step Sc1. The user ID of the prospective passenger is compared, and a flag correction instruction is generated based on the comparison result (Sc3). When the flag correction instruction is generated, the waiting state management unit 1104 changes the car assignment flag in the waiting state management DB 123 according to the generated flag correction instruction (Sc4). After the car assignment flag is changed, the waiting number correction unit 1114 refers to the destination floor management DB 125 and the number of users specified in Step Sc2 and the number of passengers who are determined to have arrived in Step Sc1. The number of persons is compared, and a waiting number correction instruction is generated based on the comparison result (Sc5). When the waiting number correction instruction is generated, the waiting number management unit 1103 changes the waiting number in the waiting number management DB 122 in accordance with the generated waiting number correction instruction (Sc6). After changing the waiting number, the car allocating unit 1107 deletes information on the destination floor and the passenger who is associated with the destination floor management DB 125 and whether or not it is determined that it has arrived in Step Sc1 (Sc7). When information such as the destination floor is deleted, it is determined whether or not a predetermined process end time has been reached (Sc8). If the process end time has not been reached (NO in Sc8), step Sc1 is executed again. If the processing end time is reached (YES in Sc8), the waiting state / number of people correction processing ends.
This completes the explanation of the waiting situation / number of people correction processing.

  According to the notification system 1 described above, in principle, when the number of waiting persons on the destination floor reaches a predetermined number, a car is assigned to the destination floor. Therefore, the transport capacity of each elevator E can be improved as compared with the case where a car is assigned to the destination floor without considering the waiting number. Further, in principle, since one car is assigned to one destination floor, the car does not stop on a plurality of floors, and the time required to send customers is shortened. In addition, when the waiting time of a user reaches a predetermined time, a car is assigned to the destination floor of the user even if the waiting number does not reach the predetermined number of users. Can be prevented from waiting excessively. At that time, the transportation capacity of the elevator E can be improved by sharing users with different destination floors. In addition, since the number and individuals of the users who actually get on the elevator E car are specified, the waiting number stored in the waiting number management DB 122 and the car assignment flag stored in the waiting state management DB 123 are corrected. It is possible to manage the waiting number and the waiting situation with higher accuracy. In addition, when the notification system 1 is introduced, it is not necessary to change the control algorithm for controlling the elevator E. Therefore, the introduction and adjustment of the system is easy.

2. Modifications The above embodiment may be modified as described below. One or more of the modifications described below may be combined with each other.

2-1. Modification 1
The notification system 1 is assumed to be installed in an elevator hall on the first floor of a 30-story building, but the number of floors and installation floors of the building are not limited thereto. In addition, the notification system 1 is assumed to distribute the destination floor to each car of the six elevators E, but the number of the elevators E is not limited to six. In addition, although the notification system 1 is assumed to distribute the destination floor to all the six cars, it is not always necessary to distribute the destination floor to all the cars. That is, a free group may be provided. In addition, the notification system 1 may be used to distribute the destination floor to each of the elevators for the lower floor and the middle floor instead of the elevator E for the higher floor.

2-2. Modification 2
The number and arrangement of the entrance camera 20, the landing camera 30, the display 40, and the speakers 50 are not limited to the example shown in FIG. The number and arrangement of each device may be appropriately selected according to the structure of the floor on which the notification system 1 is installed and the number of elevators. As an example, the hall camera 30 may be installed on the ceiling of the car of each elevator E instead of the ceiling of the elevator hall.

2-3. Modification 3
The user specifying unit 1101 specifies a user who intends to use the elevator E by using the face authentication technology, but the user specifying method is not limited to this. For example, biometric authentication other than face authentication may be used, or IC card authentication or password authentication may be used. Similarly, the passenger identification unit 1112 may also use biometric authentication, IC card authentication, or password authentication other than face authentication.

2-4. Modification 4
In the display screen of the display 40 illustrated in FIG. 8, the next destination floor to which each car is assigned is notified. However, the next and subsequent destination floors may be notified. FIG. 15 is a diagram illustrating an example of a display screen of the display 40 that notifies the next destination floor in addition to the next time. In the screen shown in the figure, for example, it is notified that the elevator car of “No. 13” is assigned to the destination floor “30F” next time and assigned to the destination floor “21F” next time. When the notification is made, each record stored in the destination floor management DB 125 is composed of information indicating the next time and the next time in addition to the car ID, the destination floor, and the user ID of the scheduled passenger. In addition, when the car arrival monitoring unit 1111 determines that the elevator E has arrived, the car allocating unit 1107 is information on the next destination floor and the expected passenger who are associated with the car in the destination floor management DB 125. Is carried forward as the next information.

2-5. Modification 5
In principle, the car allocating unit 1107 allocates one car to one destination floor, but one car may be allocated to a plurality of destination floors (in other words, a group of destination floors). . In that case, the waiting number management DB 122 manages the number of users waiting for the elevator E for each group on the destination floor. Note that the destination floor group may be composed of continuous floors or discontinuous floors.

2-6. Modification 6
The notification unit 1108 notifies the user that the car has been assigned to the destination floor using both the display 40 and the speaker 50, but may notify using only one of them. In addition to or instead of these, a notification may be given that a car has been assigned to the destination floor via a communication terminal such as a smartphone carried by the user. In that case, you may perform the said notification only with respect to the user to whom the car was allocated to the destination floor.

2-7. Modification 7
In the notification system 1, the number of users who actually get on the elevator E car and the number of individuals are specified and the waiting number and the car assignment flag are corrected. However, these processes may be omitted. When this modification is adopted, the number of waiting persons managed by the system and the accuracy of the car assignment flag are reduced, but the introduction of the system is facilitated because the installation of the hall camera 30 can be omitted.

2-8. Modification 8
The notification system 1 may preferentially assign a car to the destination floor of the user when the attribute of the user who intends to use the elevator E satisfies a predetermined condition. Here, the case where the user attribute satisfies a predetermined condition is, for example, a case where the user is a disabled person, an elderly person, or a pregnant woman, or the user is in a predetermined position. In this case, each record stored in the user information DB 121 is configured by user attributes in addition to the user ID, the feature point position data, and the belonging floor. In addition, the arithmetic processing device 11 further includes a function called an attribute specifying unit that specifies the destination floor of the user specified by the user specifying unit 1101 with reference to the user information DB 121. In addition to the user ID, the user identification time, the destination floor, and the car assignment flag, the waiting situation management unit 1104 stores the attribute identified by the attribute identification unit in the waiting situation management DB 123 in association with each other. In addition, the waiting state monitoring unit 1109 refers to the waiting state management DB 123 to determine whether any user attribute satisfies a predetermined condition. In addition, the destination floor determination unit 1110 performs the above-described destination floor determination process in order to determine a user to be shared with a user whose attribute is determined to satisfy a predetermined condition by the waiting state monitoring unit 1109.

2-9. Modification 9
A program for realizing each function included in the notification device 10 may be provided via a recording medium readable by the computer device. Here, the recording medium is, for example, a magnetic recording medium such as a magnetic tape or a magnetic disk, an optical recording medium such as an optical disk, a magneto-optical recording medium, or a semiconductor memory. In addition, this program may be provided via a network such as the Internet.

DESCRIPTION OF SYMBOLS 1 ... Notification system, 10 ... Notification apparatus, 11 ... Arithmetic processing apparatus, 12 ... Memory | storage device, 13 ... Input / output interface, 20 ... Entrance camera, 30 ... Landing camera, 40 ... Display, 50 ... Speaker, 121 ... User information DB: 122 ... Waiting number management DB, 123 ... Waiting state management DB, 124 ... Operation status DB, 125 ... Destination floor management DB, 1101 ... User specifying unit, 1102 ... Destination floor specifying unit, 1103 ... Waiting number management unit, DESCRIPTION OF SYMBOLS 1104 ... Wait status management part, 1105 ... Waiting number monitoring part, 1106 ... Car specification part, 1107 ... Car allocation part, 1108 ... Notification part, 1109 ... Wait situation monitoring part, 1110 ... Destination floor determination part, 1111 ... Car arrival monitoring , 1112 ... Passenger identification part, 1113 ... Flag correction part, 1114 ... Waiting number correction part, E ... Elevator, G ... Entrance gate

Claims (7)

A destination floor specifying unit for specifying a destination floor of each user who intends to use one of a plurality of elevators;
For each destination floor, a waiting number management unit that counts the number of users heading to the destination floor,
A car allocating unit that allocates one of the plurality of elevators to the first destination floor when the number of users heading to the first destination floor reaches a predetermined number; ,
A notification unit for notifying a user heading for the first destination floor that the first car has been assigned to the first destination floor ;
A waiting state monitoring unit for monitoring the waiting time of each user;
Among the users, when the waiting time of the first user heading to the second destination floor reaches a predetermined time, the number of users heading to the second destination floor is a predetermined number of people. A destination floor determination unit for specifying a third destination floor to which a second user different from the first user heads
With
The car assigning unit assigns any second car of the plurality of elevators to the second and third destination floors;
The notifying unit notifies the first and second users that the second car has been assigned to the second and third destination floors.
The notification apparatus characterized by the above-mentioned . A passenger number specifying unit for specifying the number of users who have boarded the first car;
The notification device according to claim 1, wherein the waiting number management unit subtracts the specified number of users from the number of users counted for the first destination floor. A passenger identifying unit that identifies a user who has boarded the first car;
The identified said user, the notification apparatus according to claim 1 or 2, characterized by further comprising a exclude wait state management unit from the monitored wait time by the waiting state monitor. An attribute specifying unit for specifying the attribute of each user;
If the attribute of the third user among the users satisfies a predetermined condition, the first of the plurality of elevators with respect to the fourth destination floor to which the third user goes Assign 3 baskets,
The notification unit according to any one of claims 1 to 3, characterized in that notifies the third user that allocated the third car to the fourth destination floor Notification device. A destination floor identification unit identifying a destination floor of each user who intends to use one of a plurality of elevators;
A waiting number management unit for each destination floor, counting the number of users heading to the destination floor;
When the number of users heading to the first destination floor reaches a predetermined number, the car allocating unit moves one of the plurality of elevators to the first destination floor. Assigning steps,
A step of notifying a user heading to the first destination floor that the notifying unit has assigned the first car to the first destination floor ;
A waiting state monitoring unit monitoring the waiting time of each user;
The destination floor determination unit is a user who goes to the second destination floor when the waiting time of the first user heading to the second destination floor among the respective users reaches a predetermined time. Specifying a third destination floor to which a second user different from the first user heads when the number of people does not reach a predetermined number
The step of allocating the second car of any of the plurality of elevators to the second and third destination floors;
A notification method comprising: notifying the first and second users that the notification unit has allocated the second car to the second and third destination floors. Computer
A destination floor specifying unit for specifying a destination floor of each user who intends to use one of a plurality of elevators;
For each destination floor, a waiting number management unit that counts the number of users heading to the destination floor,
A car allocating unit that allocates one of the plurality of elevators to the first destination floor when the number of users heading to the first destination floor reaches a predetermined number; ,
A notification unit for notifying a user heading for the first destination floor that the first car has been assigned to the first destination floor ;
A waiting state monitoring unit for monitoring the waiting time of each user;
Among the users, when the waiting time of the first user heading to the second destination floor reaches a predetermined time, the number of users heading to the second destination floor is a predetermined number of people. A destination floor determination unit for specifying a third destination floor to which a second user different from the first user heads
Is a program for functioning as
The car assigning unit assigns any second car of the plurality of elevators to the second and third destination floors;
The notifying unit notifies the first and second users that the second car has been assigned to the second and third destination floors.
A program characterized by that . A notification system comprising an imaging device, a notification device, and an output device,
The photographing device photographs each user who intends to use one of a plurality of elevators,
The notification device includes:
A destination floor specifying unit for specifying a destination floor of each user specified by analyzing an image photographed by the photographing device;
For each destination floor, a waiting number management unit that counts the number of users heading to the destination floor,
A car allocating unit that allocates one of the plurality of elevators to the first destination floor when the number of users heading to the first destination floor reaches a predetermined number; ,
A notification unit for notifying a user heading for the first destination floor via the output device that the first car has been assigned to the first destination floor ;
A waiting state monitoring unit for monitoring the waiting time of each user;
Among the users, when the waiting time of the first user heading to the second destination floor reaches a predetermined time, the number of users heading to the second destination floor is a predetermined number of people. A destination floor determination unit for specifying a third destination floor to which a second user different from the first user heads
With
The car assigning unit assigns any second car of the plurality of elevators to the second and third destination floors;
The notifying unit notifies the first and second users that the second car has been assigned to the second and third destination floors .

Images