Elevator management system, control method

Abstract

To improve convenience in elevator systems that include both shuttle elevators and local elevators. [Solution] An elevator management system (100) comprising a shuttle elevator (3) and a local elevator (7) includes an acquisition unit that acquires an image showing the face of a user who is scheduled to board or is currently boarding the shuttle elevator; an authentication unit that authenticates the user based on the acquired image; a request unit that requests a first local group management control device (5), which manages local elevators whose service floor includes the destination floor associated with the authenticated user, to register the destination floor call of the authenticated user; and an assignment unit that assigns a local elevator whose service floor includes the destination floor of the authenticated user to the destination floor call of the authenticated user.

Description

Technical Field

[0001] The present invention relates to an elevator management system including a shuttle elevator and a local elevator, and a control method for the elevator management system.

Background Art

[0002] Conventionally, an elevator system that enables passengers to transfer between a shuttle elevator and a local elevator has been known (for example, Patent Document 1). The shuttle elevator shuttles between the main lobby floor and the transfer floor. Also, passengers can move to a lower or upper floor than the transfer floor by transferring to a local elevator that can stop at each floor.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a conventional elevator system, after getting off the car of the shuttle elevator at the transfer floor, passengers needed to register a destination floor call for using the local elevator again.

[0005] One aspect of the present invention aims to improve the convenience in an elevator system including a shuttle elevator and a local elevator.

Means for Solving the Problems

[0006] To solve the above problems, an elevator management system according to one aspect of the present invention comprises: a shuttle elevator having one or more units that shuttle between a lobby floor and a transfer floor; a plurality of local elevators having one or more units that operate between the transfer floor and an upper or lower floor of the transfer floor, with at least some service floors different from each other; and a plurality of management devices that manage each of the plurality of local elevators, wherein the elevator management system comprises: an acquisition unit that acquires an image showing the face of a user who is scheduled to board or is currently boarding the shuttle elevator; an authentication unit that authenticates the user based on the acquired image; a request unit that requests the management device that manages the local elevators whose service floors include the destination floor associated with the authenticated user authenticated by the authentication unit to register the destination floor call of the authenticated user; and an assignment unit that assigns the front symbol unit of the local elevator whose service floors include the destination floor of the authenticated user to the destination floor call of the authenticated user.

[0007] To solve the above problems, a control method according to one aspect of the present invention is a control method for an elevator management system comprising: a shuttle elevator having one or more units that shuttle between a lobby floor and a transfer floor; a plurality of local elevators having one or more units that operate between the transfer floor and an upper or lower floor of the transfer floor, with at least some service floors different from each other; and a plurality of management devices that manage each of the plurality of local elevators, the control method comprising: an acquisition step of acquiring an image showing the face of a user who is scheduled to board or is currently boarding the shuttle elevator; an authentication step of authenticating the user based on the acquired image; a request step of requesting the management device that manages the local elevators whose service floors include the destination floor associated with the authenticated user authenticated in the authentication step to register the destination floor call of the authenticated user; and an assignment step of assigning the front symbol unit of the local elevators whose service floors include the destination floor of the authenticated user to the destination floor call of the authenticated user.

[0008] Each aspect of the present invention may be implemented by a computer, in which case the control program for the elevator management system that implements the elevator management system by operating the computer as each part (software element) of the elevator management system, and the computer-readable recording medium on which the program is recorded, also fall within the scope of the present invention. [Effects of the Invention]

[0009] According to one aspect of the present invention, the convenience of an elevator system comprising a shuttle elevator and a local elevator can be improved. [Brief explanation of the drawing]

[0010] [Figure 1] This is a schematic diagram showing an example of the arrangement of shuttle elevators and local elevators in a building to which the elevator management system according to the present invention is applied. [Figure 2] This is a block diagram showing the schematic configuration of an elevator management system according to Embodiment 1 of the present invention. [Figure 3] Figure 2 is a block diagram showing the configuration of the shuttle management system. [Figure 4] This is a floor plan showing an example of a landing on the lobby floor. [Figure 5] This is a floor plan showing an example of a transfer level platform. [Figure 6] This figure shows an example of a user database. [Figure 7] This figure shows an example of a database of planned requests. [Figure 8] This figure shows an example of a screen displayed on the first display unit. [Figure 9] Figure 2 is a block diagram showing the configuration of the local management system. [Figure 10] This flowchart shows an example of the processing flow performed by a shuttle elevator control system. [Figure 11]It is a flowchart showing an example of the process performed by the shuttle elevator control device. [Figure 12] It is a sequence diagram showing an example of the process performed by the shuttle group management control device and the local group management control device. [Figure 13] It is a flowchart showing an example of the process performed by the shuttle elevator control device. [Figure 14] It is a block diagram showing the schematic configuration of the elevator management system according to Embodiment 2 of the present invention. [Figure 15] It is a block diagram showing the configuration of the shuttle management system shown in FIG. 14. [Figure 16] It is a block diagram showing the configuration of the local management system shown in FIG. 14. [Figure 17] It is a block diagram showing the schematic configuration of the elevator management system according to Embodiment 3 of the present invention. [Figure 18] It is a block diagram showing the configuration of the shuttle management system shown in FIG. 17. [Figure 19] It is a block diagram showing the configuration of the local management system shown in FIG. 17. [Figure 20] It is a block diagram showing the schematic configuration of the elevator management system according to Embodiment 4 of the present invention. [Figure 21] It is a block diagram showing the configuration of the shuttle management system shown in FIG. 20. [Figure 22] It is a block diagram showing the configuration of the local management system shown in FIG. 20. [Figure 23] It is a block diagram showing the schematic configuration of the elevator management system according to Embodiment 5 of the present invention. [Figure 24] It is a block diagram showing the configuration of the shuttle management system shown in FIG. 23.

Mode for Carrying Out the Invention

[0011] 〔Embodiment 1〕 <Overview of Elevator Management System 100> The following describes in detail one embodiment of the present invention. Figure 1 is a schematic diagram showing an example of the arrangement of a shuttle elevator 3 and a local elevator 7 in a building to which the elevator management system 100 according to the present invention is applied. In Figure 1, the squares shown by solid lines indicate the service floors to which the shuttle elevator 3 or the local elevator 7 can stop, respectively. As shown in Figure 1, the shuttle elevator 3 operates as a shuttle between the lobby floor and the transfer floor, and the local elevator 7 operates between the transfer floor and the floor above or below the transfer floor.

[0012] Figure 2 is a block diagram illustrating the schematic configuration of the elevator management system 100 according to Embodiment 1 of the present invention. The elevator management system 100 comprises a shuttle elevator 3 and a local elevator 7, and is a system that manages the operation of these elevators in response to calls from users of these elevators.

[0013] As shown in Figure 2, the elevator management system 100 includes a shuttle management system 10 for managing the shuttle elevator 3 and a local management system 20 for managing the local elevator 7. In the elevator management system 100, the shuttle management system 10 manages at least one shuttle elevator 3.

[0014] Figure 4 is a plan view showing an example of a landing on the lobby floor. In the following explanation, we will use as an example a configuration in which the shuttle management system 10 manages three shuttle elevators 3, numbered 10 to 12, as shown in Figure 4.

[0015] Furthermore, as shown in Figure 2, the elevator management system 100 includes a plurality of local elevators 7 and a plurality of local management systems 20. In the elevator management system 100, each of the plurality of local management systems 20 manages at least one local elevator 7. Hereinafter, a local management system 20 that manages at least one local elevator 7 (the first local elevator 7) will be referred to as the "first local management system 20". Also, a local management system 20 that manages at least one local elevator 7 (the second local elevator 7) that is different from the first local elevator 7 will be referred to as the "second local management system 20" to distinguish it from the first local management system 20. As shown in Figure 1, in the elevator management system 100, the first local elevator 7 and the second local elevator 7 have at least some service floors that differ from each other. Hereinafter, when the first local management system 20 and the second local management system 20 are not distinguished, they will simply be referred to as the "local management system 20". Also, when the first local elevator 7 and the second local elevator 7 are not distinguished, they will simply be referred to as the "local elevator 7".

[0016] In the elevator management system 100 according to the present invention, the shuttle management system 10 acquires an image showing the face of a user who is scheduled to board or is currently boarding the shuttle elevator 3, and authenticates the user based on the acquired image. The shuttle management system 10 then requests the local management system 20, which manages local elevators 7 whose service floors include the destination floor associated with the authenticated user, to register the destination floor call of the authenticated user. The local management system 20 assigns the unit number of the local elevator 7 under its management to the destination floor call of the authenticated user requested by the shuttle management system 10.

[0017] Traditionally, users had to register their call for the local elevator 7 at the transfer floor after disembarking from the shuttle elevator 3's car 31. In contrast, with the above configuration, an image of the user who is scheduled to board or is currently boarding the shuttle elevator 3 is acquired, and authentication is performed based on that image. Then, a local elevator 7 unit is assigned to the authenticated user's destination floor call. As a result, after disembarking from the shuttle elevator 3's car 31, the authenticated user can travel to their destination floor by boarding the assigned local elevator 7 unit. Thus, with the above configuration, users of the shuttle elevator 3 do not need to register their destination floor call for the local elevator 7 at the transfer floor, thus improving convenience.

[0018] Figure 5 is a plan view showing an example of a transfer floor landing. For the sake of simplicity, the following explanation will use an example where the elevator management system 100 is equipped with two local management systems 20, and each of the multiple local management systems 20 manages six local elevators 7, as shown in Figure 1. The first local management system 20 manages local elevators 7 from A to F (the first local elevator 7), and the second local management system 20 manages local elevators 7 from G to L (the second local elevator 7). Furthermore, the following explanation will use an example where the lobby floor is the 1st floor, the transfer floor is the 10th floor, the service floors for the first local elevator 7 are from the 10th to the 20th floor, and the service floors for the second local elevator 7 are from the 10th and 21st to the 30th floor. The service floors for the first local elevator 7 are also referred to as the lower floors, and the service floors for the second local elevator 7 are also referred to as the upper floors.

[0019] However, the configuration of the elevator management system 100 is not limited to this, and it may include three or more local management systems 20. For example, the elevator management system 100 may include a third local elevator 7 (units M to R in Figure 5) whose service floors differ from those of the first local elevator 7 and the second local elevator 7 in at least some respects. In this case, the elevator management system 100 includes a third local management system 20 that manages the third local elevator 7. If the service floors of the third local elevator 7 are higher than those of the first local elevator 7 and the second local elevator 7, the service floors of the first local elevator 7 may be referred to as low floors, the service floors of the second local elevator 7 as middle floors, and the service floors of the third local elevator 7 as high floors.

[0020] <Shuttle Management System 10> Figure 3 is a block diagram showing the configuration of the shuttle management system 10. As shown in Figures 2 and 3, the shuttle management system 10 comprises a shuttle group management control device 1, a shuttle elevator control device 2, a shuttle elevator 3, and an input device 4.

[0021] (Input device 4) Input device 4 is a device such as a button that users use to register a call for the shuttle elevator 3. For example, as shown in Figures 4 and 5, input devices 4 may be installed on the lobby floor and the transfer floor, respectively. If the transfer floor is a higher floor than the lobby floor, the input device 4 installed on the lobby floor may have a button indicating the upward direction, and the input device 4 installed on the transfer floor may have a button indicating the downward direction.

[0022] Input device 4 can accept operations from users. An operation is, for example, pressing a button on input device 4. When input device 4 accepts an operation from a user, it transmits a signal containing its own identification information to the shuttle group management control device 1. As a result, the shuttle elevator 3 landing call is registered in the shuttle group management control device 1.

[0023] (Shuttle elevator control device 2 and shuttle elevator 3) The shuttle elevator control device 2 is a device that controls the operation of the shuttle elevator 3. The shuttle elevator 3 is an elevator that operates in a shuttle fashion based on the control of the corresponding shuttle elevator control device 2. As shown in Figure 3, the shuttle elevator 3 comprises a car 31, an imaging unit 32, and a first display unit 33. The car 31 is capable of accommodating passengers and operates in a shuttle fashion according to the control of the elevator control unit 211 of the shuttle elevator control device 2. The imaging unit 32 is a device such as a camera installed in the car 31, and outputs captured images to the shuttle elevator control device 2. The imaging unit 32 is installed in a position that allows it to capture the faces of passengers inside the car 31 and passengers outside the car 31 who are attempting to board the car 31 from the landing. There may be one or more imaging units 32 installed in one car 31. The first display unit 33 is a device such as a display that can display various screens according to the control of the display control unit 214. The first display unit 33 is installed on the wall inside the elevator car 31 or in a position where the screen displayed to the user inside the elevator car 31 can be seen.

[0024] As shown in Figure 3, the shuttle elevator control device 2 comprises a control unit 21 and a storage unit 22. The control unit 21 comprises an elevator control unit 211, an acquisition unit 212, an authentication unit 213, and a display control unit 214. The storage unit 22 stores the user DB (database) 221 and the request schedule DB (database) 222. Figure 6 shows an example of the user DB 221. The user DB 221 is a database in which authenticated users of the shuttle elevator 3 are registered. The user DB 221 is also called an array TBL. As shown in Figure 6, in the user DB 221, serial numbers (numbers) and authenticated user identification information (user IDs) are stored in association. The storage unit 22 stores a separate user DB 221 for each shuttle elevator unit 3.

[0025] The Request Schedule DB222 is a database in which request schedule information for each shuttle elevator unit 3 is registered. The request schedule information is information regarding the schedule for requesting the allocation of a local elevator unit 7 to the local group management control device 5. The Request Schedule DB222 is also called the Array DES. Figure 7 shows an example of the Request Schedule DB222. As shown in Figure 7, the Request Schedule DB222 associates the building floor (destination floor) with the number of authenticated users (number of people) indicating the number of people whose destination floor is that floor. The storage unit 22 stores the Request Schedule DB222 for each shuttle elevator unit 3.

[0026] The elevator control unit 211 controls the operation of the shuttle elevator 3. When the elevator control unit 211 receives information from the shuttle group management control device 1 that instructs the shuttle operation, including information indicating the departure floor, it operates the shuttle elevator 3 based on that information. Specifically, the elevator control unit 211 moves the car 31 of the shuttle elevator 3 to the departure floor included in the received information and opens the doors of the car 31 at the departure floor. After a predetermined time has elapsed since the doors were opened, the elevator control unit 211 closes the doors of the car 31 and moves the car 31 to the floor of the lobby floor and the transfer floor that is different from the departure floor.

[0027] The acquisition unit 212 acquires images (face images) showing the faces of users who are scheduled to board or are currently boarding the shuttle elevator 3. The following describes the process by which the acquisition unit 212 acquires user face images. First, the acquisition unit 212 acquires images captured by the imaging unit 32. While the doors of the shuttle elevator car 31 are open on the lobby floor, the acquisition unit 212 extracts the figures of people from the acquired images. If the extracted person is performing an action that indicates they are scheduled to board the shuttle elevator 3, the acquisition unit 212 identifies the extracted person as a user scheduled to board the shuttle elevator 3 and acquires the face image of that user.

[0028] An action indicating that someone is planning to board the shuttle elevator 3 is, for example, the action of a person in the image walking from the landing towards the elevator car 31. If the acquisition unit 212 extracts a person approaching the elevator car 31 with its doors open from the landing, that person may be considered a user planning to board the shuttle elevator 3.

[0029] Furthermore, after the doors of the shuttle elevator car 31 located on the lobby floor close, the acquisition unit 212 performs a process to extract users currently riding the shuttle elevator 3 based on the images acquired from the imaging unit 32, until a predetermined time has elapsed. Specifically, the acquisition unit 212 extracts the figures of people present inside the car 31 from the acquired images. The acquisition unit 212 identifies the extracted individuals as users scheduled to ride the shuttle elevator 3 and acquires their facial images.

[0030] Shuttle elevator 3 operates as a shuttle between the lobby floor and the transfer floor. Therefore, the travel time from departing one floor of the lobby floor or transfer floor to arriving at the other floor is generally constant. Accordingly, the time after the doors of the shuttle elevator car 31 located on the lobby floor close, when a first predetermined time has elapsed, can be rephrased as the time before the second predetermined time before arriving at the transfer floor. The acquisition unit 212 may perform the process of acquiring the user's facial image after the doors of the shuttle elevator car 31 located on the lobby floor close, until a predetermined time before the car 31 arrives at the transfer floor.

[0031] The acquisition unit 212 outputs the acquired user's face image to the authentication unit 213. Note that if the acquisition unit 212 has acquired the face images of all users who are riding in the shuttle elevator car 31 after the doors of the car 31 have closed, it may terminate the process of acquiring the user's face image even if a predetermined time has not elapsed.

[0032] The authentication unit 213 authenticates the user based on the image acquired by the acquisition unit 212. When the authentication unit 213 receives the user's facial image from the acquisition unit 212, it sends a request for information to the shuttle group management control device 1. A request for information is information to request the shuttle group management control device 1 to provide the information contained in the first registrant DB 123. When the reception unit 111 of the shuttle group management control device 1 receives the request for information, it sends the information contained in the first registrant DB 123 in the storage unit 12 to the shuttle elevator control device 2.

[0033] The first registrant DB123 stored in the shuttle group management control device 1 is a database that stores information used for user authentication. The first registrant DB123 stores, for each registrant, associated information such as the registrant's identification information (user ID), an image showing the registrant's face, and information indicating the registrant's default destination floor. The default destination floor is the floor to which the registrant travels using the local elevator 7 from the transfer floor.

[0034] The authentication unit 213 identifies the registered user based on the image showing the registered user's face registered in the first registered user DB 123 and the received face image. If the authentication unit 213 can identify the registered user based on the received face image, it determines that the user's authentication was successful. On the other hand, if the authentication unit 213 cannot identify the registered user based on the received face image, it determines that the user's authentication failed. If the user's authentication is successful, the authentication unit 213 extracts the identification information of the identified registered user and the default destination floor associated with that identification information, and identifies them as the identification information and destination floor of the authenticated user.

[0035] If the authentication unit 213 successfully authenticates a user, it checks for duplicate users and determines whether a request for a destination floor call for the authenticated user has already been registered. If the authentication unit 213 has not yet registered a request for a destination floor call for the authenticated user, it registers the request for a destination floor call for the authenticated user.

[0036] Specifically, if user authentication is successful, the authentication unit 213 refers to the user database 221. The authentication unit 213 determines whether the user identification information included in the authenticated user information is already registered in the user database 221. If the user identification information is not already registered in the user database 221, the authentication unit 213 determines that a request for calling the destination floor for the authenticated user has not yet been registered. In this case, the request unit 112 registers a new request for calling the destination floor for the authenticated user. Specifically, the authentication unit 213 increments the number of people indicated by the number of people information corresponding to the authenticated user's destination floor in the request schedule database 222 by 1.

[0037] On the other hand, if the authentication user's identification information is already registered in the user database 221, the authentication unit 213 determines that a scheduled request for a destination floor call for the authentication user has already been registered. In this case, the authentication unit 213 does not register a new scheduled request for a destination floor call for the authentication user.

[0038] After a predetermined time has elapsed since the doors of elevator car 31 of shuttle elevator 3 closed, the authentication unit 213 transmits the information included in the registered request schedule to the shuttle group management control device 1. Specifically, the authentication unit 213 transmits an assignment request to the shuttle group management control device 1 that associates the floor indicating the destination floor registered in the request schedule DB 222 with the number of authenticated users who will use that floor as their destination floor. The authentication unit 213 transmits an assignment request for the floor to which the number of users indicated as 1 or more in the request schedule DB 222 is associated. Once the assignment request is transmitted from the authentication unit 213 to the shuttle group management control device 1, the shuttle group management control device 1 requests the appropriate local group management control device 5 to assign the authenticated users to their destination floor calls.

[0039] Let's explain using the example shown in Figure 7, where the information is registered in the Request Schedule DB 222. In this case, the authentication unit 213 associates information indicating the destination floor as the 11th floor with information indicating the number of authenticated users as 1 and transmits it to the shuttle group management control device 1. The authentication unit 213 also associates information indicating the destination floor and information indicating the number of authenticated users with information indicating the 12th and 30th floors and transmits them to the shuttle group management control device 1. On the other hand, the number of authenticated users with the 13th floor as their destination floor is 0. In this case, the authentication unit 213 does not transmit an assignment request with the 13th floor as the destination floor.

[0040] The display control unit 214 causes the allocation result from the allocation unit 511 to be displayed on the first display unit 33 inside the car 31 of the shuttle elevator 3. Figure 8 is a diagram showing an example of a screen displaying the allocation result shown on the first display unit 33. As shown in Figure 8, the display control unit 214 displays the allocated elevator numbers for each destination floor of the local elevator 7 on the first display unit 33.

[0041] After the authentication unit 213 sends an assignment request to the shuttle group management control device 1, the display control unit 214 receives information from the shuttle group management control device 1 indicating the assignment result based on the assignment request. This information associates information indicating the destination floor of the authenticated user with information indicating the assigned shuttle unit for the authenticated user's destination floor call. When the display control unit 214 receives the assignment result information, it displays the assignment result information on the first display unit 33. If the display control unit 214 receives new assignment result information while the first display unit 33 is already displaying the assignment result information, it updates the screen displayed on the first display unit 33 to display the newly received assignment result information in addition to the already displayed assignment result information.

[0042] When elevator car 31 arrives at the transfer floor, the display control unit 214 terminates the display of the allocation result information by the first display unit 33. The timing at which the display control unit 214 terminates the display of the allocation result information may be after a predetermined time (for example, 5 seconds) has elapsed since elevator car 31 arrived at the transfer floor.

[0043] With the above configuration, authenticated users can identify their assigned elevator car 31 within the elevator car 31 of the shuttle elevator 3 before transferring to the local elevator 7. This allows authenticated users to make transfers smoothly, improving convenience. Furthermore, if, for example, the destination floor for each authenticated user is displayed on the first display unit 33, it may take time for the authenticated user to find their assigned elevator car. In contrast, with the above configuration, the assigned elevator car is displayed for each destination floor on the first display unit 33. This simplifies the display on the first display unit 33, making it easier for authenticated users to identify the elevator car they should board.

[0044] (Shuttle group management control device 1) The shuttle group management control device 1 is a device that manages the shuttle elevators 3. The shuttle group management control device 1 also requests the local group management control device 5 to assign a local elevator 7 to a user's destination floor call and provides the assignment result to the shuttle elevator control device 2. As shown in Figure 3, the shuttle group management control device 1 comprises a control unit 11 and a storage unit 12. The control unit 11 comprises a reception unit 111, an authentication unit 213, a request unit 112, and an assignment result acquisition unit 113. The storage unit 12 stores the shuttle DB (database) 121, the local DB (database) 122, and the first registrant DB (database) 123.

[0045] Shuttle DB121 is a database that stores information about the equipment installed in Shuttle Elevator 3. In Shuttle DB121, identification information indicating the unit number of Shuttle Elevator 3, identification information of the imaging unit 32 installed in that unit, and identification information of the first display unit 33 installed in that unit are stored in association for each unit.

[0046] Local DB122 is a database that stores information to identify the local group control device 5 to which the first allocation request is sent. Local DB122 stores identification information for each local group control device 5 and information indicating the service floor of the local elevator 7 managed by that local group control device 5, with these information associated with each local group control device 5.

[0047] The first registrant DB123 is a database that stores information used for user authentication. In the first registrant DB123, the registrant's identification information (user ID), an image showing the registrant's face, and information indicating the registrant's default destination floor are associated and stored for each registrant.

[0048] The reception unit 111 receives landing calls from users to use the shuttle elevator 3. When the input device 4 is operated by the user, the reception unit 111 receives a signal from the input device 4 that includes identification information for its own device. Upon receiving this signal, the reception unit 111 assigns a shuttle elevator 3 unit to the user's landing call, designating the floor on which the operated input device 4 is installed as the user's boarding floor, and registers the user's landing call. The reception unit 111 transmits information to the shuttle elevator control device 2, which controls the assigned unit, instructing it to operate a shuttle service with the boarding floor as the departure floor. As a result, the assigned shuttle elevator 3 unit moves to the user's departure floor and then operates a shuttle service between the lobby floor and the transfer floor.

[0049] Furthermore, when the reception unit 111 receives a request from the shuttle elevator control device 2, it transmits the information contained in the first registered user DB 123 of the storage unit 12 to the shuttle elevator control device 2. This allows the shuttle elevator control device 2 to authenticate the user.

[0050] The request unit 112 requests the local group control device 5 (management device), which manages the local elevator 7 whose service floor includes the destination floor associated with the authenticated user authenticated by the authentication unit 213, to register the destination floor call of the authenticated user.

[0051] The request unit 112 transmits the number of users for each destination floor of a single shuttle elevator 3 to the local group management control device 5. After a predetermined time has elapsed since the doors of the car 31 of the shuttle elevator 3 closed, the request unit 112 receives an allocation request from the shuttle elevator control device 2 that controls the elevator. The allocation request is information that associates information indicating the floor that is the destination floor with information indicating the number of authenticated users whose destination floor is that floor. Upon receiving the allocation request, the request unit 112 refers to the local DB 122 and identifies a local elevator 7 that includes the floor included in the allocation request as a service floor. The request unit 112 transmits a first allocation request to the local group management control device 5 that manages the identified local elevator 7. The first allocation request is information that associates information indicating the floor that is the destination floor with information indicating the number of authenticated users whose destination floor is that floor. According to the above configuration, it is possible to request the destination floors of authenticated users who are currently using one shuttle elevator unit 3 all at once.

[0052] The allocation result acquisition unit 113 receives information from the local group management control device 5 indicating the allocation result based on the first allocation request. Upon receiving this information, the allocation result acquisition unit 113 transmits the information indicating the allocation result to the shuttle elevator control device 2, which is the source of the allocation request. As a result, the first display unit 33 inside the car 31 of the shuttle elevator 3 displays information indicating the destination floor of the authenticated user and information indicating the allocated elevator unit corresponding to that destination floor, in association with each other.

[0053] <Local Management System 20> Figure 9 is a block diagram showing the configuration of the local management system 20. As shown in Figures 2 and 9, the first local management system 20 comprises a first local group management control device 5, a first local elevator control device 6, a first local elevator 7, and a destination floor registration device 8. The second local management system 20 has the same configuration as the first local management system 20, except that the service floors of the second local elevator 7 under its management differ from those of the first local elevator 7. Hereafter, when the configurations of the first local management system 20 and the second local management system 20 are not distinguished, the terms "first" and "second" will be omitted in each configuration.

[0054] (Destination floor registration device 8) The destination floor registration device 8 is a device used by users to register destination floor calls. In response to input from the user, the destination floor registration device 8 requests the corresponding local group management control device 5 to register the destination floor call.

[0055] Each destination floor registration device 8 installed on floors other than transfer floors corresponds to a local group control device 5 that manages the local elevator 7 that includes the floor on which it is installed as a service floor, and is connected to the corresponding local group control device 5. For example, destination floor registration devices 8 installed on floors from the 11th to the 20th floors correspond to a first local group control device 5 that manages a first local elevator 7 that includes floors from the 11th to the 20th floors as service floors. Destination floor registration devices 8 may be installed at the landings of multiple floors. Furthermore, multiple destination floor registration devices 8 may be installed on a single floor.

[0056] As shown in Figure 9, the destination floor registration device 8 includes a reading unit 81 and a second display unit 82. The reading unit 81 and the second display unit 82 may be configured as separate devices housed in a single housing, or they may be configured as a single integrated device. In this embodiment, the configuration in which the reading unit 81 and the second display unit 82 are separate devices and these devices are housed in a single housing will be described as an example. The reading unit 81 is a reader device capable of reading user identification information. The reading unit 81 reads user identification information from an employee ID card, membership card, or terminal such as terminal device 50 that stores the user's identification information. When the reading unit 81 reads the user's identification information, it transmits a second assignment request, which includes the identification information of its own device and information indicating the read identification information, to the corresponding local group management control device 5.

[0057] The second display unit 82 is a display device such as a display. When a user's destination floor call is registered in the local group management control device 5, the second display unit 82 receives information from the local group management control device 5 indicating the assignment result for the destination floor call. This information includes information indicating the user's destination floor and the assigned elevator unit for the destination floor call. The second display unit 82 displays the received information.

[0058] The destination floor registration device 8 installed on the transfer floor is connected to all local group control devices 5. As shown in Figure 5, multiple destination floor registration devices 8 may be installed on the transfer floor. The reading unit 81 of the destination floor registration device 8 installed on the transfer floor is a reader device capable of reading user identification information and is connected to all local group control devices 5. When the reading unit 81 reads the user's identification information, it transmits a second assignment request, which includes its own identification information and information indicating the read identification information, to either the first local group control device 5 or the second local group control device 5. For example, the reading unit 81 transmits the second assignment request to the first local group control device 5. If the default destination floor of the registrant corresponding to the identification information is included in the service floor of the first local elevator 7, the user's destination floor call is registered in the first local group control device 5. If the default destination floor of the registered user corresponding to the identification information is not included in the service floors of the first local elevator 7, the reading unit 81 receives information from the first local group control device 5 indicating that the destination floor call cannot be registered. Upon receiving this information, the reading unit 81 transmits a second assignment request to the second local group control device 5. If the default destination floor of the registered user corresponding to the identification information is included in the service floors of the second local elevator 7, the user's destination floor call is registered in the second local group control device 5.

[0059] The second display unit 82 is a display device such as a display. Similar to the reading unit 81, the second display unit 82 is connected to all local group control devices 5. When a user's destination floor call is registered in the local group control device 5, the second display unit 82 receives information from the local group control device 5 indicating the assignment result for the destination floor call. This information includes information indicating the user's destination floor and the assigned elevator number for the destination floor call. Upon receiving this information, the second display unit 82 displays the received information. This allows the user to determine which local elevator 7 they should board.

[0060] As described above, users can register their destination floor request not only by using the shuttle elevator 3, but also by using the destination floor registration device 8.

[0061] (Local elevator control device 6 and local elevator 7) The local elevator control device 6 controls the operation of the local elevator 7. As shown in Figure 9, the local elevator control device 6 includes a control unit 61. The control unit 61 receives a call request from the local group control device 5, which is connected to the local elevator control device 6, and includes information indicating the departure floor and destination floor. Upon receiving a call request, the control unit 61 registers the user's destination floor call based on the call request. Based on the registered destination floor call, the control unit 61 controls the movement of the car of the local elevator 7 to the user's departure floor and destination floor, and the opening and closing of the car doors. If the control unit 61 receives information from the local group control device 5 instructing an extension of the door opening time, it extends the door opening time of the car 31. The local elevator 7 moves between floors and opens and closes its doors according to the control of the local elevator control device 6.

[0062] (Local group management control device 5) Multiple local group management control devices 5 are management devices that manage each of the multiple local elevators 7. One local group management control device 5 may manage multiple local elevators 7 as shown in Figure 5, or it may manage only one local elevator 7. As shown in Figure 9, the local group management control device 5 comprises a control unit 51 and a storage unit 52. The control unit 51 comprises an allocation unit 511. The storage unit 52 stores the second registrant DB (database) 521 and the registrant device DB (database) 522.

[0063] The second registrant DB521 is a database in which the registrant's identification information (user ID) and information indicating the registrant's default destination floor are associated for each registrant. The second registrant DB521 is used to identify the destination floor of a user who has requested registration of a destination floor call using the destination floor registration device 8.

[0064] In the registration device DB522, the identification information of the reading unit 81 of the destination floor registration device 8 is associated with the identification information of the second display unit 82 corresponding to the reading unit 81, and information indicating the floor on which the destination floor registration device 8 is installed.

[0065] The allocation unit 511 assigns the local elevator 7 that includes the destination floor of the authenticated user in its service floor to the authenticated user's destination floor call. The allocation unit 511 assigns the local elevator 7 based on the number of people information.

[0066] Once a user is authenticated, the request unit 112 of the shuttle group control device 1 identifies the local group control device 5 that manages the local elevator 7 whose service floor includes the authenticated user's destination floor. The allocation unit 511 of the identified local group control device 5 receives a first allocation request from the request unit 112, requesting allocation for the authenticated user's destination floor call.

[0067] The first allocation request includes information indicating the destination floor of an authenticated user using one of the shuttle elevators 3, and information indicating the number of people for each destination floor. When the allocation unit 511 receives the first allocation request, it assigns the most suitable local elevator 7 to the destination floor of the authenticated user based on the first allocation request, the registered destination floor call, and the capacity of each local elevator 7. The allocation unit 511 assigns authenticated users using one of the shuttle elevators 3 so that authenticated users with the same destination floor use the same local elevator 7 whenever possible.

[0068] According to the above configuration, requests for destination floors from authenticated users currently using one shuttle elevator 3 are processed collectively. The allocation unit 511 uses the number of authenticated users for each destination floor to assign elevators so that users going to the same floor use the same elevator as much as possible. This reduces the possibility of a decrease in the convenience of the local elevator 7.

[0069] When the allocation unit 511 assigns an elevator to a destination floor call with a single floor as the destination floor, it registers the destination floor call. Specifically, the allocation unit 511 stores the departure floor, destination floor, and the number of passengers corresponding to that destination floor in the storage unit 52. The allocation unit 511 also transmits a call request, including information indicating the departure floor and destination floor, to the local elevator control device 6 that controls the assigned local elevator 7. If the first allocation request includes information indicating multiple destination floors, the allocation unit 511 may register the destination floor call and transmit a call request each time it assigns an elevator to a destination floor call with a single floor as the destination floor. If the allocation unit 511 assigns multiple elevators to a destination floor call with a single floor as the destination floor, it transmits a call request to each of the local elevator control devices 6 that control the multiple elevators.

[0070] Furthermore, if the allocation unit 511 has made an allocation based on the first allocation request, it transmits information to the local elevator control device 6, which controls the allocated elevator, instructing it to extend the door-open time along with the call request. The local elevator control device 6 may extend the door-open time of the car 31 so that the door-open state is maintained at least until the shuttle elevator 3 arrives at the transfer floor.

[0071] The allocation by the allocation unit 511 will be explained using the example of a case where each elevator in the first local elevator 7 has a capacity of 15 people. In this case, when the first allocation request is received indicating that there are 10 authenticated users whose destination floor is the 12th floor, the allocation unit 511 identifies elevators with 10 or more available seats. The allocation unit 511 assigns the identified elevators to the destination floor calls of the 10 authenticated users whose departure floor is the transfer floor and whose destination floor is the 12th floor. If there are no elevators with 10 or more available seats, the allocation unit 511 assigns multiple elevators to the destination floor calls of the authenticated users. Here, the allocation unit 511 makes the allocation in a way that minimizes the number of elevators assigned.

[0072] When the allocation unit 511 completes all allocations based on the received first allocation request, it transmits information indicating the allocation results to the shuttle group management control device 1. This information includes the destination floor and information indicating the assigned shuttle unit for each destination floor. If the allocation unit 511 assigns multiple shuttle units to a destination floor call based on the first request, this information includes information indicating multiple assigned shuttle units.

[0073] If users with the same destination floor use different units of the local elevator 7, all of these units would need to stop at that destination floor. In this case, the number of floors that the local elevator 7 stops at would increase, potentially reducing its convenience. In contrast, with the above configuration, the request unit 112 requests destination floors for authenticated users currently using a single unit of the shuttle elevator 3 in a single request for each destination floor. The assignment unit 511 uses the number of authenticated users for each destination floor to assign users with the same destination floor and using the same unit of the shuttle elevator 3 to use the same unit of the local elevator 7 whenever possible. By having users with the same destination floor use the same unit of the local elevator 7, the possibility of multiple units needing to stop at the same floor can be reduced. This reduces the possibility of reduced convenience for the local elevator 7.

[0074] Furthermore, the allocation unit 511 also assigns the local elevator 7 to users who call for a destination floor using the destination floor registration device 8. When the allocation unit 511 receives a second allocation request from the destination floor registration device 8, it refers to the second registrant DB 521 in the storage unit based on the user identification information included in the second allocation request and identifies the default destination floor of the registrant corresponding to that identification information. In addition, the allocation unit 511 identifies the floor (installation floor) on which the destination floor registration device 8 is installed based on the identification information of the destination floor registration device 8 included in the second allocation request.

[0075] The allocation unit 511 assigns the optimal elevator to a destination floor call where the installation floor is the departure floor and the default destination floor is the destination floor, and registers the destination floor call. The allocation unit 511 transmits information indicating the allocation result to the second display unit 82 of the destination floor registration device 8, which is the source of the second allocation request. The allocation unit 511 also transmits a call request to the local elevator control device 6, which controls the assigned local elevator 7, requesting registration of the destination floor call. The call request includes information indicating the departure floor and destination floor. When the allocation unit 511 makes an allocation based on the second allocation request, the departure floor is the installation floor of the destination floor registration device 8 that sent the second allocation request, and the destination floor is the user's default destination floor.

[0076] Furthermore, when a second assignment request is received from the reading unit 81 of the destination floor registration device 8 installed on the transfer floor, the default destination floor corresponding to the identification information included in the second assignment request may not be included in the service floors of the local elevator 7. In this case, the assignment unit 511 transmits information indicating that the destination floor call cannot be registered to the reading unit 81, which is the source of the second assignment request.

[0077] Traditionally, users had to register their request to use the local elevator 7 at the transfer floor after disembarking from the shuttle elevator 3's car 31. Furthermore, if the number of destination floor registration devices 8 installed at the transfer floor was insufficient for the number of users on the shuttle elevator 3's car 31, a queue would form to register a request for the local elevator 7, potentially reducing convenience.

[0078] According to the above configuration, images of users who are scheduled to board or are currently boarding the shuttle elevator 3 are acquired, and authentication is performed based on these images. Then, a local elevator 7 unit is assigned to the authenticated user's destination floor call. As a result, after the authenticated user disembarks from the shuttle elevator 3's car 31, they can travel to their destination floor by boarding the assigned local elevator 7 unit. Thus, with the above configuration, users of the shuttle elevator 3 do not need to register their destination floor call for local elevator 7 at the transfer floor, thus improving convenience.

[0079] <Processing flow in elevator management system 100> Figures 10 to 13 are flowcharts and sequence diagrams illustrating examples of the processing flow in the elevator management system 100. The processing flow in the elevator management system 100 will be explained below using Figures 10 to 13.

[0080] Figures 10-11 and 13 are flowcharts illustrating examples of the processing flow performed by the shuttle elevator control device 2. Figure 12 is a sequence diagram showing examples of the processing flow performed by the shuttle group management control device 1 and the local group management control device 5.

[0081] First, using Figures 10 and 11, we will explain the process by which the shuttle elevator control device 2 authenticates a user and sends an assignment request to the shuttle group management control device 1. When the input device 4 on the lobby floor is operated, the elevator control unit 211 of the shuttle elevator control device 2 moves the elevator car 31 to the lobby floor based on the information received from the shuttle group management control device 1.

[0082] The acquisition unit 212 determines whether the doors of the elevator car 31 have been closed after they have been opened on the lobby floor (YES in S1) (S2). If the doors have not been closed (NO in S2), the acquisition unit 212 performs a process to acquire an image showing the face of a user who is scheduled to ride the shuttle elevator 3. Specifically, the acquisition unit 212 acquires an image from the imaging unit 32 and extracts the faces of people included in the acquired image. If the extracted person is scheduled to ride the elevator car 31 of the shuttle elevator 3, that is, if the face of a user who is scheduled to ride the shuttle elevator 3 is recognized (YES in S3), the acquisition unit 212 acquires the face image of that user (S4: acquisition step). The acquisition unit 212 outputs the acquired face image of the user to the authentication unit 213.

[0083] When the authentication unit 213 acquires a user's facial image, it authenticates the user based on the acquired facial image (S5: Authentication step). Specifically, when the authentication unit 213 acquires a user's facial image, it sends a request to the shuttle group management control device 1. When the reception unit 111 of the shuttle group management control device 1 receives the request, it sends the information contained in the first registrant DB 123 of the storage unit 12 to the shuttle elevator control device 2. Based on the registrant's facial image contained in the received information and the user's facial image acquired from the acquisition unit 212, the authentication unit 213 determines whether or not a registrant to which the user belongs exists. If the facial image of a registrant to which the user belongs is included in the first registrant DB 123, the authentication unit 213 determines that the user has been successfully authenticated. On the other hand, if the facial image of a registrant to which the user belongs is not included in the first registrant DB 123, the authentication unit 213 determines that the user has been unsuccessfully authenticated.

[0084] If the authentication unit 213 fails to authenticate the user (NO in S6), the process returns to S2. If the user authentication unit 213 succeeds in authenticating the user (YES in S6), it obtains information indicating the authenticated user's default destination floor from the first registrant DB 123. The authentication unit 213 assigns the value indicating the authenticated user's default destination floor to the variable L, which indicates the destination floor (S7). After the process in S7, the process proceeds to the process shown in Figure 11.

[0085] If the doors of elevator car 31 have been closed on the lobby floor (YES in S2) and a predetermined amount of time has not elapsed since the doors were closed (NO in S8), the acquisition unit 212 performs the process of acquiring an image showing the face of a user who is riding in the shuttle elevator 3. Specifically, the acquisition unit 212 acquires an image from the imaging unit 32 and extracts the face of a person inside elevator car 31. If the face of a person inside elevator car 31 is extracted, that is, if the face of a user who is riding in the shuttle elevator 3 is recognized (YES in S9), the acquisition unit 212 acquires the face image of that user (S4: acquisition step). The processing after the user's face image has been acquired (processing in S5 to S7) has already been explained, so the explanation is omitted here.

[0086] Next, the processing that takes place after the processing of S7 will be explained using Figure 11. After the processing of S7, the authentication unit 213 checks for duplicate requests from the authenticated user. If there are no duplicate requests from the authenticated user, that is, if the authenticated user's request has not yet been registered, the authentication unit 213 registers the request for that authenticated user.

[0087] First, the authentication unit 213 assigns 0 to the variable CNT, which indicates the number of authenticated users who have registered a request. The authentication unit 213 also clears the user DB 221 and the request request DB 222. Then, the authentication unit 213 assigns 1 to the variable Q (S21).

[0088] Next, the authentication unit 213 determines whether the variable CNT = 0 (S22). In other words, the authentication unit 213 determines whether the authenticated user who has just been authenticated is the first authenticated user in the series of processes. If the variable CNT = 0 (YES in S22), the authentication unit 213 assigns 1 to the variable CNT (S23).

[0089] The authentication unit 213 enters the authentication user's identification information (user ID) into the field corresponding to the first entry in the user database 221 (TBL(1)) (S24). This allows the authentication unit 213 to know that a request for a destination floor call for the authentication user has already been registered when it next refers to the user database 221. Subsequently, the authentication unit 213 registers the request for a destination floor call for the authentication user. Specifically, the authentication unit 213 increments the value (DES(L)) indicated by the number of people information corresponding to the authentication user's default destination floor by 1 (S25).

[0090] After S25, the authentication unit 213 refers to the user database 221 and determines whether the user ID of the authenticated user has already been registered. Specifically, the authentication unit 213 determines whether the identification information (user ID) of the authenticated user matches the identification information associated with the number indicated by variable Q in the user database 221 (S26). If the authenticated user is the first authenticated user in the series of processes, then variable Q = 1. Also, in S25, a request for a destination floor call for the authenticated user was registered, and in S24, the identification information of the authenticated user was entered into the first field of the user database 221. Therefore, in the processing after S25, the authentication unit 213 determines that the identification information (user ID) of the authenticated user matches the identification information associated with the number indicated by variable Q in the user database 221 (YES in S26).

[0091] If the answer in S22 is NO, that is, if the authenticated user is the second or later authenticated user in the series of processes, the authentication unit 213 performs the process in S26. If the authenticated user is the second authenticated user in the series of processes and the variable Q = 1, the authentication unit 213 refers to the identification information entered in the first column of the user DB 221. If the authenticated user is the same person as the first authenticated user, the identification information of the authenticated user matches the identification information entered in the first column of the user DB 221. On the other hand, if the authenticated user is a different person from the first authenticated user, the identification information of the authenticated user does not match the identification information entered in the first column of the user DB 221.

[0092] If the identification information of the authenticated user does not match the identification information associated with the number indicated by the variable Q in the user DB221 (NO in S26), the authentication unit 213 increments the variable Q by 1 (S27). Next, the authentication unit 213 determines whether it has checked the identification information of all authenticaters entered in the user DB221. Specifically, the authentication unit 213 determines whether variable Q > variable CNT (S28). If NO in S28, the process returns to S26.

[0093] If the answer in S28 is YES, the authentication unit 213 increments the variable CNT by 1 (S29). The answer in S28 is YES if the identification information of the authenticated user authenticated this time does not match any of the identification information of authenticated users entered in the user DB 221. In this case, the authentication unit 213 registers the scheduled request for a destination floor call for the authenticated user authenticated this time. Specifically, after S29, the authentication unit 213 enters the identification information of the authenticated user into the field corresponding to the CNT number in the user DB 221 (TBL(CNT)) (S30). Subsequently, the authentication unit 213 registers the scheduled request for a destination floor call for the authenticated user. Specifically, the authentication unit 213 increments the value (DES(L)) indicated by the number of people corresponding to the default destination floor of the authenticated user by 1 (S31). After S31, the process returns to S2 in Figure 10.

[0094] On the other hand, if the identification information of the authenticated user in this case matches the identification information associated with the number indicated by the variable Q in the user DB221 (YES in S26), then the identification information of the authenticated user in this case is already registered in the user DB221. In this case, the scheduled request for the destination floor call of the authenticated user is already registered in the scheduled request DB222, so there is no need to register a new scheduled request for the destination floor call of the authenticated user. Therefore, if YES is obtained in S26, the authentication unit 213 does not register a scheduled request for the destination floor call of the authenticated user and returns to the process in S2 of Figure 10.

[0095] If the answer is YES in S26, or after processing in S31, the shuttle elevator control device 2 acquires the user's facial image and authenticates the user until a predetermined time has elapsed since the doors of the elevator car 31 closed (until the answer is YES in S8). If the doors of the elevator car 31 have closed on the lobby floor (YES in S2) and a predetermined time has elapsed since the doors closed (YES in S8), the process proceeds to S10.

[0096] If the answer to S8 is YES, the authentication unit 213 requests the local group management control device 5 to register the destination floor call of the authenticated user, based on the information registered in the request schedule DB 222. First, the authentication unit 213 assigns a value to the variable P, which indicates the floor number, that represents the lowest floor among all the service floors of the local elevators 7. For example, if the lowest service floor of the local elevators 7 is the 10th floor, the authentication unit 213 assigns 10 to the variable P.

[0097] The authentication unit 213 determines whether the value indicated by variable P is higher than the value indicating the top floor among the service floors of the local elevator 7, that is, whether P > top floor (S10). If P ≤ top floor (NO in S10), the authentication unit 213 identifies the number of authenticated users (DES(P)) whose destination floor is the floor indicated by variable P, based on the information registered in the request schedule DB 222. Next, the authentication unit 213 determines whether there are authenticated users whose destination floor is the floor indicated by variable P, that is, whether DES(P) > 0 (S11). If DES(P) > 0 (YES in S11), that is, there are authenticated users whose destination floor is floor P, and a request schedule for a destination floor call by such authenticated users is registered, the authentication unit 213 sends an assignment request to the shuttle group management control device 1 (S12). The authentication unit 213 associates information indicating floor P as the destination floor with information indicating the number of authenticated users whose destination floor is floor P, and sends it as an assignment request. On the other hand, if DES(P) ≤ 0 (YES in S11), there are no authenticated users whose destination floor is floor P. In this case, the authentication unit 213 proceeds to processing S13 without sending an assignment request. After processing S12, or if NO in S11, the authentication unit 213 increments the variable P by 1 (S13) and returns to processing S10.

[0098] If P is the top floor (YES in S10), that is, the authentication unit 213 determines whether it is necessary to send an assignment request for all service floors of the local elevator 7, and if it sends an assignment request as necessary, the process ends.

[0099] Next, using Figures 12 and 13, we will explain the process by which the shuttle group management control device 1 requests the local group management control device 5 to assign a local elevator 7, and displays the assignment result on the first display unit 33 of the shuttle elevator 3.

[0100] When the request unit 112 of the shuttle group management control device 1 receives an allocation request from the shuttle elevator control device 2 (YES in S41), it identifies the local group management control device 5, which is the destination of the first allocation request. The request unit 112 then requests the local group management control device 5 (management device), which manages the local elevator 7 that includes the destination floor associated with the authenticated user authenticated in the authentication step as a service floor, to register the destination floor call of the authenticated user. Specifically, the request unit 112 identifies which local elevator 7's service floor includes the floor indicating the destination floor included in the received allocation request.

[0101] If the destination floor is a low floor (YES in S42), that is, if the floor indicating the destination floor is included in the service floors of the first local elevator 7, the request unit 112 identifies the first local group control device 5, which manages the first local elevator 7, as the recipient of the first assignment request. The request unit 112 sends the first assignment request to the identified local group control device 5, i.e., the first local group control device 5 (S43: Request step).

[0102] If the destination floor is not a low-rise floor (NO in S42) but a high-rise floor (YES in S44), the floor indicating the destination floor is included in the service floors of the second local elevator 7. In this case, the request unit 112 identifies the second local group control device 5, which manages the second local elevator 7, as the destination for the first assignment request. The request unit 112 sends the first assignment request to the identified local group control device 5, i.e., the second local group control device 5 (S45: Request step).

[0103] Even if the elevator management system 100 is equipped with three or more local group control devices 5, the request unit 112 performs the same processing. That is, the request unit 112 identifies a local elevator 7 that has a service floor that includes the floor indicating the destination floor included in the received assignment request, and transmits the first assignment request to the local group control device 5 that manages the identified local elevator 7.

[0104] The request unit 112 performs the processing from S42 onwards each time it receives an allocation request from the shuttle elevator control device 2. For example, let's consider a case where there are 3 authenticated users whose destination is the 11th floor and 5 authenticated users whose destination is the 21st floor inside the shuttle elevator 3. In this case, the request unit 112 receives an allocation request indicating that the destination is the 11th floor and that there are 3 authenticated users whose destination is the 11th floor, and an allocation request indicating that the destination is the 21st floor and that there are 5 authenticated users whose destination is the 21st floor. Based on each of the received allocation requests, the request unit 112 identifies the recipient of the first allocation request and sends the first allocation request. For example, in the above case, the request unit 112 sends the first allocation request indicating that the destination is the 11th floor and that there are 3 authenticated users whose destination is the 11th floor to the first local group management control device 5. Furthermore, the request unit 112 transmits a first allocation request to the second local group management control device 5, indicating that the destination floor is the 21st floor and that there are 5 authenticated users whose destination floor is the 21st floor.

[0105] When the local group control device 5 receives a first assignment request, it assigns a local elevator 7 that includes the destination floor of the authenticated user as a service floor to the authenticated user's destination floor call. For example, when the assignment unit 511 of the first local group control device 5 receives a first assignment request from the shuttle group control device 1 (YES in S51), it assigns a local elevator 7 to the authenticated user's destination floor call based on the first assignment request (S52: assignment step). The assignment unit 511 assigns the optimal elevator based on the operating status of each elevator in the first local elevator 7, the capacity of each elevator, and the first assignment request. The assignment unit 511 transmits information indicating the assigned elevator, information indicating the destination floor, and information indicating the assignment result to the shuttle group control device 1. The assignment unit 511 also transmits a call request including information indicating the departure floor and destination floor to the first local elevator control device 6 that controls the assigned elevator. When the allocation unit 511 makes an allocation based on the first allocation request, the departure floor is the transfer floor, and the destination floor is the destination floor of the authenticated user included in the first allocation request. When the local elevator control device 6 receives a call request, it registers the destination floor call based on the received call request and controls the operation of the elevator based on the registered destination floor call.

[0106] When the allocation unit 511 of the second local group management control device 5 receives the first allocation request (YES in S61), it allocates a unit of the second local elevator 7 based on the first allocation request (S62: allocation step). The allocation unit 511 then transmits information indicating the allocation result to the shuttle group management control device 1 and transmits a call request including information indicating the departure floor and destination floor to the second local elevator control device 6, which controls the allocated unit.

[0107] When the allocation result acquisition unit 113 of the shuttle group management control device 1 receives information indicating the allocation result from the local group management control device 5 (YES in S46), it transmits the information to the shuttle elevator control device 2, which is the source of the allocation request (S47). When the display control unit 214 of the shuttle elevator control device 2 receives information indicating the allocation result (YES in S71), it displays the information on the first display unit 33. Specifically, the display control unit 214 displays the destination floor and the assigned elevator number corresponding to that destination floor on the first display unit 33 (S72). When the elevator number of the shuttle elevator 3 completes door opening at the transfer floor (YES in S73), the display control unit 214 erases the display content currently displayed on the first display unit 33 (S74).

[0108] As described above, when a user uses the shuttle elevator 3, the user is authenticated, and a destination floor call is registered for the authenticated user to use the local elevator 7. In addition, the first display unit 33 inside the car 31 of the shuttle elevator 3, which the authenticated user is using, displays the assignment result, including information indicating the unit number of the local elevator 7 that the authenticated user should board.

[0109] [Embodiment 2] Other embodiments of the present invention are described below. For the sake of clarity, components having the same function as those described in the above embodiments will be denoted by the same reference numerals, and their descriptions will not be repeated.

[0110] Figure 14 is a block diagram showing the configuration of the elevator management system 100A according to Embodiment 2 of the present invention. As shown in Figure 14, the elevator management system 100A comprises a shuttle management system 10A, a local management system 20A, and a terminal device 50. The terminal device 50 is an information processing device such as a smartphone owned by the user. In the elevator management system 100A according to Embodiment 2, the shuttle management system 10A notifies the user's terminal device 50 of the allocation result for the local elevator 7.

[0111] Figure 15 is a block diagram showing the configuration of the shuttle management system 10A included in the elevator management system 100A. Figure 16 is a block diagram showing the configuration of the local management system 20A included in the elevator management system 100A. The shuttle management system 10A differs from the shuttle management system 10 in that it includes a shuttle group management control device 1A, a shuttle elevator control device 2A, and a shuttle elevator 3A instead of a shuttle group management control device 1, a shuttle elevator control device 2, and a shuttle elevator 3. The local management system 20A differs from the shuttle management system 10 in that it includes a local group management control device 5A instead of a local group management control device 5.

[0112] Shuttle elevator 3A differs from shuttle elevator 3 in that it does not have a second display unit 82. Shuttle elevator control device 2A differs from shuttle elevator control device 2 in that it has a control unit 21A and a storage unit 22A instead of a control unit 21 and a storage unit 22. Control unit 21A includes an elevator control unit 211, an acquisition unit 212, and an authentication unit 213A. Storage unit 22A stores a request schedule DB 222A instead of a request schedule DB 222. In the request schedule DB 222A, the floor indicating the destination floor, the number of authenticated users whose destination floor is that floor, and the identification information of the authenticated users whose destination floor is that floor are associated.

[0113] If the authentication unit 213A successfully authenticates a user, it increments the number of people information associated with the floor corresponding to the authenticated user's default destination floor in the request schedule DB 222A by 1, and further associates the authenticated user's identification information with that floor. The authentication unit 213A also transmits the information registered in the request schedule DB 222A to the shuttle group management control device 1.

[0114] The shuttle group management control device 1A includes a control unit 11A and a storage unit 12A instead of the control unit 11 and storage unit 12. The control unit 11A includes a reception unit 111, a request unit 112A, an assignment result acquisition unit 113A, and a notification control unit 114. The storage unit 12A stores the first registrant DB 123A instead of the first registrant DB 123. The first registrant DB 123A is a database in which contact information indicating the contact details of each registrant is associated with the information contained in the first registrant DB 123. The contact information is information for notifying the assignment result to the terminal device 50 held by the authenticated user. For example, the contact information may be information such as the telephone number or email address of the terminal device 50 held by the registrant.

[0115] When the request unit 112A receives an allocation request from the shuttle elevator control device 2A, it transmits a first allocation request to the appropriate local group management control device 5. Here, the allocation request received from the shuttle elevator control device 2A includes information indicating the destination floor and the number of authenticated users whose destination is that floor, as well as identification information of the authenticated users whose destination is that floor. The request unit 112A transmits the first allocation request, including the identification information of the authenticated users, to the local group management control device 5.

[0116] The local group control device 5A differs from the local group control device 5 in that it includes a control unit 51A having an allocation unit 511A. The allocation unit 511A of the local group control device 5A assigns a local elevator 7 to the destination floor call of an authenticated user based on the first allocation request. The allocation unit 511A associates the destination floor and the assigned elevator number with the identification information of the authenticated user who should board the assigned elevator and transmits it to the shuttle group control device 1.

[0117] For example, let's consider a case where there are 10 authenticated users whose destination is the 11th floor. If there are 10 available seats in elevator A of local elevator 7, the allocation unit 511A assigns elevator A to destination calls for the 11th floor. The allocation unit 511A transmits to the shuttle group management control device 1 the information indicating the destination floor, the 11th floor, the information indicating the assigned elevator, elevator A, and the identification information of the 10 authenticated users who should board elevator A, in association with each other.

[0118] If none of the local elevators 7 have 10 available seats, the allocation unit 511A will assign multiple elevators to a destination call for the 11th floor. For example, if elevator A has 2 available seats and elevator B has 8 available seats, the allocation unit 511A will assign both elevators A and B to a destination call for the 11th floor. In this case, the allocation unit 511A will transmit to the shuttle group management control device 1 the information indicating the destination floor, the 11th floor, the information indicating the assigned elevator, elevator A, and the identification information of the two authenticated users who should board elevator A, in association with each other. The allocation unit 511A will also transmit to the shuttle group management control device 1 the information indicating the destination floor, the 11th floor, the information indicating the assigned elevator, elevator B, and the identification information of the eight authenticated users who should board elevator B, in association with each other.

[0119] When the allocation result acquisition unit 113A receives information indicating the allocation result from the local group management control device 5, it outputs the received information to the notification control unit 114. Here, the information indicating the allocation result includes not only information indicating the destination floor and the allocated elevator car, but also identification information of the authenticated user who should board the allocated elevator car.

[0120] The notification control unit 114 notifies the terminal device 50 held by the authenticated user of the assignment result by the assignment unit 511A. When the notification control unit 114 obtains information indicating the assignment result from the assignment result acquisition unit 113A, it identifies the contact information for each authenticated user included in the information. Specifically, the notification control unit 114 refers to the first registrant DB 123 and identifies the registrant identification information that matches the authenticated user identification information included in the information indicating the assignment result. The notification control unit 114 identifies the contact information associated with the identified registrant identification information as the contact information for the authenticated user.

[0121] The notification control unit 114 notifies the authenticated user's terminal device 50 of the assigned unit for the authenticated user's destination floor call. Specifically, the notification control unit 114 identifies the assigned unit and destination floor information associated with the authenticated user identification information in the information indicating the assignment result received from the local group management control device 5. The notification control unit 114 uses the authenticated user's contact information to transmit the information indicating the assigned result for the authenticated user to the authenticated user's terminal device 50. The notification control unit 114 sends a notification to all authenticated user terminal devices 50 indicated by the identification information included in the information indicating the assignment result.

[0122] For example, let's consider a scenario where there are 10 authenticated users whose destination is the 11th floor, and elevator A is assigned to two users' destination calls for the 11th floor, while elevator B is assigned to the remaining eight users' destination calls. In this case, the notification control unit 114 transmits information indicating the destination floor, the 11th floor, and information indicating the assigned elevator, elevator A, to the terminal devices 50 of the two authenticated users to whom elevator A is assigned. The notification control unit 114 also transmits information indicating the destination floor, the 11th floor, and information indicating the assigned elevator, elevator B, to the terminal devices 50 of the eight authenticated users to whom elevator A is assigned. As a result, authenticated users can determine which local elevator 7 they should board by checking their terminal devices 50.

[0123] With the above configuration, the assignment result from the assignment unit 511 is notified to each authenticated user's terminal device 50. This reduces the possibility that authenticated users may overlook the assignment result. Also, if there are many calls to a single destination floor, calls to that destination floor may be assigned to multiple elevators. If multiple authenticated users going to the same destination floor board one elevator, it may result in a situation where another user who was planning to board the same elevator is unable to board. With the above configuration, however, the terminal device 50 of an authenticated user is notified of the elevator assigned to that authenticated user's call to the destination floor. This allows authenticated users to know which elevator they should board, thus reducing the possibility of the above-mentioned situation occurring.

[0124] [Embodiment 3] Figure 17 is a block diagram showing the configuration of the elevator management system 100B according to Embodiment 3 of the present invention. As shown in Figure 17, the elevator management system 100B includes a shuttle management system 10B and a local management system 20B. In the elevator management system 100B according to Embodiment 3, if an authenticated user who meets specific attributes is located within a predetermined range in the shuttle elevator 3, the door opening time of the local elevator 7 on which the authenticated user is riding is extended.

[0125] Figure 18 is a block diagram showing the configuration of the shuttle management system 10B included in the elevator management system 100B. Figure 19 is a block diagram showing the configuration of the local management system 20B included in the elevator management system 100B. The shuttle management system 10B differs from the shuttle management system 10 in that it includes a shuttle group management control device 1B and a shuttle elevator control device 2B instead of the shuttle group management control device 1 and the shuttle elevator control device 2. The local management system 20B differs from the local management system 20 in that it includes a local group management control device 5B and a local elevator control device 6B instead of the local group management control device 5 and the local elevator control device 6.

[0126] The shuttle group management control device 1B includes a control unit 11B and a storage unit 12B instead of the control unit 11 and storage unit 12. The control unit 11B differs from the control unit 11 in that it includes a request unit 112B instead of the request unit 112. The storage unit 12B stores the first registrant DB 123B instead of the first registrant DB 123. In addition to the same information as the first registrant DB 123, the first registrant DB 123B associates the registrant's identification information with information indicating the registrant's attributes. The registrant's attributes may be, for example, general user, wheelchair user, visually impaired person, or VIP user.

[0127] The shuttle elevator control device 2B includes a control unit 21B instead of the control unit 21. The control unit 21 differs from the control unit 21 in that it includes an authentication unit 213B instead of the authentication unit 213, and also includes a specification unit 215. When the authentication unit 213B acquires a user's facial image, it sends a request to the shuttle group management control device 1 and receives information contained in the first registered user DB 123B. If the authentication unit 213B successfully authenticates the user, it registers the authenticated user's request schedule and outputs information indicating that the user's authentication was successful to the specification unit 215.

[0128] When the identification unit 215 obtains information indicating that user authentication has been successful, it determines whether the authenticated user falls under a specific attribute based on the information contained in the first registrant DB 123B. For example, the identification unit 215 determines whether the authenticated user is a wheelchair user or a visually impaired person. If the authenticated user falls under a specific attribute, the identification unit 215 obtains an image of the inside of the car 31 from the imaging unit 32 or the acquisition unit 212. The identification unit 215 identifies the position of the authenticated user inside the car 31 and determines whether the authenticated user is located within a predetermined range inside the car 31. The predetermined range is the range in which it is considered that it takes longer for a user who falls under a specific attribute to disembark from the car 31 than for a general user to disembark. The predetermined range may be, for example, the range belonging to the wall side when the inside of the car 31 is divided into the door side and the wall side opposite the door.

[0129] If an authenticated user matching a specific attribute is located within a predetermined range in the cart 31, the identification unit 215 associates information indicating that an authenticated user matching the specific attribute is scheduled to use the cart with information indicating the floor corresponding to the destination floor of the authenticated user in the request schedule DB 222. If the authenticated user does not match a specific attribute, or if an authenticated user matching a specific attribute is not located within a predetermined range in the cart 31, the identification unit 215 does not associate any information regarding the scheduled use.

[0130] When the request unit 112B of the shuttle group management control device 1 receives an allocation request from the shuttle elevator control device 2, it transmits a first allocation request to the local group management control device 5. If the allocation request is associated with usage information, the request unit 112B further associates the usage information with the first allocation request and transmits it.

[0131] As shown in Figure 19, the local group management control device 5B includes a control unit 51B instead of a control unit 51. The control unit 51B includes an allocation unit 511B instead of an allocation unit 511. When the allocation unit 511B receives a first allocation request, it allocates a local elevator 7 based on the said allocation request. If the first allocation request is associated with usage information, the allocation unit 511B transmits an extension instruction to the local elevator control device 6 that controls the allocated elevator, along with information indicating the destination floor of a specific user.

[0132] The local elevator control device 6B is equipped with a control unit 61B in place of the control unit 61. When the control unit 61B receives a call request from the local group management control device 5B, it registers the user's destination floor call based on the information contained in the call request. Here, if the control unit 61B receives an extension instruction along with the call request, it extends the door opening time of the elevator car 31 at the transfer floor by a predetermined time. The predetermined time may be, for example, 20 seconds.

[0133] As a result, if an authenticated user matching a specific attribute is present within a predetermined range inside the car 31 of the shuttle elevator 3, the control unit 61B of the local elevator control device 6B can extend the door opening time of the assigned elevator for the authenticated user's destination floor call.

[0134] If an authenticated user with specific attributes is located within a predetermined range inside elevator car 31, it may take time for that user to disembark. For example, if an authenticated user who uses a wheelchair is located far from the door of elevator car 31, it may take time for that user to disembark, and they may not be able to transfer to local elevator 7 in time.

[0135] According to the above configuration, if an authenticated user matching a specific attribute is present within a predetermined range in the elevator car 31, the door opening time for the assigned elevator car of that authenticated user is extended. This reduces the possibility that the authenticated user may not be able to transfer in time.

[0136] [Embodiment 4] Figure 20 is a block diagram showing the configuration of the elevator management system 100C according to Embodiment 4 of the present invention. As shown in Figure 20, the elevator management system 100C includes a shuttle management system 10C, a local management system 20C, and an authentication device 30. In the elevator management system 100C according to Embodiment 4, the authentication device 30 authenticates the user.

[0137] Figure 21 is a block diagram showing the configuration of the shuttle management system 10C and the authentication device 30 included in the elevator management system 100C. The shuttle management system 10C differs from the shuttle management system 10 in that it includes a shuttle group management control device 1C and a shuttle elevator control device 2C instead of the shuttle group management control device 1 and the shuttle elevator control device 2.

[0138] The shuttle elevator control device 2C includes a control unit 21C and a storage unit 22C instead of the control unit 21 and storage unit 22. The storage unit 22C differs from the storage unit 22 in that it does not store the user DB 221 and the scheduled request DB 222. The control unit 21C differs from the control unit 21 in that it does not have an authentication unit 213 and has an acquisition unit 212C instead of an acquisition unit 212. When the acquisition unit 212C acquires a user's facial image, it transmits the facial image to the authentication device 30.

[0139] As shown in Figure 21, the authentication device 30 comprises a control unit 301 and a storage unit 302. The storage unit 302 stores the first registrant DB 304, the user DB 305, and the request schedule DB 306. The first registrant DB 304, the user DB 305, and the request schedule DB 306 contain the same information as the first registrant DB 123, the user DB 221, and the request schedule DB 222 according to Embodiment 1.

[0140] The control unit 301 includes an authentication unit 303. The authentication unit 303 authenticates users in the same manner as the authentication unit 213 of the shuttle elevator control device 2 according to Embodiment 1. When the authentication unit 303 receives a user's facial image from the shuttle elevator control device 2, it refers to the first registered user DB 123 and authenticates the user. If the user authentication is successful, the authentication unit 213 checks for duplicate authenticated users and registers the authenticated user's destination floor request. After a predetermined time has elapsed since the doors of the elevator car 31 were closed, the authentication unit 303 sends an assignment request to the shuttle group management control device 1 based on the information registered in the request schedule DB 306.

[0141] The assignment request may also be sent by the shuttle elevator control device 2C. In this case, the authentication device 30 does not store the user DB 305 and the request schedule DB 306, and the shuttle elevator control device 2C may store them. The authentication unit 303 associates information indicating the user's authentication result with information indicating the authenticated user's default destination floor and sends it to the shuttle elevator control device 2C. The control unit 21C of the shuttle elevator control device 2C registers the request schedule for the authenticated user's destination floor based on the received information.

[0142] The shuttle group management control device 1C comprises a control unit 11C and a storage unit 12C. The control unit 11C differs from the control unit 11 in that it includes a request unit 112C instead of a request unit 112. The storage unit 12C differs from the storage unit 12 in that it does not store the first registrant DB 123. When the request unit 112C receives an assignment request from the authentication device 30, it transmits a first assignment request to the local group management control device 5 based on the assignment request.

[0143] Figure 22 is a block diagram showing the configuration of the local management system 20C provided by the elevator management system 100C. The local management system 20C differs from the local management system 20 in that it is equipped with a local group management control device 5C and a destination floor registration device 8C instead of the local group management control device 5 and the destination floor registration device 8.

[0144] The destination floor registration device 8C includes a reading unit 81C. The reading unit 81C is connected to the authentication device 30. When the reading unit 81C reads the user's identification information, it transmits the read identification information and its own device's identification information to the authentication device 30. When the authentication unit 303 of the authentication device 30 receives the identification information from the reading unit 81C, it authenticates the user based on the received identification information. If the user authentication is successful, the authentication unit 303 associates information indicating the authenticated user's default destination floor with the identification information of the reading unit 81C that read the identification information, and transmits this as a second assignment request to the local group management control device 5C. The authentication unit 303 also transmits the second assignment request to the local group management control device 5, which manages the local elevator 7 that includes the floor on which the reading unit 81C that read the identification information is installed as a service floor. If the reading unit 81C that read the identification information is the reading unit 81C of the destination floor registration device 8C installed on the transfer floor, the authentication unit 303 sends a second assignment request to the local group management control device 5C that includes the user's destination floor as a service floor.

[0145] The local group management control device 5C includes a control unit 51C and a storage unit 52C instead of the control unit 51 and storage unit 52. The storage unit 52C differs from the storage unit 52 in that it does not store the second registrant DB 521. The control unit 51 includes an allocation unit 511C instead of the allocation unit 511. The allocation unit 511C allocates a local elevator 7 unit based on a first allocation request received from the shuttle group management control device 1C and transmits information indicating the allocation result to the shuttle group management control device 1C. The allocation unit 511C also allocates a local elevator 7 unit based on a second allocation request received from the authentication device 30 and transmits information indicating the allocation result to the second display unit 82 corresponding to the reading unit 81C that read the identification information.

[0146] [Embodiment 5] Figure 23 is a block diagram showing the configuration of the elevator management system 100D according to Embodiment 5 of the present invention. As shown in Figure 23, the elevator management system 100D includes a shuttle management system 10D and a local management system 20. In the elevator management system 100D according to Embodiment 5, if user authentication fails, guidance is provided prompting the user to register a destination floor call at the transfer floor.

[0147] Figure 24 is a block diagram showing the configuration of the shuttle management system 10D provided by the elevator management system 100D. The shuttle management system 10D differs from the shuttle management system 10 in that it includes a shuttle elevator control device 2D instead of the shuttle elevator control device 2. The shuttle elevator control device 2D includes a control unit 21D instead of the control unit 21. The control unit 21D differs from the control unit 21 in that it includes an authentication unit 213D instead of the authentication unit 213, and also includes a guidance unit 216.

[0148] If authentication fails, the authentication unit 213D stores authentication failure information in the storage unit 22, indicating that authentication has failed. If authentication failure information is stored in the storage unit 22, the guidance unit 216 prompts the user to register a destination floor call at the transfer floor. Specifically, the guidance unit 216 causes the first display unit 33 to display a message prompting the user to register a destination floor call using the destination floor registration device 8 at the transfer floor. However, the guidance unit 216 is not limited to this method of guidance. For example, the guidance unit 216 may output the above message as an audio output from a speaker (not shown) installed inside the car 31 of the shuttle elevator 3.

[0149] [Variation] (Variation 1) In each of the embodiments described above, the authentication unit 213 registered a scheduled request for a destination floor call by the authenticated user in the scheduled request DB 222 and sent an assignment request to the shuttle group management control device 1 at a predetermined timing, but is not limited to this. For example, the authentication unit 213 may send an assignment request each time it successfully authenticates a user. In this case, when the authentication unit 213 successfully authenticates a user, it refers to the user DB 221 and checks for duplicate authenticated users. If the identification information of the authenticated user is not registered in the user DB 221, the authentication unit 213 may send an assignment request to the shuttle group management control device 1 that includes information indicating the authenticated user's default destination floor as the destination floor. When the request unit 112 of the shuttle group management control device 1 receives an assignment request, it may send a first assignment request to the local group management control device 5 that includes information indicating the authenticated user's default destination floor as the destination floor. When the allocation unit 511 receives the first allocation request, it allocates local elevator 7 to the destination floor, where the transfer floor is the departure floor and the floor included in the first allocation request is the destination floor, and transmits the allocation result to the shuttle group management control device 1. The display control unit 214 may obtain information indicating the allocation result via the shuttle group management control device 1 and display the obtained information on the first display unit 33.

[0150] (Modification 2) In each of the embodiments described above, when the reading unit 81 of the destination floor registration device 8 reads the user's identification information, the default destination floor for the registered user is identified as the user's destination floor, but this is not limited to this. For example, when a user registers a destination floor request using the destination floor registration device 8, the destination floor may be a floor specified by the user from among the permitted floors that the user is allowed to use.

[0151] In this case, information indicating the permitted floor, which is the floor that the registrant is permitted to use, is associated with each registrant in the second registrant DB 521 stored in the storage unit 52 of the local group management control device 5. The destination floor registration device 8 may also be equipped with an input device (not shown) that can accept user operations. When a user is authenticated based on the identification information read by the reading unit 81, the control unit 51 of the local group management control device 5 identifies the user's permitted floor and transmits information indicating the user's permitted floor to the second display unit 82 corresponding to the reading unit 81. The user can use the input device to specify a desired floor from among the permitted floors. When the input device receives an input operation from the user, it transmits information indicating the specified floor to the local group management control device 5. When the assignment unit 511 receives this information, it may assign the local elevator 7 to a destination floor call where the floor on which the destination floor registration device 8 is installed is the departure floor and the specified floor is the destination floor.

[0152] (Variation 3) In each of the embodiments described above, the shuttle group management control device 1 stored the first registrant DB 123 and provided the information contained in the first registrant DB 123 in response to a request from the shuttle elevator control device 2. Furthermore, in each of the embodiments described above, the shuttle elevator control device 2 performed user authentication based on the information contained in the provided first registrant DB 123. However, the configuration of the elevator management system 100 is not limited to this. For example, the storage unit 22 of the shuttle elevator control device 2 may store the first registrant DB 123. Alternatively, the shuttle group management control device 1 may store the first registrant DB 123 and perform user authentication in the shuttle group management control device 1.

[0153] (Modification 4) In the above-described embodiment 2, the notification control unit 114 was configured to notify the authenticated user's terminal device 50 of the assigned elevator number that the authenticated user should board, but it is not limited to this configuration. For example, the notification control unit 114 may notify the authenticated user's terminal device 50 of the assigned elevator number for each destination floor for authenticated users who are using the same shuttle elevator 3 as the authenticated user and have called for a destination floor.

[0154] In this case, the contact information of registered users does not need to be associated in the storage unit 12A of the shuttle group management control device 1A. Furthermore, a communication device such as a beacon capable of wireless communication with the user's terminal device 50 may be provided. This communication device is installed in a location that allows it to establish communication with the user's terminal device 50 located inside the shuttle elevator car 31. When the notification control unit 114 receives information indicating the assignment result from the local group management control device 5, it transmits the received information indicating the assignment result to each of the terminal devices 50 that have established communication with the communication device.

[0155] According to the above configuration, a terminal device 50 of an authenticated user is notified of the assigned elevator unit for each destination floor based on the destination floor calls of all authenticated users using the same shuttle elevator unit 3 as that authenticated user. This allows authenticated users to know which elevator unit they should board. Furthermore, according to the above configuration, since it is not necessary to identify which authenticated user each terminal device 50 belongs to, notifications can be made in a way that does not uniquely identify the authenticated user.

[0156] (Variation 5) In the elevator management system 100A according to the above-described embodiment 2, in addition to notification to the terminal device 50 by the notification control unit 114, the assignment result may also be displayed inside the car 31 of the shuttle elevator 3. In this case, the control unit 21A of the shuttle elevator control device 2A may include a display control unit 214, and the shuttle elevator 3A may include a first display unit 33. Furthermore, the assignment result acquisition unit 113A may output information indicating the assignment result to the shuttle elevator control device 2 in addition to the notification control unit 114A, and the display control unit 214 may display this information on the first display unit 33. With the above configuration, even if a user forgets their terminal device 50 or is unable to confirm the assigned elevator number using the terminal device 50, they can still determine the number of the local elevator 7 they should ride by checking the first display unit 33.

[0157] (Experimental variation 6) In the above-described embodiment 4, the display control unit 214 caused the first display unit 33 to display information indicating the assignment result, but the invention is not limited to this. For example, the authentication device 30 may notify the user's terminal device 50 of the information indicating the assignment result. The authentication device 30 stores contact information for transmitting information to the user's terminal device 50. The local group management control device 5 may also assign a local elevator 7 to each authenticated user's destination floor call and transmit information indicating the assignment result to the shuttle group management control device 1C. When the assignment result acquisition unit 113 of the shuttle group management control device 1C receives information indicating the assignment result, it may transmit the received information to the authentication device 30. When the authentication device 30 receives this information, it may transmit information indicating the assignment result to the authenticated user's terminal device 50 based on the authenticated user's contact information.

[0158] [Examples of implementation using software] The functions of the elevator management systems 100, 100A to 100D (hereinafter referred to as "the system") are programs that cause a computer to function as the system, and these programs can be realized by programs that cause a computer to function as each control block of the system (particularly the parts included in the control units 11, 11A to 11C, 21, 21A to 21D, 51, 51A to 51C, 61, 61B, and 301).

[0159] In this case, the system includes a computer having at least one control device (e.g., a processor) and at least one storage device (e.g., memory) as hardware for executing the program. By executing the program using this control device and storage device, the functions described in each of the embodiments are realized.

[0160] The above program may be recorded on one or more computer-readable recording media, not temporary ones. These recording media may or may not be provided by the system. In the latter case, the program may be supplied to the device via any wired or wireless transmission medium.

[0161] Furthermore, some or all of the functions of each of the above control blocks can also be realized by logic circuits. For example, an integrated circuit in which logic circuits functioning as each of the above control blocks are formed is also included in the scope of the present invention. In addition, it is also possible to realize the functions of each of the above control blocks by, for example, a quantum computer.

[0162] Furthermore, each process described in the above embodiments may be performed by AI (Artificial Intelligence). In this case, the AI ​​may operate on the control device described above, or it may operate on other devices (for example, an edge computer or a cloud server).

[0163] The present invention is not limited to the embodiments described above, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention.

[0164] 〔summary〕 An elevator management system according to Embodiment 1 of the present invention comprises: a shuttle elevator having one or more units that shuttle between a lobby floor and a transfer floor; a plurality of local elevators having one or more units that operate between the transfer floor and an upper or lower floor of the transfer floor, with at least some service floors different from each other; and a plurality of management devices that manage each of the plurality of local elevators, the elevator management system comprising: an acquisition unit that acquires an image showing the face of a user who is scheduled to board or is currently boarding the shuttle elevator; an authentication unit that authenticates the user based on the acquired image; a request unit that requests the management device that manages the local elevators whose service floors include the destination floor associated with the authenticated user authenticated by the authentication unit to register the destination floor call of the authenticated user; and an assignment unit that assigns the front symbol unit of the local elevator whose service floors include the destination floor of the authenticated user to the destination floor call of the authenticated user.

[0165] In embodiment 2 of the present invention, the elevator management system may include a display control unit that displays the assignment result by the assignment unit on the display unit inside the car of the shuttle elevator, as described in embodiment 1.

[0166] In the elevator management system according to embodiment 3 of the present invention, in embodiment 2, the display control unit may cause the display unit to display the assigned elevator number for each destination floor of the local elevator.

[0167] In any of the above embodiments 1 to 3, the elevator management system according to embodiment 4 of the present invention may include a notification control unit that notifies the terminal device held by the authenticated user of the allocation result by the allocation unit.

[0168] In the elevator management system according to aspect 5 of the present invention, in aspect 4 above, the notification control unit may notify the terminal device of the authenticated user of the assigned elevator number for the authenticated user's destination floor call.

[0169] In the elevator management system according to aspect 6 of the present invention, in aspect 4 above, the notification control unit may notify the terminal device of the authenticated user of the assigned elevator unit for each destination floor for an authenticated user who is using the same shuttle elevator unit as the authenticated user.

[0170] An elevator management system according to embodiment 7 of the present invention may include, in any of embodiments 1 to 6 above, an identification unit that identifies the attributes of the authenticated user, and a control unit for the local elevator that, when an authenticated user matching the specific attributes is present within a predetermined range inside the shuttle elevator car, extends the door opening time of the assigned elevator for a call to the destination floor of the authenticated user.

[0171] In an elevator management system according to embodiment 8 of the present invention, in any of embodiments 1 to 7 above, the request unit transmits the number of people information indicating the number of authenticated users for each destination floor currently using one of the shuttle elevator units to the management device, and the assignment unit assigns the front unit of the local elevator based on the number of people information.

[0172] In any of the embodiments 1 to 8 described above, the elevator management system according to embodiment 9 of the present invention may further include a guidance unit that, if there is a user in the car of the shuttle elevator unit who has not been authenticated by the authentication unit, guides the user to use a destination floor registration device to request the management device to register the user's destination floor.

[0173] A control method according to embodiment 10 of the present invention is a control method for an elevator management system comprising: a shuttle elevator having one or more units that shuttle between a lobby floor and a transfer floor; a plurality of local elevators having one or more units that operate between the transfer floor and an upper or lower floor of the transfer floor, with at least some service floors different from each other; and a plurality of management devices that manage each of the plurality of local elevators, the method comprising: an acquisition step of acquiring an image showing the face of a user who is scheduled to board or is currently boarding the shuttle elevator; an authentication step of authenticating the user based on the acquired image; a request step of requesting the management device that manages the local elevators whose service floors include the destination floor associated with the authenticated user authenticated in the authentication step to register the destination floor call of the authenticated user; and an assignment step of assigning the front symbol unit of the local elevators whose service floors include the destination floor of the authenticated user to the destination floor call of the authenticated user. [Explanation of symbols]

[0174] Elevator management system for 100, 100A~100D 112, 112A~112C Request Department 114 Notification Control Unit 212, 212C Acquisition Department 213, 213A, 213B, 213D, 303 Authentication Department 214 Display Control Unit 215 Specific section 216 Information Department 3 Shuttle elevator 31 baskets 33 1st display section (display section) 5, 5A~5C management device 511, 511A~511C Assignment section 61, 61B Control Unit 7 Local elevator 50 Terminal devices S4 Acquisition Steps S5 Authentication Step Request Steps for Showa 43 and Showa 45 S52, S62 Assignment Step

Claims

1. A shuttle elevator having one or more units that operates a shuttle service between the lobby floor and the transfer floor, The system includes one or more elevators operating between the aforementioned transfer floor and the floors above the transfer floor, and a plurality of local elevators, at least some of which have different service floors. An elevator management system comprising a plurality of management devices for managing each of the plurality of local elevators, An acquisition unit that acquires images showing the faces of users who are scheduled to board or are currently boarding the shuttle elevator, An authentication unit that authenticates the user based on the acquired image, A request unit requests the management device, which manages the local elevator whose service floor includes the destination floor associated with the authenticated user authenticated by the authentication unit, to register the destination floor call of the authenticated user. The system includes an assignment unit that assigns a pre-sign unit of the local elevator that includes the destination floor of the authenticated user as a service floor to the destination floor call of the authenticated user, The request unit transmits to the management device the number of people, indicating the number of authenticated users at each destination floor who are currently using one of the shuttle elevator units. The allocation unit, based on the number of people information and the number of available seats in each of the local elevators, assigns the local elevators to the minimum number of local elevators assigned to the authenticated user whose destination floor is the same floor. Elevator management system.

2. The display unit inside the car of the shuttle elevator is equipped with a display control unit that displays the assignment result from the assignment unit. The elevator management system according to claim 1.

3. The display control unit causes the display unit to display the assigned elevator number for each destination floor of the local elevator. The elevator management system according to claim 2.

4. The terminal device possessed by the authenticated user is equipped with a notification control unit that notifies the user of the assignment result from the assignment unit. The elevator management system according to claim 1.

5. The notification control unit notifies the authenticated user's terminal device of the assigned unit for the authenticated user's destination floor call. The elevator management system according to claim 4.

6. The notification control unit notifies the authenticated user's terminal device of the assigned elevator unit for each destination floor for authenticated users using the same shuttle elevator unit as the authenticated user. The elevator management system according to claim 4.

7. An identification unit that identifies the attributes of the authenticated user, The local elevator includes a control unit that, when an authenticated user matching a specific attribute is present within a predetermined range inside the shuttle elevator car, extends the door opening time of the assigned elevator for the destination floor call of the authenticated user. The elevator management system according to claim 1.

8. If there is a user in the car of the aforementioned shuttle elevator unit who has not been authenticated by the authentication unit, the shuttle elevator further includes a guidance unit that guides the user to use a destination floor registration device to request the management device to register the user's destination floor. The elevator management system according to claim 1.

9. A shuttle elevator having one or more units that operates a shuttle service between the lobby floor and the transfer floor, The system includes one or more elevators operating between the aforementioned transfer floor and the floors above the transfer floor, and a plurality of local elevators, at least some of which have different service floors. A control method for an elevator management system comprising a plurality of management devices for managing each of the plurality of local elevators, The acquisition step involves acquiring an image showing the face of a user who is scheduled to board or is currently boarding the shuttle elevator. An authentication step to authenticate the user based on the acquired image, A request step to register the destination floor call of the authenticated user to the management device that manages the local elevator whose service floor includes the destination floor associated with the authenticated user in the authentication step, The process includes an assignment step of assigning a pre-sign unit of the local elevator that includes the destination floor of the authenticated user as a service floor to the destination floor call of the authenticated user, In the aforementioned request step, the number of people indicating the number of authenticated users at each destination floor who are currently using one of the shuttle elevator units is transmitted to the management device. In the allocation step, based on the number of people information and the number of available seats in each of the local elevators, the local elevators are assigned in such a way that the number of local elevators assigned to the authenticated user whose destination floor is the same floor is minimized. Control method.

Images