Landing place destination floor registration system and control method for landing place destination floor registration system

The landing destination floor registration system optimizes elevator allocation by determining compatibility between users and self-propelled devices, enhancing efficiency by allowing shared use without conflicts.

JP7582430B1Active Publication Date: 2024-11-13FUJITEC CO LTD

Patent Information

Application Number
JP2023196062
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-11-17
Publication Date
2024-11-13
Estimated Expiration
2043-11-17

AI Technical Summary

Technical Problem

Existing elevator systems used by robots and humans have inefficiencies in movement coordination, particularly when users and self-propelled devices share elevators, leading to potential conflicts and reduced efficiency.

Method used

A landing destination floor registration system that includes a reception section for user and self-propelled device calls, a determination unit to assess compatibility, and a selection unit to allocate elevators based on permission/disapproval information, ensuring users and devices can share elevators efficiently without conflicts.

Benefits of technology

Improves the movement efficiency of elevator systems by allowing users and self-propelled devices to share elevators while avoiding conflicts, optimizing allocation based on device type compatibility.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007582430000001_ABST
    Figure 0007582430000001_ABST
Patent Text Reader

Abstract

To improve the movement efficiency in an elevator system used by robots and people. [Solution] The platform destination floor registration system (100) includes an acquisition unit (113) that acquires permission / denial information indicating whether or not the user is permitted to ride together with a self-propelled device, which is determined according to the type of self-propelled device, when there is a possibility that a user who has newly registered a platform destination floor call will ride together with a self-propelled device (3) for which a platform destination floor call has been registered, in the cage (81) of the vehicle, and a selection unit (114) that selects a candidate vehicle that can be assigned to the platform destination floor call, excluding vehicles in which the user and the self-propelled device may ride together, from the candidate vehicles for the user, when the permission / denial information indicates that riding together with the self-propelled device is not permitted.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a landing-destination floor registration system that can be used by both people and a self-propelled device, and a control method for the landing-destination floor registration system. [Background technology]

[0002] In recent years, a technology has been known that allows an autonomously traveling robot to use an elevator. Patent Document 1 discloses an autonomous mobile body control device that notifies a device installed in the autonomous mobile body of information indicating whether a user or an autonomous mobile body has gotten on or off an elevator car. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2018 / 066054 Summary of the Invention [Problem to be solved by the invention]

[0004] There is still room for improvement in improving the movement efficiency in elevator systems used by robots and humans. [Means for solving the problem]

[0005] In order to solve the above problems, a landing destination floor registration system according to one embodiment of the present invention is an elevator landing destination floor registration system for an elevator equipped with a plurality of elevators and capable of using a plurality of types of self-propelled devices, comprising: a reception unit that receives a first landing destination floor call by a user and a second landing destination floor call by the self-propelled device; a determination unit that determines whether or not a noted user who has newly registered the first landing destination floor call is likely to ride in the cage of the elevator together with a noted self-propelled device in which the second landing destination floor call has been registered; and a determination unit that, when there is a possibility that the noted user will ride in the cage of the elevator together with the noted self-propelled device, determines whether or not the noted user will ride in the cage of the elevator together with the noted self-propelled device, The device comprises an acquisition unit that acquires permission / denial information indicating permission / denial of riding with the target self-propelled device, a selection unit that selects, from the multiple devices, a first candidate device that can be assigned to the first landing destination floor call and a second candidate device that can be assigned to the second landing destination floor call based on the permission / denial information, and an allocation unit that determines, from the first candidate devices, a device to be assigned to the first landing destination floor call and determines, from the second candidate devices, a device to be assigned to the second landing destination floor call, and when the permission / denial information indicates that riding with the target self-propelled device is not permitted, the selection unit excludes the device in which the target user and the target self-propelled device may ride from the list of first candidate devices.

[0006] In order to solve the above-mentioned problems, a control method for a landing destination floor registration system according to one aspect of the present invention is a control method for an elevator landing destination floor registration system for an elevator capable of using multiple types of self-propelled devices, executed by one or multiple computers, the elevator being equipped with multiple elevator cars, the control method including a reception step of receiving a first landing destination floor call by a user and a second landing destination floor call by the self-propelled device, a determination step of determining whether or not a noted user who has newly registered the first landing destination floor call is likely to ride together with a noted self-propelled device in which the second landing destination floor call has been registered, in the cage of the elevator, and, when there is a possibility that the noted user will ride together with the noted self-propelled device in the cage of the elevator, The method includes an acquisition step of acquiring permission / denial information indicating permission / denial of riding with the target self-propelled device, the permission / denial information being determined according to the type of the target self-propelled device; a selection step of selecting, from the multiple devices, a first candidate device that can be assigned to the first landing destination floor call and a second candidate device that can be assigned to the second landing destination floor call based on the permission / denial information; and an allocation step of determining, from the first candidate devices, a device to be assigned to the first landing destination floor call and determining, from the second candidate devices, a device to be assigned to the second landing destination floor call, wherein, in the selection step, if the permission / denial information indicates that riding with the target self-propelled device is not permitted, the device in which the target user and the target self-propelled device may ride together is excluded from the first candidate devices.

[0007] The landing destination floor registration system according to each aspect of the present invention may be realized by a computer. In this case, the control program for the landing destination floor registration system that realizes the landing destination floor registration system on a computer by causing the computer to operate as each part (software element) of the landing destination floor registration system, and the computer-readable recording medium on which it is recorded, also fall within the scope of the present invention. Effect of the Invention

[0008] According to one aspect of the present invention, it is possible to improve the movement efficiency in an elevator system used by robots and people. [Brief description of the drawings]

[0009] [Figure 1] 1 is a block diagram showing a configuration of a hall / destination floor registration system according to a first embodiment. [Diagram 2] FIG. 13 is a diagram illustrating an example of a robot DB. [Diagram 3] FIG. 13 is a diagram illustrating an example of a user DB. [Figure 4] FIG. 11 is a diagram illustrating an example of a device DB. [Diagram 5] FIG. 13 is a diagram showing an example of a gate DB. [Figure 6] FIG. 11 is a diagram illustrating an example of allocation information. [Figure 7] 11 is a schematic diagram for explaining a specific example of a selection method by a selection unit. FIG. [Figure 8] 10 is a flowchart showing the flow of processing performed by a destination floor registration device or a security gate. [Figure 9] 13 is a flowchart showing the flow of processing performed by a security server. [Figure 10] 13 is a flowchart showing the flow of gate processing. [Figure 11] 11 is a flowchart showing the flow of a destination floor registration device process 1. [Figure 12] 10 is a flowchart showing the flow of processing performed by the destination floor registration device when authentication of a user is successful in the security server. [Figure 13] 13 is a flowchart showing a flow of a destination floor registration device process. [Figure 14] 4 is a flowchart showing the flow of processing performed by a group management control device. [Figure 15] 1 is a flowchart showing the flow of an allocation process 1. [Figure 16] 10 is a flowchart showing the flow of processing performed by a destination floor registration device or a security gate when allocation is performed by the group management control device or when user authentication fails in a security server. [Figure 17]13 is a flowchart showing the flow of an allocation process 2. [Figure 18] 13 is a flowchart showing the flow of an allocation process 2. [Figure 19] 13 is a flowchart showing the flow of allocation processing 3. [Figure 20] FIG. 11 is a block diagram showing a configuration of a hall / destination floor registration system according to a second embodiment. [Figure 21] FIG. 11 is a block diagram showing a configuration of a hall / destination floor registration system according to a third embodiment. [Figure 22] FIG. 11 is a diagram illustrating an example of a user DB according to the third embodiment. [Diagram 23] FIG. 11 is a block diagram showing a configuration of a hall / destination floor registration system according to a fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] [Embodiment 1] <Outline of the boarding hall destination floor registration system 100> An embodiment of the present invention will be described in detail below. Fig. 1 is a block diagram showing the configuration of a hall destination floor registration system 100 according to embodiment 1. As shown in Fig. 1, the hall destination floor registration system 100 includes a group management control device 1, a robot management control device 2, a self-propelled device 3, a security server 4, a destination floor registration device 5, a security gate 6, an elevator control device 7, and an elevator 8.

[0011] The landing destination floor registration system 100 is a landing destination floor registration system for an elevator 8 having a plurality of elevators. A user and a self-propelled device 3 can use the landing destination floor registration system 100, and the landing destination floor registration system 100 accepts registration of a landing destination floor call by the user and the self-propelled device 3. When a user registers a landing destination floor call, the landing destination floor registration system 100 authenticates the user, and accepts registration of the landing destination floor call by the user who has been successfully authenticated.

[0012] The elevator hall destination floor registration system 100 selects candidate elevators that can be assigned to the received elevator hall destination floor call, and determines an elevator to be assigned to the elevator hall destination floor call from among the candidate elevators, notifies the user of the assignment result, and controls the elevator 8 based on the assignment result.

[0013] Furthermore, when a user registers a landing destination floor call, the landing destination floor registration system 100 judges whether or not there is a possibility that the user and a self-propelled device 3 for which a landing destination floor call has already been registered will board the same car 81 in any car of the elevator 8. If there is a car in which the user and the self-propelled device 3 may board the same car 81, the landing destination floor registration system 100 selects a candidate car based on the permission / denial information of the user.

[0014] The permission information is information determined according to the type of the self-propelled device, and is information indicating whether or not the user is permitted to ride in the same car 81 of the elevator 8 as the self-propelled device 3. For example, the permission information is information indicating whether or not the user is permitted to ride in the same car 81 of the elevator 8 as the self-propelled device 3 that performs cleaning, or whether or not the user is permitted to ride in the same car 81 of the elevator 8 as the self-propelled device 3 that performs security. Hereinafter, the user and the self-propelled device 3 riding in the same car 81 of the elevator 8 is also referred to as "riding together."

[0015] Hereinafter, a platform destination floor call by a user is referred to as a first platform destination floor call, and a candidate vehicle for the first platform destination floor call is referred to as a first candidate vehicle. Furthermore, a platform destination floor call by the self-propelled device 3 is referred to as a second platform destination floor call, and a candidate vehicle for the second platform destination floor call is referred to as a second candidate vehicle.

[0016] In addition, a user who has registered a first boarding hall destination floor call for which a candidate vehicle is selected is referred to as a "noted user," and a self-propelled device 3 that can ride together with the noted user in the cage 81 is referred to as a "noted self-propelled device."

[0017] For example, when the permission information of the noted user indicates that the noted user is not permitted to ride with the noted self-propelled device, the hall destination floor registration system 100 excludes a vehicle in which the noted user and the noted self-propelled device may ride together from the first candidate vehicle. For example, when the permission information of the noted user indicates that the noted user is not permitted to ride with a cleaning robot and the type of the noted self-propelled device is a cleaning robot, the hall destination floor registration system 100 excludes a vehicle in which the noted user and the noted self-propelled device may ride together from the first candidate vehicle.

[0018] According to the above configuration, in a first hall destination floor call of a noted user where a self-propelled device 3 of a type that the noted user is not allowed to ride with exists, elevators in which the noted user can ride with the noted self-propelled device of a type that the noted user does not allow to ride with are excluded from the first candidate elevators. Therefore, for the first hall destination floor call, allocation is performed so that the noted user does not ride with a noted self-propelled device of a type that the noted user does not want to ride with, and the noted user can use the elevator 8 without riding with a noted self-propelled device of a type that the noted user does not want to ride with.

[0019] In addition, the first candidate vehicle is selected so as to allow the noted user to ride with the noted self-propelled device of the type that the noted user can ride with. Therefore, for a user who cannot ride with only some types of self-propelled devices, the movement efficiency by the elevator 8 is improved compared to when the allocation is performed so as to avoid riding with all types of self-propelled devices 3.

[0020] <Robot management control device 2, self-propelled device 3> The self-propelled device 3 is an information processing device capable of moving between floors using an elevator 8. The self-propelled device 3 may be, for example, a device such as a robot or a drone capable of autonomous travel. The self-propelled device 3 may be, for example, a security, cleaning, or delivery robot, and may be a device that uses the elevator 8 to complete a given task. The robot management control device 2 is a device that manages the self-propelled device 3, and stores a robot DB (database) 21.

[0021] FIG. 2 is a diagram showing an example of the robot DB 21. As shown in FIG. 2, in the robot DB 21, for example, identification information for identifying the self-propelled device 3 (hereinafter, robot ID), number of users information, and type information are stored in association with each self-propelled device 3. The number of users information is information indicating the size of the space occupied by the self-propelled device 3 in the car 81 of the elevator 8. The number of users information may be information indicating how many standard users the size of the space occupied by the self-propelled device 3 corresponds to. For example, as shown in FIG. 2, the number of users information "3" of the self-propelled device 3 with the robot ID "Robo1" means that the self-propelled device 3 occupies a space for three users.

[0022] The type information is information indicating the type of the self-propelled device 3. The type of the self-propelled device 3 may be the type of function that the self-propelled device 3 has. For example, if the self-propelled device 3 has a delivery function, the type information of the self-propelled device 3 is "delivery". Alternatively, the type of the self-propelled device 3 may be the type of function, such as security or cleaning. Furthermore, the type of the self-propelled device 3 is not limited to the function of the self-propelled device 3. For example, the type of the self-propelled device 3 may be a classification based on the size or weight of the self-propelled device 3.

[0023] When the self-propelled device 3 uses the elevator 8, it transmits information including the departure floor, destination floor, and its own robot ID to the robot management control device 2. Upon receiving this information, the robot management control device 2 identifies the number of people and type information of the self-propelled device 3 based on the robot ID. The robot management control device 2 transmits information for registering a second hall destination floor call, including the robot ID, departure floor, destination floor, type information, and number of people information, to the group management control device 1.

[0024] When the allocation is performed in the group management control device 1, the robot management control device 2 receives the allocation result including the robot ID and the assigned robot number from the group management control device 1. When the robot management control device 2 receives the allocation result, it transmits the allocation result to the self-propelled device 3 that has registered the second hall destination floor call. When the self-propelled device 3 receives the allocation result, it waits for the assigned robot number at the hall of the departure floor and moves between floors using the elevator 8.

[0025] <Security server 4, destination floor registration device 5, security gate 6> The security server 4, the destination floor registration device 5, and the security gate 6 are a group of devices related to hall / destination floor calls of users who use the elevator 8.

[0026] When a user performs an operation for authentication and a hall / destination floor call on the destination floor registration device 5 or the security gate 6, the security server 4 authenticates the user.

[0027] When the security server 4 succeeds in authenticating the user, the user's hall destination floor call is registered, and a car number is assigned to the hall destination floor call. When the hall destination floor call registration is completed, the allocation result is displayed on the destination floor registration device 5 or security gate 6 that the user used for authentication.

[0028] In addition, if there is a possibility that a user who has registered a destination floor call for the first boarding hall may board the same car 81 as the self-propelled device 3, the destination floor registration device 5 or security gate 6 used by the user for authentication will inquire about permission / denial information for the user.

[0029] [Security Server 4] The security server 4 performs processes for authenticating a user and registering the user's hall / destination floor call based on information received from the destination floor registration device 5 or the security gate 6. As shown in Fig. 1, the security server 4 includes a control unit 41 and a storage unit 42. The control unit 41 includes an authentication unit 411. The control unit 41 performs processes related to the authentication of a user and the registration of the user's hall / destination floor call, as well as other processes, such as issuing instructions to the flapper 63 to open or close. The processes of the control unit 41 will be described in detail later.

[0030] (Storage unit 42) As shown in FIG. 1, the storage unit 42 stores a user DB (database) 421, a device DB (database) 422, and a gate DB (database) 423.

[0031] Fig. 3 is a diagram showing an example of the user DB 421. As shown in Fig. 3, the user DB 421 stores user identification information (hereinafter, user ID), information indicating a destination floor, and information indicating an allowed floor, in association with each user. In the user DB 421, the information indicating a destination floor indicates a destination floor when a user uses the security gate 6 to register a landing destination floor call. As shown in Fig. 3, only one floor may be set in advance as the information indicating a destination floor.

[0032] The information indicating permitted floors indicates floors that can be selected as destination floors when a user performs a landing destination floor call registration using the destination floor registration device 5. As shown in Fig. 3, the information indicating permitted floors may set a plurality of floors to which a user can move using the elevator 8.

[0033] For example, a user can have a card storing a user ID read by the reading unit 51 of the destination floor registration device 5 or the reading unit 61 of the security gate 6, thereby authenticating the user and registering a hall / destination floor call.

[0034] The method of authenticating a user is not limited to a method using a card, and may be biometric authentication using biometric information such as a face, a fingerprint, or veins. In this case, it is sufficient that the user DB 421 associates the user ID with pre-registered biometric information for each user.

[0035] Fig. 4 is a diagram showing an example of the device DB 422. As shown in Fig. 4, the device DB 422 stores information related to the destination floor registration device 5 in association with each destination floor registration device 5. The information related to the destination floor registration device 5 includes identification information (reader ID) of the reading unit 51 of the destination floor registration device 5, identification information (device ID) of the display unit 53 corresponding to the reading unit 51, and information indicating the departure floor.

[0036] Fig. 5 is a diagram showing an example of the gate DB 423. As shown in Fig. 5, the gate DB 423 stores information related to the security gate 6 in association with each security gate 6. The information related to the security gate 6 includes identification information (reader ID) of the reading unit 61 of the security gate 6, identification information (device ID) of the display unit 62 corresponding to the reading unit 61, and identification information (gate ID) of the flapper 63 corresponding to the reading unit 61.

[0037] In the device DB 422 and the gate DB 423, the departure floor may be a floor where the destination floor registration device 5 or the security gate 6 is provided. A user who registers a hall destination floor call gets on the elevator 8 from a floor where the destination floor registration device 5 or the security gate 6 used to register the hall destination floor call is provided. Therefore, based on the floor where the destination floor registration device 5 or the security gate 6 is provided, the departure floor, which is the floor where the user gets on the elevator 8, can be specified.

[0038] (Control unit 41) Hereinafter, a description will be given of the processing of the authentication unit 411 included in the control unit 41. When the authentication unit 411 receives an authentication request from the destination floor registration device 5 or the security gate 6, it authenticates the user who has performed an operation to register a hall / destination floor call.

[0039] The authentication unit 411 refers to the user DB 421 and determines whether or not the user ID included in the received authentication request is included in the user DB 421. If the received user ID is included in the user DB 421, the authentication unit 411 determines that the authentication of the user has been successful.

[0040] If the authentication unit 411 succeeds in authenticating the user, it identifies the departure floor and destination floor of the user. The authentication unit 411 identifies the departure floor of the user based on the device DB 422 or the gate DB 423.

[0041] When the sender of the authentication request is the destination floor registration device 5, the authentication unit 411 identifies the permitted floor of the user based on the user DB 421, and transmits information indicating the identified permitted floor to the destination floor registration device 5 that sent the authentication request. When the authentication unit 411 receives information indicating the destination floor input by the user from the destination floor registration device 5, it identifies the received destination floor as the destination floor of the user. When the sender of the authentication request is a security gate 6, the authentication unit 411 refers to the gate DB 423 to identify the destination floor of the user.

[0042] After identifying the departure floor and destination floor of the user, the authentication unit 411 transmits a registration request for requesting hall-destination floor call registration to the group management control device 1. The registration request includes the device ID of the sender of the authentication request, the departure floor of the user, and the destination floor of the user.

[0043] If the received user ID is not included in the user DB 421, the authentication unit 411 determines that authentication of the user has failed. In this case, the authentication unit 411 transmits an error signal indicating that authentication has failed to the group management control device 1 together with the device ID of the source of the authentication request.

[0044] If the sender of the authentication request is a security gate 6, the authentication unit 411 controls the flapper 63 of the security gate 6 based on the authentication result. Specifically, if the authentication of the user is successful, the authentication unit 411 identifies the flapper 63 corresponding to the reading unit 61 of the security gate 6 that is the sender of the authentication request, and transmits a flapper control signal (open) to the gate ID of the flapper 63 to instruct the flapper 63 to open. This opens the flapper 63 of the security gate 6 that the user used to register the authentication and hall destination floor call, allowing the user to pass through.

[0045] If authentication of the user fails, the authentication unit 411 transmits a flapper control signal (close) to the gate ID of the flapper 63 corresponding to the reading unit 61 of the security gate 6 that is the sender of the authentication request, instructing to close the flapper 63. As a result, the flapper 63 of the security gate 6 that the user used to register the authentication and hall destination floor call is closed, and the user who failed authentication cannot pass through.

[0046] [Destination floor registration device 5] The destination floor registration device 5 is a device used by a user to register a landing destination floor call. The destination floor registration device 5 may be provided at the landing of each floor. Also, multiple destination floor registration devices 5 may be provided on one floor. Also, a terminal device such as a smartphone carried by a user may have the function of the destination floor registration device 5.

[0047] As shown in FIG. 1, the destination floor registration device 5 includes a reading unit 51, an input unit 52, and a display unit 53. The reading unit 51, the input unit 52, and the display unit 53 may be an integrated device or may be separate devices. In the following example, the input unit 52 and the display unit 53 are an integrated device such as a touch panel, and the housing of the destination floor registration device 5 includes the reading unit 51 and a touch panel. The reading units 51 of each destination floor registration device 5 are assigned different reader IDs. Furthermore, the input units 52 and the display units 53 are assigned device IDs corresponding to the reader IDs.

[0048] The reading unit 51 is a device such as a card reader capable of reading card information of a card brought into contact with the reading unit 51. The card information includes information for identifying a user, such as the user ID of the user. A user can have his / her user ID read by bringing his / her card into contact with the reading unit 51. The reading unit 51 transmits an authentication request including the read user ID and his / her own reader ID to the security server 4.

[0049] The input unit 52 is a device such as a touch panel, and accepts an input operation by a user. For example, the input unit 52 accepts an operation of inputting a floor by a user. The input unit 52 receives information indicating a permitted floor from the security server 4, and if the input floor is included in the permitted floors, the input floor is set as a destination floor, and the input floor is transmitted to the security server 4 as a device ID, a user ID, and information indicating the destination floor.

[0050] The display unit 53 may be a display device such as a display provided in the destination floor registration device 5 used by the user to make a landing destination floor call, or may be a touch panel that also functions as the input unit 52. For example, the display unit 53 displays a screen such as a numeric keypad for receiving floor input. In addition, when the floor input to the input unit 52 is not included in the permitted floors, the display unit 53 displays a screen showing a message or the like indicating that the input floor is not included in the permitted floors.

[0051] When the display unit 53 receives an allocation result including information indicating the destination floor of the user and the assigned elevator assigned to the user hall-destination floor call from the group management control device 1, the display unit 53 displays a screen indicating the destination floor and the assigned elevator. The display unit 53 also receives an error signal indicating that authentication of the user has failed from the group management control device 1. When the display unit 53 receives the error signal, it displays an error screen including a message indicating that authentication has failed.

[0052] Furthermore, the destination floor registration device 5 inquires of the user about permission information. Specifically, when the display unit 53 receives a ride-along permission request signal from the group management control device 1, it displays a screen inquiring of the user about permission information. The ride-along permission request signal includes information requesting the user to inquire about permission information and type information of the self-propelled device 3 that may ride with the user. Furthermore, the screen displayed by the display unit 53 includes buttons that indicate the possibility of riding with the self-propelled device 3, the type of self-propelled device 3 that may sympathize, and whether or not to permit riding with the self-propelled device 3.

[0053] The input unit 52 receives a selection of permission information indicating whether or not the user is permitted to ride along with the self-propelled device 3, and transmits the selected permission information to the group management control device 1 together with the device ID of the self-propelled device.

[0054] [Security Gate 6] The security gate 6 is a gate through which a user passes to travel between one location and another location in a building in which an elevator 8 is provided. For example, the security gate 6 may be a gate provided at an entrance of a building in which an elevator 8 is provided, through which a user passes to enter or exit the building. One or more security gates 6 may be provided. For example, multiple security gates 6 may be provided on one floor, for example, on a floor on which an entrance or exit of a building is provided. In the following, a configuration in which multiple security gates 6 are provided will be described as an example, as shown in FIG. 1.

[0055] 1, the security gate 6 includes a reading unit 61, a display unit 62, and a flapper 63. The reading unit 61, the display unit 62, and the flapper 63 may be separate devices provided in one housing, or may be an integrated device. In the following, an example will be described in which the reading unit 61, the display unit 62, and the flapper 63 are separate devices, each of which is provided with identification information.

[0056] A different reader ID is assigned to each of the reading units 61 of the multiple security gates 6. A device ID corresponding to the reader ID is assigned to the display unit 62 corresponding to the reading unit 61. A gate ID corresponding to the reader ID is assigned to the flapper 63 corresponding to the reading unit 61.

[0057] The reading unit 61 is a device such as a card reader capable of reading card information of a card that is brought into contact with the reading unit 61. A user can have his / her user ID read by bringing his / her card into contact with the reading unit 61. The reading unit 61 transmits an authentication request including his / her own reader ID and the read user ID to the security server 4.

[0058] The display unit 62 may be a display device such as a display provided in the security gate 6 used by the user to make a landing destination floor call. When the display unit 62 receives an allocation result including information indicating the destination floor of the user and the assigned elevator assigned to the user landing destination floor call from the group management control device 1, it displays a screen indicating the destination floor and the assigned elevator. In addition, the display unit 62 receives an error signal from the group management control device 1 indicating that authentication of the user has failed. When the display unit 62 receives the error signal, it displays an error screen including a message indicating that authentication has failed.

[0059] The flapper 63 opens and closes based on an instruction signal corresponding to the authentication result in the security server 4 , thereby restricting the passage of the user through the security gate 6 .

[0060] When the security server 4 successfully authenticates the user, the flapper 63 receives a gate control signal (open) from the security server 4. Upon receiving the gate control signal (open), the flapper 63 opens. This allows the user to pass through the security gate 6.

[0061] If the security server 4 fails to authenticate the user, the flapper 63 receives a gate control signal (closed) from the security server 4. Upon receiving the gate control signal (closed), the flapper 63 closes. This makes it impossible for the user to pass through the security gate 6.

[0062] The security gate 6 also queries the user for permission information. Specifically, when the display unit 62 of the security gate 6 receives a ride-along permission request signal from the group management control device 1, it displays a screen for querying the user for permission information. The ride-along permission request signal includes information requesting the user to query for permission information and type information of the self-propelled device 3 that may ride with the user. The screen displayed by the display unit 62 also includes buttons that indicate the possibility of riding with the self-propelled device 3, the type of self-propelled device 3 that may sympathize, and whether or not to permit riding with the self-propelled device 3.

[0063] The display unit 62 receives a selection of permission information indicating whether or not the user is permitted to ride along with the self-propelled device 3, and transmits the selected permission information to the group management control device 1 together with the device ID of the self-propelled device.

[0064] <Elevator control device 7, elevator 8> The elevator control device 7 receives information about the allocation result of the hall / destination floor calls for which registration has been completed from the group management control device 1. The information about the allocation result includes information indicating the number of the assigned elevator 8 and information indicating the departure floor and the destination floor. The elevator control device 7 controls the operation of the elevator 8 based on this information. The elevator 8 moves the car 81 between floors and opens and closes the doors under the control of the elevator control device 7.

[0065] The elevator control device 7 may control the operation of one elevator 8, or may control the operation of a plurality of elevators 8.

[0066] <Group management control device 1> The group management control device 1 is a device that receives and assigns information related to a first hall destination floor call by a user or a second hall destination floor call by the self-propelled device 3. The group management control device 1 accepts the first hall destination floor call by a user or the second hall destination floor call by the self-propelled device 3, and selects a candidate floor for each hall destination floor call. The group management control device 1 also determines the assigned floor from the candidate floors, and transmits the assignment result to the elevator control device 7 and the robot management control device 2, destination floor registration device 5, or security gate 6, which are the senders of the hall destination floor calls.

[0067] In particular, when the noted user who has registered the first hall destination floor call does not allow the user to ride with a noted self-propelled device that can ride with the user, the group management control device 1 selects a first candidate device so that the user does not ride with a noted self-propelled device that the user does not allow to ride with. In addition, whether or not a user can ride with the noted self-propelled device is determined for each type of noted self-propelled device. For example, when the noted user who has registered the first hall destination floor call does not allow the user to ride with a self-propelled device 3 of a type that performs delivery, the group management control device 1 excludes a device used by the noted self-propelled device that performs delivery from the first candidate devices.

[0068] The storage unit 12 may store a device DB 121, a gate DB 122, and allocation information 123. The device DB 121 and the gate DB 122 are databases similar to the device DB 422 and the gate DB 423.

[0069] FIG. 6 is a diagram showing an example of the allocation information 123 stored in the storage unit 12. The allocation information 123 stores information on the allocation result of the landing destination floor call in association with each registered landing destination floor call. The information on the allocation result of the landing destination floor call includes information indicating the attribute of the person who registered the landing destination floor call, the departure floor, the destination floor, and the assigned elevator. The attribute of the person who registered the landing destination floor call is either an allowed person, a non-allowed person, or a mobile device representing a self-propelled device 3. An allowed person is a user who allows the self-propelled device 3 to ride with the user. An unallowed person is a user who does not allow at least one type of self-propelled device 3 to ride with the user. As shown in FIG. 6, the allocation information 123 may further include type information of the self-propelled device 3, or information indicating the type of the self-propelled device 3 that the non-allowed person does not allow to ride with the user.

[0070] The control unit 11 executes various controls performed in the group management control device 1. As shown in FIG.

[0071] [Reception Department 111] The reception unit 111 receives a first hall destination floor call from a user, a second hall destination floor call from the self-propelled device 3, and an error signal. The reception unit 111 outputs information related to the received second hall destination floor call and second hall destination floor call to each unit of the control unit 11.

[0072] Specifically, when the security server 4 successfully authenticates the user, the reception unit 111 receives a registration request requesting registration of a first-hall destination floor call from the security server 4. The registration request includes the device ID of the destination floor registration device 5 or security gate 6 used by the user, the departure floor, and the destination floor. The reception unit 111 accepts the registration of the first-hall destination floor call based on the received registration request.

[0073] If the security server 4 fails to authenticate the user, the reception unit 111 receives an error signal and the device ID of the destination floor registration device 5 or security gate 6 used by the user from the security server 4. When the reception unit 111 receives the error signal, it transmits the error signal to the destination floor registration device 5 or security gate 6 corresponding to the device ID.

[0074] Specifically, the reception unit 111 transmits an error signal to the received device ID. As a result, the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 receives the error signal and displays a screen indicating that the authentication has failed.

[0075] In addition, the reception unit 111 receives information for registering a second hall destination floor call from the robot management control device 2. The information for registering a second hall destination floor call includes the departure floor, destination floor, type information, and number of people information of the self-propelled device 3.

[0076] [Determination unit 112] The determination unit 112 determines whether or not the noted user who has newly registered a first hall destination floor call is likely to ride together with the noted self-propelled device in which a second hall destination floor call has been registered, in the car 81 of the elevator, based on the information acquired from the reception unit 111. The determination unit 112 performs the determination for all elevators 8 equipped in the elevator hall destination floor registration system 100.

[0077] For example, when the departure floor of the noted self-propelled device is the first floor and the destination floor is the fourth floor, if the departure floor of the noted user is the first floor and the destination floor is the second floor, the determination unit 112 determines that there is a possibility that the noted user will ride with the noted self-propelled device. Also, when the departure floor of the noted self-propelled device is the third floor and the destination floor is the fourth floor, if the departure floor of the noted user is the first floor and the destination floor is the second floor, the determination unit 112 determines that there is no possibility that the noted user will ride with the noted self-propelled device.

[0078] When there is a possibility that the noted user will ride together with the noted self-propelled device in at least one vehicle, the determination unit 112 outputs the determination result to the acquisition unit 113. On the other hand, when there is no possibility that the noted user will ride together with the noted self-propelled device in all vehicles, the determination unit 112 outputs the determination result to the selection unit 114.

[0079] In addition, the judgment unit 112 judges whether or not there is a possibility that the self-propelled device 3 that has newly registered the second hall destination floor call will ride in the car of the elevator with a user who has registered the first hall destination floor call.

[0080] The determination unit 112 refers to the allocation information 123. When the self-propelled device 3 is allocated to a second hall destination floor call in a certain vehicle, the determination unit 112 determines whether or not there is a possibility that the self-propelled device 3 and a non-permitted person who is not permitted to ride together with the self-propelled device 3 of the type corresponding to the self-propelled device 3 may ride together. The determination unit 112 performs the same determination for all vehicles.

[0081] The determination unit 112 outputs to the selection unit 114 the determination result regarding the self-propelled device 3 that has newly registered the second hall destination floor call.

[0082] [Acquisition part 113] When there is a possibility that the noted user will ride together with the noted self-propelled device in the car 81 of the car, the acquisition unit 113 acquires permission / denial information indicating whether the noted user is permitted to ride together with the noted self-propelled device, which is determined according to the type of the noted self-propelled device. For example, when there is a possibility that the noted user will ride together with the noted self-propelled device in the car of the car, the acquisition unit 113 inquires of the noted user about permission / denial information.

[0083] When the acquisition unit 113 obtains a judgment result from the judgment unit 112 indicating that the noted user is likely to be riding with the noted self-propelled device in at least one vehicle, it inquires about permission information from the destination floor registration device 5 or security gate 6 used by the user.

[0084] Specifically, when the acquisition unit 113 identifies the destination floor registration device 5 or security gate 6 used by the user to register the first hall destination floor call based on the device ID, it transmits a ride-along permission request signal to the destination floor registration device 5 or security gate 6. The ride-along permission request signal is a signal for inquiring about permission information of the noted user according to the type of the noted self-propelled device, and includes type information of the noted self-propelled device.

[0085] The acquisition unit 113 receives the permission / rejection information of the noted user selected by the noted user from the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6. The acquisition unit 113 outputs the received permission / rejection information to the selection unit 114.

[0086] [Selection Department 114] The selection unit 114 selects, based on the permission information, a first candidate elevator that can be assigned to the first hall destination floor call and a second candidate elevator that can be assigned to the second hall destination floor call from the multiple elevators 8. The selection unit 114 outputs the selection result to the assignment unit 115.

[0087] When a first hall destination floor call is registered by a user, the selection unit 114 acquires a determination result as to whether or not the noted user who has newly registered the first hall destination floor call is likely to ride together with the noted self-propelled device in which the second hall destination floor call has been registered, in the car 81 of the car. The selection unit 114 selects a first candidate car based on the determination result.

[0088] For example, the selection unit 114 obtains a determination result from the determination unit 112 indicating that the noted user is unlikely to ride together with the noted self-propelled device for all elevators 8. In this case, the selection unit 114 selects all elevators 8 as first candidate elevators. If the noted user is unlikely to ride together with the noted self-propelled device in all elevators, there is no elevator that cannot be assigned even if the noted user is a non-permitted user.

[0089] Alternatively, the selection unit 114 acquires from the determination unit 112 a determination result indicating that the noted user may ride with the noted self-propelled device for any one of the elevators 8. In this case, the selection unit 114 further acquires permission / denial information indicating permission / denial of the noted user to ride with the noted self-propelled device from the acquisition unit 113. The selection unit 114 selects a first candidate elevator based on the permission / denial information.

[0090] For example, when the permission information of the permitted user indicates that riding with the noted self-propelled device is permitted, the selection unit 114 targets all vehicles, including the vehicles in which the noted user and the noted self-propelled device may ride together, as first candidate vehicles. On the other hand, when the permission information of the noted user indicates that riding with the noted self-propelled device is not permitted, the selection unit 114 excludes vehicles in which the noted user and the noted self-propelled device may ride together from the first candidate vehicles.

[0091] According to the above configuration, in a first hall destination floor call of a noted user with a self-propelled device 3 of a type that the noted user does not permit to ride with, an elevator in which the noted user can ride with the noted self-propelled device of a type that the noted user does not permit to ride with is excluded from the first candidate elevators. Therefore, for the first hall destination floor call, allocation is performed so that the noted user does not ride with a self-propelled device 3 of a type that the noted user does not want to ride with, and the noted user can use the elevator 8 without riding with a self-propelled device 3 of a type that the noted user does not want to ride with.

[0092] In addition, the first candidate vehicle is selected so as to allow the user of interest to ride with the type of self-propelled vehicle that the user of interest can ride with. Therefore, for a user who cannot ride with only some types of self-propelled vehicles, the travel efficiency is improved compared to when the vehicle is assigned so as to avoid riding with all types of self-propelled vehicles.

[0093] When a second hall destination floor call by the self-propelled device 3 is registered, the selection unit 114 acquires a judgment result as to whether or not the self-propelled device that has newly registered the second hall destination floor call is likely to ride together with a user who has registered the first hall destination floor call in the car 81 of the vehicle. The selection unit 114 selects a second candidate vehicle based on the judgment result. Specifically, the selection unit 114 excludes a vehicle that is likely to ride together with a non-allowed person who does not allow the self-propelled device 3 to ride together with the type of self-propelled device 3 to which the self-propelled device 3 corresponds, from the second candidate vehicles for the second hall destination floor call.

[0094] As a result, even if a new self-propelled device 3 registers a second hall destination floor call, the allocation unit 115 performs allocation so that the self-propelled device 3 does not ride with a type of self-propelled device 3 that a user who has registered a first hall destination floor call does not want to ride with.

[0095] Furthermore, the selection unit 114 may select the second candidate vehicle taking into consideration the space occupied by the self-propelled device 3 in the car 81. Specifically, the selection unit 114 specifies the number of people who can ride in the car 81 at the time when the self-propelled device 3 gets on, based on the allocation information 123 and the number of people that can be accommodated in the car 81. The selection unit 114 determines for each vehicle whether the self-propelled device 3 can ride in the car 81, based on the number of people information of the self-propelled device 3 and information indicating the number of people who can ride in the car 81 at the time when the self-propelled device 3 gets on.

[0096] The selection unit 114 excludes a vehicle that it has determined that the self-propelled device 3 cannot ride in the cage 81 from the second candidate vehicles, and sets a vehicle in which the self-propelled device 3 can ride in the cage 81 as the second candidate vehicle. This allows the selection unit 114 to select a vehicle in which the self-propelled device 3 can ride as the second candidate vehicle. When the selection unit 114 selects the second candidate vehicle taking into consideration the space that the self-propelled device 3 occupies in the cage 81, it selects a vehicle having space in which the self-propelled device 3 can ride from the vehicles remaining after excluding vehicles in which the self-propelled device 3 is riding with an unacceptable person.

[0097] [Allocation Section 115] The allocation unit 115 acquires information indicating the candidate elevators selected by the selection unit 114. The allocation unit 115 allocates an optimal elevator from the candidate elevators to the hall destination floor call. The allocation unit 115 determines an elevator to be allocated to the first hall destination floor call from the first candidate elevator, and determines an elevator to be allocated to the second hall destination floor call from the second candidate elevator. The method by which the allocation unit 115 determines an assigned elevator may be an allocation method based on a commonly used selective collective operation. After determining an assigned elevator, the allocation unit 115 stores an allocation result for the assigned hall destination floor call in the allocation information 123 of the storage unit 12.

[0098] Furthermore, the allocation unit 115 transmits the allocation result to the sender of the hall destination floor call. Specifically, when the allocation unit 115 has performed allocation for the first hall destination floor call, it transmits information indicating the allocation result to the device ID included in the registration request. The information indicating the allocation result includes information indicating the destination floor of the user and information indicating the assigned elevator. This allows the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 used by the user to receive the information indicating the allocation result.

[0099] When the allocation unit 115 has performed allocation for the second hall destination floor call, it transmits to the robot management control device 2 the robot ID of the self-propelled device 3 that has registered the second hall destination floor call and information indicating the assigned robot number.

[0100] As described above, when the noted user and the noted self-propelled device can ride together, an inquiry is made to the user, and the acquisition unit 113 acquires the permission / denial information of the noted user. Then, based on the permission / denial information acquired by the acquisition unit 113, the selection unit 114 selects a first candidate device, and the allocation unit 115 allocates a device.

[0101] This allows the hall destination floor registration system 100 to perform allocation based on the inquiry result of the acquisition unit 113. For example, when the permission information obtained as a result of the inquiry indicates that the noted user is not permitted to ride with the self-propelled device 3 that may ride with him / her, allocation can be performed by excluding a car number in which the noted user and a type of noted self-propelled device that the noted user does not want to ride with are riding together. Also, when the permission information obtained as a result of the inquiry indicates that riding with the noted self-propelled device is permitted, the optimal car number is assigned to the first hall destination floor call, thereby improving the movement efficiency of the noted user.

[0102] In addition, since no inquiry is made when the user is not riding with the self-propelled device in the optimal vehicle, the possibility of unnecessary inquiries being made and increasing the effort required for the user of interest to select permission / denial information can be reduced.

[0103] [Specific example of selection method by selection unit 114] A specific example of a method in which the selection unit 114 selects a candidate elevator will be described below with reference to Fig. 7. Fig. 7 is a schematic diagram for explaining a specific example of a selection method by the selection unit 114. As shown in Fig. 7, the following description will be given taking as an example a configuration in which the hall-destination-floor registration system 100 includes six elevators 8, elevators A to F.

[0104] In Fig. 7, A to F respectively indicate cages 81 of elevators 8, A to F. A circle indicates that an acceptable person is aboard or is scheduled to board. A black circle indicates that a non-acceptable person who is not permitted to ride with any type of self-propelled device 3 is aboard or is scheduled to board. A square indicates that a self-propelled device 3 is aboard or is scheduled to board. In Fig. 7, a solid square indicates a self-propelled device 3 whose type is a cleaning robot, and a dashed square indicates a self-propelled device 3 whose type is a delivery robot.

[0105] For example, in Fig. 7, car C has one permissible person on board or has been assigned to a first hall destination floor call by a permissible person, and a permissible person is scheduled to board. Also, car C has one non-permissible person on board or has been assigned to a first hall destination floor call by a non-permissible person, and a non-permissible person is scheduled to board.

[0106] First, a case will be described where each elevator 8 is in a usage state as shown in FIG. 7 and a newly registered hall destination floor call is a first hall destination floor call of a user.

[0107] Below, we will take as an example a case where the departure floor of the self-propelled device 3 using unit B is the 3rd floor and the destination floor is the 4th floor, the departure floor of the self-propelled device 3 using unit E is the 4th floor and the destination floor is the 5th floor, and the departure floor of the self-propelled device 3 using unit F is the 5th floor and the destination floor is the 1st floor.

[0108] As an example, if the departure floor of the noted user who has registered the first hall destination floor is the first floor and the destination floor is the second floor, the noted user will not ride with any of the self-propelled devices 3 using the elevator 8. In this case, the determination unit 112 outputs a determination result indicating that the noted user is not likely to ride with the noted self-propelled device for all elevators to the selection unit 114. Upon acquiring the determination result, the selection unit 114 selects all elevators 8 as first candidate elevators.

[0109] As another example, if the departure floor of the noted user who has registered the first hall destination floor is the second floor and the destination floor is the fifth floor, there is a possibility that the noted user will ride together with the self-propelled device 3 using unit B and the self-propelled device 3 using unit E. In this case, the determination unit 112 outputs a determination result indicating that the noted user is likely to ride together with the noted self-propelled device in units B and E to the acquisition unit 113. The acquisition unit 113 transmits a ride-along permission request signal to the destination floor registration device 5 or security gate 6 used by the noted user, and the selection unit 114 receives the result of the inquiry.

[0110] If the result of the inquiry is that the permission information of the noted user indicates that riding with the cleaning robot and the delivery robot is permitted, the selection unit 114 selects all robots, including robots B and E, as first candidate robots.

[0111] If, as a result of the inquiry, the permission information of the noted user indicates that the user is not permitted to ride with both a cleaning robot and a delivery robot, the selection unit 114 excludes machines B and E from the first candidate machines, and selects machines A, C to D, and F as the first candidate machines.

[0112] Furthermore, if the result of the inquiry indicates that the permission information of the noted user indicates that riding with a cleaning robot is not permitted but riding with a delivery robot is permitted, the selection unit 114 excludes only machine B from the list of first candidate machines, and selects machines A and machines C to F as first candidate machines.

[0113] Next, a case will be described in which, when each elevator 8 is in a usage state as shown in Fig. 7, a newly registered hall destination floor call is a second hall destination floor call of the self-propelled device 3. In addition, a case will be described in which the type of the self-propelled device 3 that has registered the second hall destination floor call is a delivery robot, as an example.

[0114] In the following, we will explain an example where the departure floor of a non-allowed passenger using flight C is the 3rd floor and the destination floor is the 4th floor, and the departure floor of a non-allowed passenger using flight D is the 4th floor and the destination floor is the 5th floor.

[0115] As an example, if the departure floor of the self-propelled device 3 that has registered the second hall destination floor is the first floor and the destination floor is the second floor, the self-propelled device 3 will not ride with any unacceptable person using the elevator 8. In this case, the determination unit 112 outputs a determination result indicating that the self-propelled device 3 is unlikely to ride with any unacceptable person for all elevators to the selection unit 114. Upon acquiring the determination result, the selection unit 114 selects all elevators 8 as second candidate elevators.

[0116] As another example, if the departure floor of the self-propelled device 3 that has registered the second hall destination floor is the second floor and the destination floor is the fifth floor, there is a possibility that the self-propelled device 3 will ride together with the non-allowed person using unit C and the non-allowed person using unit D. In this case, the determination unit 112 outputs to the selection unit 114 a determination result indicating that there is a possibility that the self-propelled device 3 will ride together with the non-allowed person in unit C and unit D.

[0117] The selection unit 114 acquires the permission / denial information of the non-allowed person stored in the allocation information 123, and identifies the type of self-propelled device 3 that the non-allowed person does not allow to ride with. The selection unit 114 selects a second candidate device based on the type of self-propelled device 3 that the non-allowed person does not allow to ride with.

[0118] For example, if the type of self-propelled device 3 that the non-allowed person using machine C does not allow to ride with is a delivery robot, and the type of self-propelled device 3 that the non-allowed person using machine D does not allow to ride with is a cleaning robot, the selection unit 114 excludes machine C from the second candidate machine. On the other hand, the selection unit 114 targets machine D as a second candidate machine, and ultimately selects machines A to B and machines D to F as second candidate machines.

[0119] <An example of the processing flow of the landing destination floor registration system 100> 8 to 19 are flow charts showing an example of the flow of processing performed by the elevator-hall / destination floor registration system 100. Hereinafter, the flow of processing performed by the elevator-hall / destination floor registration system 100 will be described with reference to FIGS.

[0120] [certification] 8 to 11 are flowcharts showing the flow of processing carried out in the elevator-hall / destination floor registration system 100 for authenticating a user.

[0121] (Processing performed by destination floor registration device 5 or security gate 6 (card reading)) FIG. 8 shows the flow of processing performed by the destination floor registration device 5 or the security gate 6.

[0122] When a user wishes to register a landing destination floor call, the user touches a card to the reading unit 51 of the destination floor registration device 5 or the reading unit 61 of the security gate 6. When the card touches the reading unit 51 or the reading unit 61, the reading unit 51 or the reading unit 61 reads the card information from the card. When the reading unit 51 or the reading unit 61 acquires the user ID included in the card information (YES in S1), it transmits data including its own reader ID and the read user ID to the security server 4 (S2).

[0123] (Processing performed by Security Server 4) FIG. 9 shows the flow of processing performed by the security server 4.

[0124] When the control unit 41 of the security server 4 receives data from the reading unit 51 of the destination floor registration device 5 or the reading unit 61 of the security gate 6 (YES in S11), it refers to the gate DB 423. Based on the gate DB 423, the control unit 41 determines whether or not the reader ID of the reading unit 61 of the security gate 6 is included in the received data (S12).

[0125] If the received data includes the reader ID of the reading unit 61 of the security gate 6 (YES in S12), that is, if the card information is read by the reading unit 61 of the security gate 6, the security server 4 performs gate processing (S13). The gate processing is a process performed when the security server 4 receives an authentication request from the security gate 6, for authenticating the user and requesting registration of a hall / destination floor call. The gate processing will be described in detail later.

[0126] If the received data does not include the reader ID of the reading unit 61 of the security gate 6 (NO in S12), the control unit 41 of the security server 4 refers to the device DB 422. The control unit 41 judges whether or not the received data includes the reader ID of the reading unit 51 of the destination floor registration device 5 based on the device DB 422 (S14). If the received data includes the reader ID of the reading unit 51 of the destination floor registration device 5 (YES in S14), that is, if the card information is read by the reading unit 51 of the destination floor registration device 5, the security server 4 performs destination floor registration device process 1 (S15). The destination floor registration device process 1 is a process for authenticating a user that is performed when the security server 4 receives an authentication request from the destination floor registration device 5. The details of the destination floor registration device process 1 will be described later.

[0127] If the received data does not include the reader ID of the reading unit 51 of the destination floor registration device 5 (NO in S14), the control unit 41 of the security server 4 performs destination floor registration device processing 2 (S16). NO in step S14 means that the security server 4 has received information indicating a destination floor input by a user from the destination floor registration device 5. The destination floor registration device processing 2 is a process for requesting the security server 4 to register a hall destination floor call of the user based on the information received from the destination floor registration device 5. The details of the destination floor registration device processing 2 will be described later.

[0128] (Gate processing) FIG. 10 shows a flow of the gate process shown in step S13 of FIG.

[0129] In the gate process, first, the authentication unit 411 of the security server 4 refers to the gate DB 423 and acquires information indicating the device ID, the gate ID, and the departure floor (S21). Next, the authentication unit 411 refers to the user DB 421 and determines whether the user ID received from the security gate 6 is registered in the user DB 421 (S22). This allows authentication of the user.

[0130] If the user ID is registered in the user DB 421 (YES in S22), the authentication unit 411 determines that authentication of the user has been successful. In this case, the authentication unit 411 identifies a gate ID corresponding to the reader ID of the reading unit 61 of the security gate 6, and transmits a gate control signal (open) to the identified gate ID (S23). This opens the flapper 63 of the security gate 6 that includes the reading unit 61 that the user has caused to read the card information, allowing the user to pass through.

[0131] Next, when the authentication of the user is successful, the authentication unit 411 refers to the user DB 421 and acquires information indicating the destination floor of the user corresponding to the user ID (S24: acquisition step). The authentication unit 411 also refers to the gate DB 423 and acquires information indicating the device ID of the display unit 62 and the floor on which the security gate 6 is located, i.e., the departure floor of the user, based on the reader ID of the reading unit 61 of the security gate 6. The authentication unit 411 transmits the device ID of the display unit 62 of the security gate 6 and information indicating the departure floor and destination floor of the user to the group management control device 1 (S25).

[0132] If the user ID is not registered in the user DB 421 (NO in S22), the authentication unit 411 determines that authentication of the user has failed. In this case, the authentication unit 411 identifies a gate ID corresponding to the reader ID of the reading unit 61 of the security gate 6, and transmits a gate control signal (close) to the identified gate ID (S26). This closes the flapper 63 of the security gate 6 including the reading unit 61 from which the user has read the card information, preventing the user from passing through. The authentication unit 411 also transmits the device ID of the display unit 62 of the security gate 6 and an error signal indicating that authentication of the user has failed to the group management control device 1 (S27).

[0133] (Destination floor registration device processing 1) FIG. 11 shows a flow of the destination floor registration device process 1 shown in step S15 of FIG.

[0134] In the destination floor registration device process 1, first, the authentication unit 411 refers to the device DB 422 and acquires the device ID of the reading unit 51 of the destination floor registration device 5 (S31). Next, the authentication unit 411 refers to the user DB 421 and determines whether or not the user ID received from the destination floor registration device 5 is registered in the user DB 421 (S32). This allows authentication of the user.

[0135] If the user ID is registered in the user DB 421 (YES in S32), the authentication unit 411 determines that the authentication has been successful. In this case, the authentication unit 411 acquires information indicating the permitted floors of the user identified by the user ID based on the user DB 421 (S33). The authentication unit 411 transmits the user ID and the information indicating the permitted floors to the destination floor registration device 5 that is the data transmission source (S34).

[0136] If the user ID is not registered in the user DB 421 (NO in S32), the authentication unit 411 determines that authentication of the user has failed. In this case, the authentication unit 411 transmits the device ID and an error signal indicating that authentication of the user has failed to the group management control device 1 (S35).

[0137] [allocation] 12 to 19 are flowcharts showing the flow of processing when the elevator-hall / destination floor registration system 100 performs allocation to an elevator-hall / destination floor call.

[0138] (Processing performed by destination floor registration device 5) FIG. 12 shows the flow of processing performed by the destination floor registration device 5 when the security server 4 has successfully authenticated the user.

[0139] The process shown in FIG. 12 is performed when the security server 4 has successfully authenticated the user, that is, after the result of step S32 in the destination floor registration device process 1 shown in FIG. 11 becomes YES and the process of step S34 has been performed.

[0140] After the process of step S34 is performed, the destination floor registration device 5 receives data including the user ID and information indicating the permitted floor from the security server 4 (YES in S41). When the destination floor registration device 5 receives the above-mentioned data, it starts a timer (S42). After the timer is started, if a destination floor is not input to the input unit 52 (NO in S43), the destination floor registration device 5 determines whether a predetermined time has elapsed (S44). If the predetermined time has not elapsed (NO in S44), the process returns to step S43. If a destination floor is not input to the input unit 52 (NO in S43) and the predetermined time has elapsed (YES in S44) after the timer is started, the destination floor registration device 5 ends the process.

[0141] When a destination floor is input to the input unit 52 within a predetermined time after the timer is started (YES in S43), the destination floor registration device 5 judges whether or not the destination floor is included in the permitted floors (S45). When the input destination floor is included in the permitted floors (YES in S45), the destination floor registration device 5 transmits the device ID of its own device, the user ID of the user, and information indicating the input destination floor to the security server 4 (S46). When the destination floor is not included in the permitted floors (NO in S45), the display unit 53 of the destination floor registration device 5 displays an error screen indicating that the input floor is not included in the permitted floors (S47). After step S47, the process returns to step S42.

[0142] (Destination floor registration device processing 2) FIG. 13 shows a flow of the destination floor registration device process 2.

[0143] When the security server 4 receives data from the destination floor registration device 5 and the received data does not include the reader ID of the reading unit 51 of the destination floor registration device 5 (NO in S14 of FIG. 9), destination floor registration device process 2 (S16 of FIG. 9) is performed. When the received data does not include the reader ID of the reading unit 51 of the destination floor registration device 5, the data that the security server 4 receives from the destination floor registration device 5 includes the device ID of the destination floor registration device 5, the user ID of the user, and information indicating the destination floor of the user.

[0144] In the destination floor registration device process 2, first, the authentication unit 411 refers to the device DB 422 and acquires information indicating the floor where the reading unit 51 of the destination floor registration device 5 is installed, i.e., the departure floor of the user (S51). The authentication unit 411 transmits the device ID of the destination floor registration device 5 and information indicating the departure floor and destination floor of the user to the group management control device 1 (S52).

[0145] (Processing performed by group management control device 1) FIG. 14 shows the flow of processing performed by the group management control device 1. The processing shown in FIG. 14 is performed when authentication is successful in the gate processing shown in FIG. 10 (YES in S22). Alternatively, the processing shown in FIG. 14 is performed after authentication is successful in the destination floor registration device processing 1 shown in FIG. 11 (YES in S32) and the destination floor registration device processing 2 shown in FIG. 13 is performed (after S53). The processing shown in FIG. 14 is also performed when authentication is unsuccessful in the gate processing shown in FIG. 10 or the destination floor registration device processing 1 shown in FIG. 11 (NO in S22 or NO in S32). Furthermore, the processing shown in FIG. 14 is also performed after a selection is made for permission information in the processing shown in FIG. 16 described later (after S87).

[0146] First, the reception unit 111 of the group management control device 1 judges whether or not data has been received from the security server 4 (S61). When data is received from the security server 4 (YES in S61), the reception unit 111 judges whether or not information indicating a destination floor is included in the received data (S62). When information indicating a destination floor is included in the received data (YES in S62), the group management control device 1 accepts a first hall destination floor call (S63: reception step) and performs allocation process 1 (S64). Details of allocation process 1 will be described later.

[0147] Next, a case where the received data does not include information indicating the destination floor (NO in S62) will be described. Specifically, the case where NO in step S62 occurs when the user authentication fails in the gate process or the destination floor registration device process 1 and an error signal indicating the failure of the user authentication is received.

[0148] In this case, the group management control device 1 transmits an error signal indicating that authentication of the user has failed to the device ID received together with the error signal (S65). The process performed in the destination floor registration device 5 or the security gate 6 after step S65 will be described later.

[0149] If the reception unit 111 has not received data from the security server 4 (NO in S61), the reception unit 111 judges whether data has been received from the destination floor registration device 5 or the security gate 6 (S66). If the reception unit 111 has received data from the destination floor registration device 5 or the security gate 6 (YES in S66: acquisition step), this is when the reception unit 111 has received information including permission / denial information selected by the noted user as a result of an inquiry to the noted user. In this case, the group management control device 1 performs allocation process 2 (S67). Details of allocation process 2 will be described later.

[0150] If the reception unit 111 has not received data from the security server 4, the destination floor registration device 5, or the security gate 6 (NO in S66), the reception unit 111 judges whether or not data has been received from the robot management control device 2 (S68). When data has been received from the robot management control device 2, it means that the self-propelled device 3 is requesting registration of a second hall destination floor call.

[0151] When the self-propelled device 3 registers a second hall destination floor call, the self-propelled device 3 transmits a usage request including a robot ID and information indicating the departure floor and the destination floor to the robot management control device 2. When the robot management control device 2 receives the usage request, it refers to the robot DB 21 and acquires the number of people information and type information of the self-propelled device 3 based on the robot ID of the self-propelled device 3. The robot management control device 2 transmits data including the robot ID of the self-propelled device 3, information indicating the departure floor and the destination floor, type information, and number of people information to the group management control device 1. When the group management control device 1 receives the data from the robot management control device 2 (YES in S68), it accepts the second hall destination floor call (S69: acceptance step) and performs allocation process 3 (S70). Details of allocation process 3 will be described later.

[0152] Moreover, if the group management control device 1 has not received data from any of the security server 4, the destination floor registration device 5, the security gate, and the robot management control device 2 (NO in S68), the process returns to step S61.

[0153] (Allocation process 1) FIG. 15 shows the flow of allocation process 1. Details of allocation process 1 will be described below with reference to FIG. 15. Allocation process 1 is a process that is performed when a first-hall destination floor call is registered by a user. When allocation process 1 is performed, reception unit 111 receives information from security server 4, including information indicating the user's destination floor and the device ID of destination floor registration device 5 or security gate 6 used to make the first-hall destination floor call. Reception unit 111 outputs the received information to determination unit 112.

[0154] The determination unit 112 identifies the departure floor of the noted user based on the received device ID (S71). Next, the determination unit 112 determines whether or not there is a car number in which the noted user and the noted self-propelled device may ride together among the elevators 8 (S72: determination step).

[0155] If there is no possibility that the noted user and the noted self-propelled device will ride together in all elevators 8 (NO in S72), the judgment unit 112 outputs the judgment result to the selection unit 114. When the selection unit 114 acquires a judgment result indicating that there is no possibility that the noted user and the noted self-propelled device will ride together, it selects all elevators 8 as allocation candidate cars (first candidate cars) (S73: selection step). The selection unit 114 outputs information indicating the selected first candidate car to the allocation unit 115.

[0156] When the allocation unit 115 acquires the information indicating the first candidate vehicle, it selects the optimal vehicle from the first candidate vehicles and allocates it to the first hall destination floor call (S74: allocation step). The allocation unit 115 transmits information indicating the user's destination floor and the allocated vehicle to the destination floor registration device 5 or security gate 6 used by the user (S75). As a result, the destination floor registration device 5 or security gate 6 notifies the user of the allocated vehicle. The processing performed in the destination floor registration device 5 or security gate 6 will be described later.

[0157] When there is a possibility that the noted user and the noted self-propelled device will ride together in any one of the elevators 8 (YES in S72), the determination unit 112 outputs the result of the determination to the acquisition unit 113. When the acquisition unit 113 acquires the result of the determination, it refers to the allocation information 123 and identifies type information of the noted self-propelled device that may ride together with the noted user (S76). Next, the acquisition unit 113 transmits a ride-along permission / denial request signal and type information to the destination floor registration device 5 or security gate 6 used by the user (S77). As a result, the destination floor registration device 5 or security gate 6 inquires of the user about the permission / denial information. The processing performed in the destination floor registration device 5 or security gate 6 will be described later.

[0158] (Processing performed by the destination floor registration device 5 or the security gate 6) Fig. 16 shows the flow of processing performed by the destination floor registration device 5 or the security gate 6. The processing performed by the destination floor registration device 5 or the security gate 6 will be described below with reference to Fig. 16.

[0159] The process shown in FIG. 16 is performed after the group management control device 1 receives an error signal from the security gate 6 in the process shown in FIG. 14 and the group management control device 1 transmits an error signal to the destination floor registration device 5 or the security gate 6 (after S65). The process shown in FIG. 16 is also performed after the allocation to the first landing destination floor call is performed in the allocation process 1 (after S75), or after the boarding permission request signal is transmitted to the destination floor registration device 5 or the security gate 6 in the allocation process 1 (after S77). The process shown in FIG. 16 is also performed after the allocation to the first landing destination floor call is performed in the allocation process 2 described later (after S99). Note that, hereinafter, the process after the boarding permission request signal is transmitted to the destination floor registration device 5 or the security gate 6 in the allocation process 1 will be described, and other processes will be described later.

[0160] First, the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 determines whether or not data has been received from the group management control device 1 (S81). When data has been received from the group management control device 1 (YES in S81), the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 determines whether or not a "passenger permission request signal" has been received from the group management control device 1 (S82).

[0161] When a "ride-along permission request signal" is received from the group management control device 1 (YES in S82), the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 displays a screen for selecting whether or not to allow ride-along with the self-propelled device 3 of the type to which the self-propelled device of interest belongs (S83). Next, the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 starts a timer to measure the time since the inquiry screen was displayed (S84).

[0162] Next, the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 determines whether or not the user has selected whether or not to allow passengers to ride together (S85). If no selection has been made (NO in S85), the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 determines whether a predetermined time has elapsed (S86). If the predetermined time has not elapsed (NO in S86), the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 performs the process of step S85 again.

[0163] If permission or disapproval of riding has not been selected and a predetermined time has elapsed (YES in S86), the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 displays a default screen (S88), and the processing ends.

[0164] In this case, the permission / rejection information indicating whether or not the noted user is permitted to ride along is not transmitted to the group management control device 1, and therefore the subsequent processing is not performed in the group management control device 1. Therefore, when an inquiry is made and the permission / rejection information is not selected within a predetermined time, the first hall destination floor call by the user is not assigned.

[0165] When "passenger permission or refusal" is selected (YES in S85), the input unit 52 of the destination floor registration device 5 or the display unit 62 of the security gate 6 accepts the selection. The input unit 52 of the destination floor registration device 5 or the display unit 62 of the security gate 6 transmits the device ID, the destination floor, and the selected permission or refusal information to the group management control device 1 (S87). Thereafter, the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 displays a default screen (S88) and ends the processing. Note that, when "passenger permission or refusal" is selected, the display unit 62 of the destination floor registration device 5 or the display unit 62 of the security gate 6 may display a screen indicating that the selection of "passenger permission or refusal" has been accepted.

[0166] (Allocation process 2) Figures 17 and 18 show the flow of allocation process 2 shown in step S67 in Figure 14. Allocation process 1 is an allocation process for a first hall destination floor call. When allocation process 2 is performed, the reception unit 111 of the group management control device 1 receives data including the device ID of the reading unit 51 of the destination floor registration device 5 or the reading unit 61 of the security gate 6, information indicating the departure floor and destination floor of the user, and permission / denial information of the user.

[0167] The reception unit 111 identifies the departure floor of the user based on the received data (S101). Next, the reception unit 111 acquires the permission information of the user based on the received data (S102). The reception unit 111 outputs the device ID, information indicating the departure floor and destination floor of the user, and the permission information of the user to the determination unit 112.

[0168] When the determination unit 112 acquires each piece of information from the reception unit 111, the determination unit 112 determines whether the person who made the hall destination floor call is an authorized person or an unauthorized person, that is, whether the user's permission information is authorized or not (S103). Specifically, the determination unit 112 determines whether the acquired permission information permits riding with any type of self-propelled device 3.

[0169] When the permission information indicates that the noted user and the noted self-propelled device are permitted to ride together (YES in S103), the judgment unit 112 outputs the judgment result to the selection unit 114. When the selection unit 114 acquires the judgment result indicating that the permission information indicates that the noted user and the noted self-propelled device are permitted to ride together, it selects all elevators 8 as first candidate elevators that are candidate elevators for the first hall destination floor call (S104: selection step). After step S104, the process proceeds to step S121 shown in FIG. 18.

[0170] If the permission information indicates that the noted user and the noted self-propelled device are not permitted to ride together (NO in S103), the judgment unit 112 makes a judgment to identify the car number in which the noted user may ride together with the noted self-propelled device.

[0171] The determination unit 112 sets the elevator number to be the object of the determination as the Car number. Car is a numerical value, and corresponds to each of the elevators equipped in the hall-destination-floor registration system 100. For example, if the hall-destination-floor registration system 100 has three elevators, A to C, a determination is made for elevator A when Car=1, for elevator B when Car=2, and for elevator C when Car=3.

[0172] The determination unit 112 first assigns 1 to the variable Car and performs a determination on the first car (S105). When the determination unit 112 assigns the Car car based on the departure floor and destination floor of the non-allowed person and the allocation information 123, the determination unit 112 determines whether or not the non-allowed person is likely to ride with the self-propelled device of interest in the cage 81 of the Car car (S106: determination step).

[0173] When there is no possibility that the non-allowed person will ride with the noted self-propelled device (NO in S106), the judgment unit 112 outputs the result of the judgment to the selection unit 114. When the selection unit 114 obtains a judgment result indicating that there is no possibility that the non-allowed person will ride with the noted self-propelled device in the Car number, it selects the Car number as the first candidate number (S107: selection step). When there is a possibility that the non-allowed person will ride with the noted self-propelled device (YES in S106), the judgment unit 112 outputs the result of the judgment to the selection unit 114. When the selection unit 114 obtains a judgment result indicating that there is a possibility that the non-allowed person will ride with the noted self-propelled device in the Car number, it excludes the Car number from the first candidate number (S108: selection step).

[0174] The determination unit 112 increments the variable Car (S109) after outputting the determination result to the selection unit 114. For example, when the determination unit 112 has performed the determination for the first car number, the determination unit 112 selects the second car number as the next Car number.

[0175] If the value of the variable Car is less than or equal to the total number of elevators 8 (NO in S110), that is, if the determination has not been completed for all elevators, the process returns to step S106, and the processes of steps S106 to S110 are repeated until step S110 is YES. If the value of the variable Car is greater than the total number of elevators 8 (YES in S110), that is, if the determination has been completed for all elevators, the determination unit 112 outputs information indicating that the determination has been completed to the selection unit 114. Upon acquiring this information, the selection unit 114 determines whether or not a first candidate elevator exists (S111).

[0176] If the first candidate elevator does not exist (NO in S111), the process returns to step S105. If the first candidate elevator does not exist, it means that there is no elevator that can be assigned to the first hall destination floor call of the non-allowed person. In this case, the processes of steps S105 to S111 are repeated until step S111 becomes YES. If the first candidate elevator exists (YES in S111), that is, if there is an elevator that can be assigned to the first hall destination floor call of the non-allowed person, the process proceeds to step S121 shown in FIG. 18.

[0177] After the process of step S104 or after the process of step S111, the selection unit 114 outputs to the allocation unit 115 information indicating the selected candidate machine (first candidate machine).

[0178] When the allocation unit 115 acquires the information indicating the first candidate elevator, it determines an assigned elevator to be assigned to the hall destination floor call from among the first candidate elevators. Specifically, the allocation unit 115 allocates an optimal elevator to the first hall destination floor call from among the first candidate elevators (S121: allocation step). An allocation method based on selective collective operation may be used to determine the assigned elevator. For example, the allocation unit 115 may determine, from among the candidate elevators, a elevator that is optimal in terms of the operation efficiency of the elevator 8 as the assigned elevator.

[0179] When the allocation unit 115 has determined the assigned elevator, it identifies the display unit 53 or the display unit 62 of the destination floor registration device 5 or the security gate 6 used by the user who registered the first hall destination floor call, based on the device ID received by the reception unit 111. The allocation unit 115 transmits information indicating the destination floor and the assigned elevator to the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 (S122). The processing performed in the destination floor registration device 5 or the security gate 6 will be described later.

[0180] (Allocation process 3) Fig. 19 shows the flow of allocation process 3 shown in step S70 of Fig. 14. Allocation process 3 is an allocation process for a second hall destination floor call. When allocation process 3 is performed, the reception unit 111 of the group management control device 1 receives data including the device ID of the self-propelled device 3, information on the number of people, and information indicating the departure floor and destination floor from the robot management control device 2. The reception unit 111 outputs each piece of received information to the selection unit 114.

[0181] The selection unit 114 selects the second candidate vehicle (S131 to S137). First, the selection unit 114 assigns 1 to the variable Car, assigns the number of people indicated in the number of people information to the variable N, and performs a judgment on the first vehicle (S131). When the selection unit 114 assigns the Car vehicle based on the departure floor and destination floor of the self-propelled device 3 and the allocation information 123, the selection unit 114 judges whether or not an unallowed person who has registered a first hall destination floor call will ride with the self-propelled device 3 in the cage 81 of the Car vehicle (S132). If there is no possibility that an unallowed person will ride with the self-propelled device 3 (NO in S132), the selection unit 114 judges whether or not N people can ride in the Car vehicle (S133).

[0182] If N persons can ride in the Car (YES in S133), the selection unit 114 selects the Car as a second candidate (S134: selection step) and proceeds to the process of step S135. If there is a possibility that an unacceptable person may ride with the self-propelled device 3 (YES in S132), or if NO in step S132 and N persons cannot ride in the Car (NO in S133), the selection unit 114 does not select the Car as a second candidate and proceeds to the process of step S135.

[0183] In step S135, the selection unit 114 increments the variable Car, and determines whether or not the value of the variable Car is equal to or less than the total number of elevators 8 (S136). If the value of the variable Car is equal to or less than the total number of elevators 8 (NO in S136), that is, if the determination has not been completed for all elevators, the process returns to step S132, and the processes of steps S131 to S136 are repeated until step S136 is YES. If the value of the variable Car is greater than the total number of elevators 8 (YES in S136), that is, if the determination has been completed for all elevators, the selection unit 114 determines whether or not a second candidate elevator exists (S137).

[0184] When the second candidate vehicle does not exist (NO in S137), the process returns to step S131. When the second candidate vehicle does not exist, it means that there is no vehicle to be assigned to the second hall destination floor call of the self-propelled device 3. In this case, the processes of steps S131 to S137 are repeated until step S137 becomes YES. When the second candidate vehicle exists (YES in S137), that is, when there is a vehicle to be assigned to the second hall destination floor call of the self-propelled device 3, the selection unit 114 selects the vehicle to be assigned to the second hall destination floor call as the second candidate vehicle. The selection unit 114 outputs information indicating the selected second candidate vehicle to the allocation unit 115.

[0185] The allocation unit 115 determines a vehicle to be allocated from the second candidate vehicles. Specifically, the allocation unit 115 determines an optimal vehicle from the second candidate vehicles as a vehicle to be allocated to the second hall destination floor call (S138: allocation step). When the allocation unit 115 determines the vehicle to be allocated, it transmits information indicating the destination floor and the allocated vehicle to the robot management control device 2 (S139).

[0186] In this manner, the self-propelled device 3 is assigned to the second hall destination floor call.

[0187] [After allocation] 16 again, a description will be given of the processing performed in the destination floor registration device 5 or the security gate 6 after an allocation to a first hall destination floor call is performed in the group management control device 1. Note that the following describes the processing after an error signal is transmitted from the group management control device 1 to the destination floor registration device 5 or the security gate 6 (after S65), after a car number is allocated in allocation process 1 (after S75), and after allocation process 2 (after S99).

[0188] When the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 receives data from the group management control device 1 (YES in S81), it determines whether or not a "passenger permission request signal" has been received from the group management control device 1 (S82). The process performed when the result in step S82 is YES has already been described, and therefore will not be described here.

[0189] If the information received from the group management control device 1 is not a "passenger permission request signal" (NO in S82), the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 determines whether the received information includes information indicating the destination floor and the assigned elevator (S89).

[0190] When information including information indicating the destination floor and the assigned elevator is received (YES in S89), the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 displays the received information indicating the destination floor and the assigned elevator for a predetermined period of time, for example, several seconds (S90). A case of YES in step S89 is when an assigned elevator for the first hall destination floor call has been determined in assignment process 1 or assignment process 2, and the assignment result has been transmitted from the group management control device 1. This allows the noted user to confirm his / her own destination floor and assigned elevator.

[0191] If the information received from the group management control device 1 does not include information indicating the destination floor and assigned elevator number (NO in S89), the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 displays an error screen indicating that user authentication has failed (S91).

[0192] After step S90 or step S91, the display unit 53 of the destination floor registration device 5 or the display unit 62 of the security gate 6 displays a default screen, and the process ends.

[0193] In this manner, the destination floor registration device 5 or the security gate 6 notifies the user of the allocation result or the authentication failure.

[0194] [Embodiment 2] Other embodiments of the present invention will be described below. For ease of explanation, the same reference numerals are given to members having the same functions as those described in the above embodiment, and the description thereof will not be repeated.

[0195] Fig. 20 is a block diagram showing the configuration of a landing destination floor registration system 100A according to embodiment 2. As shown in Fig. 20, the landing destination floor registration system 100A includes a group management control device 1A, a robot management control device 2, a self-propelled device 3, a destination floor registration device 5A, an elevator control device 7, and an elevator 8.

[0196] The group management control device 1A includes a control unit 11A and a storage unit 12A. The control unit 11A includes a reception unit 111A, a determination unit 112, an acquisition unit 113, a selection unit 114, an allocation unit 115, and an authentication unit 116. The storage unit 12A stores a device DB 121, allocation information 123, and a user DB 124. The user DB 124 is a database that stores information similar to the user DB 421 stored in the security server 4 of the hall / destination floor registration system 100 shown in FIG. 1.

[0197] In the elevator-hall / destination floor registration system 100A according to the second embodiment, the group management control device 1A performs the processing that was performed by the security server 4 in the elevator-hall / destination floor registration system 100 according to the first embodiment. For example, the group management control device 1A performs authentication of a user based on a user ID.

[0198] When the reading unit 51A of the destination floor registration device 5A acquires the user ID, it transmits the acquired user ID to the group management control device 1A. When the display unit 53 of the destination floor registration device 5 receives information indicating permitted floors from the group management control device 1A, it displays the permitted floors, and the input unit 52A accepts input of the floor by the user. The input unit 52A transmits the input information indicating the destination floor to the group management control device 1A.

[0199] When the reception unit 111A of the group management control device 1A receives the user ID, it outputs the user ID to the authentication unit 116. The authentication unit 116 refers to the user DB 124 and authenticates the user. If the authentication of the user is successful, the authentication unit 116 obtains information indicating the permitted floor of the user and transmits it to the destination floor registration device 5A. The authentication unit 116 also identifies the departure floor of the user based on the device ID. The authentication unit 116 outputs information indicating that the authentication of the user was successful and information indicating the departure floor of the user to the determination unit 112.

[0200] The determination unit 112 acquires information indicating that the authentication of the user has been successful and information indicating the departure floor of the user from the authentication unit 116, and receives information indicating the destination floor of the user from the destination floor registration device 5. The determination unit 112 makes a determination based on this information. The processing after the determination by the determination unit 112 is similar to the method performed in the hall destination floor registration system 100 according to the first embodiment, and therefore a description thereof will be omitted.

[0201] [Embodiment 3] Fig. 21 is a block diagram showing the configuration of a landing destination floor registration system 100B according to the third embodiment. The landing destination floor registration system 100B stores permission / denial information of a user in advance, and selects a first candidate elevator and a second candidate elevator based on the permission / denial information. The landing destination floor registration system 100B will be described below with reference to Fig. 21.

[0202] 21, the landing-destination floor registration system 100B differs from the landing-destination floor registration system 100 according to the first embodiment in that it includes a group management control device 1B having a control unit 11B and a storage unit 12B. The control unit 11B differs from the control unit 11 according to the first embodiment in that it includes an acquisition unit 113B instead of the acquisition unit 113.

[0203] The storage unit 12B stores a user DB 124 in addition to the device DB 121, the gate DB 122, and the allocation information 123. Fig. 22 is a diagram showing an example of the user DB 124 according to the third embodiment. As shown in Fig. 22, in the user DB 124, in addition to the information in the user DB 421, the user identification information and permission information for each type of the self-propelled device 3 of the user are associated with each user.

[0204] When a determination result indicating that the noted user may ride with the noted self-propelled device in any one of the vehicles is acquired from the determination unit 112, the acquisition unit 113B acquires permission / denial information from the storage unit 12B. The acquisition unit 113B outputs the acquired permission / denial information to the selection unit 114.

[0205] The processing after the selection unit 114 acquires the permission / denial information, and the processing when there is no possibility that the noted user will ride together with the noted self-propelled device in all the vehicles, are similar to the method performed in the boarding hall destination floor registration system 100 according to the first embodiment, and therefore will not be described.

[0206] According to the above configuration, when permission information is registered in advance, allocation is performed based on the registered permission information. Therefore, when the noted user registers a first hall destination floor call, it is possible to reduce the effort of re-inquiring about the permission information of the noted user.

[0207] [Embodiment 4] Fig. 23 is a block diagram showing a configuration of a hall / destination floor registration system 100C according to embodiment 4. The hall / destination floor registration system 100C will be described below with reference to Fig. 23.

[0208] The landing-destination-floor registration system 100C prestores permission / denial information of users, and selects the first candidate elevator and the second candidate elevator based on the permission / denial information. In addition, the landing-destination-floor registration system 100C queries the user about permission / denial information as necessary.

[0209] As shown in Fig. 23, the landing-destination floor registration system 100C differs from the landing-destination floor registration system 100 according to the first embodiment in that it includes a group management control device 1C. The group management control device 1C includes a control unit 11C and a storage unit 12C. The control unit 11C differs from the control unit 11 according to the first embodiment in that it includes an acquisition unit 113C. Similarly to the storage unit 12B, the storage unit 12C stores a user DB 124.

[0210] The acquisition unit 113C acquires from the determination unit 112 a determination result as to whether or not the noted user is likely to ride together with the noted self-propelled device in the car 81 of any car. The acquisition unit 113C refers to the memory unit 12C when there is a possibility that the noted user will ride together with the noted self-propelled device in the car 81 of the car. The acquisition unit 113 determines whether or not permission information of the noted user and the noted self-propelled device is registered in the memory unit 12C.

[0211] When the storage unit 12C has registered the permission information of the noted user and the noted self-propelled device, the acquisition unit 113C acquires the permission information. On the other hand, when the storage unit 12C has not registered the permission information of the noted user and the noted self-propelled device, the acquisition unit 113C inquires the noted user about the permission information. The method of inquiring about the permission information is the same as the method described in the first embodiment, and therefore the description here is omitted.

[0212] According to the above configuration, when permission information is registered in advance, selection and allocation are performed based on the registered permission information. When permission information is not registered, permission information is queried, and selection and allocation are performed based on the result.

[0213] The case where the permission information of the noted user with respect to the noted self-propelled device is not registered in the storage unit 12C may be a case where the permission information corresponding to the type of the noted self-propelled device is not included in the permission information pre-stored in the storage unit 12C. For example, when the types of self-propelled devices 3 that may ride with the user include delivery, cleaning, and security, the permission information indicating whether the user is allowed to ride with each of these self-propelled devices 3 is registered in the storage unit 12C.

[0214] Here, when the self-propelled device that may ride with the noted user is a security robot, the acquisition unit can identify the permission information of the noted user from the storage unit.

[0215] On the other hand, when the self-propelled device that may ride with the noted user is a medical robot or the like, the permission / denial information is not stored in the storage unit 12C. In such a case, the acquisition unit 113C inquires of the noted user, and therefore, the permission / denial information can be acquired regardless of whether the permission / denial information is registered in the storage unit 12C.

[0216] In addition, the reason why the permission information of the noted user and the noted self-propelled device is not registered in the storage unit 12C may be due to other reasons. For example, the reason why the permission information of the noted user and the noted self-propelled device is not registered may be because the permission information is not registered in advance by the noted user.

[0217] [Additional Notes] The processes executed by each device described in each of the above embodiments may be distributed among multiple computers, i.e., each process described using the flowcharts in each of the above embodiments may be executed by one or multiple computers.

[0218] [Software implementation example] The functions of the landing destination floor registration system 100, 100A to 100C (hereinafter referred to as the "system") can be realized by a program for causing a computer to function as the system, and a program for causing a computer to function as each control block of the system (particularly each part included in the control unit 11, 11A to 11C).

[0219] 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., a memory) as hardware for executing the program. The control device and storage device execute the program to realize each function described in each of the above embodiments.

[0220] The program may be non-transitory and may be recorded in one or more computer-readable recording media. The recording media may or may not be included in the device. In the latter case, the program may be provided to the device via any wired or wireless transmission medium.

[0221] In addition, some or all of the functions of each of the control blocks can be realized by a logic circuit. For example, an integrated circuit in which a logic circuit that functions as each of the control blocks is formed is also included in the scope of the present invention. In addition, the functions of each of the control blocks can be realized by, for example, a quantum computer.

[0222] Furthermore, each process described in each of the above embodiments may be executed by AI (Artificial Intelligence). In this case, the AI ​​may be operated by the control device or may be operated by another device (for example, an edge computer or a cloud server).

[0223] The present invention is not limited to the above-described embodiments, 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. 〔summary〕 A landing destination floor registration system according to a first aspect of the present disclosure is an elevator landing destination floor registration system for an elevator equipped with a plurality of elevators and capable of using a plurality of types of self-propelled devices, comprising: a reception unit that receives a first landing destination floor call by a user and a second landing destination floor call by the self-propelled device; a determination unit that determines whether or not a noted user who has newly registered the first landing destination floor call is likely to ride together with a noted self-propelled device in which the second landing destination floor call has been registered, in the cage of the elevator; and a determination unit that, when the noted user is likely to ride together with the noted self-propelled device in the cage of the elevator, determines whether or not the noted user has a destination floor of interest determined according to the type of the noted self-propelled device. the selection unit is configured to select, based on the permission information, from the plurality of machines, a first candidate machine that can be assigned to the first landing destination floor call and a second candidate machine that can be assigned to the second landing destination floor call; and an allocation unit that determines, from the first candidate machines, a machine to be assigned to the first landing destination floor call and determines, from the second candidate machines, a machine to be assigned to the second landing destination floor call, and when the permission information indicates that riding with the noted self-propelled device is not permitted, the selection unit excludes the machine in which the noted user and the noted self-propelled device may ride together from the first candidate machines.

[0224] In the boarding hall destination floor registration system according to aspect 2 of the present disclosure, in aspect 2, the acquisition unit may inquire of the noted user about the permission / denial information when there is a possibility that the noted user will be riding together with the noted self-propelled device in the cage of the elevator.

[0225] In the elevator destination floor registration system according to aspect 3 of the present disclosure, in the above-mentioned aspect 1 or 2, the determination unit determines whether or not there is a possibility that a user who has already registered the first elevator destination floor call will ride in the cage of the elevator with the self-propelled device that has newly registered the second elevator destination floor call, and the acquisition unit, when there is a possibility that the user will ride in the cage of the elevator with the self-propelled device, acquires the permission / denial information indicating whether or not the user is permitted to ride in the self-propelled device, and when the permission / denial information indicates that riding in the self-propelled device is not permitted, the selection unit may exclude the elevator in which the user and the self-propelled device are likely to ride in from the second candidate elevators.

[0226] The hall destination floor registration system according to aspect 4 of the present disclosure, in any one of aspects 1 to 3, may include a memory unit that stores, for each user, identification information of the user and the permission / denial information for each type of self-propelled device.

[0227] In the elevator destination floor registration system according to aspect 5 of the present disclosure, in aspect 4, the acquisition unit may refer to the memory unit when there is a possibility that the noted user will be riding in the cage of the elevator together with the noted self-propelled device, and if the permission / denial information of the noted user to the noted self-propelled device is registered in the memory unit, acquire the permission / denial information, and if the permission / denial information of the noted user to the noted self-propelled device is not registered in the memory unit, inquire of the noted user about the permission / denial information.

[0228] In the elevator-destination floor registration system according to a sixth aspect of the present disclosure, in any one of the first to fifth aspects, the type of the self-propelled device may be a type of function that the self-propelled device has.

[0229] A control method for a landing destination floor registration system according to a seventh aspect of the present disclosure is a control method for an elevator landing destination floor registration system for an elevator capable of using a plurality of types of self-propelled devices, executed by one or more computers, the elevator being equipped with a plurality of elevators, the control method including a reception step of receiving a first landing destination floor call by a user and a second landing destination floor call by the self-propelled device, a determination step of determining whether or not a noted user who has newly registered the first landing destination floor call is likely to ride together with a noted self-propelled device in which the second landing destination floor call has been registered, in the cage of the elevator, and a determination step of determining whether or not the noted user who has newly registered the first landing destination floor call is likely to ride together with the noted self-propelled device in the cage of the elevator, when the noted user is likely to ride together with the noted self-propelled device in the cage of the elevator, the selection step of selecting, based on the permission information, from the plurality of machines, a first candidate machine that can be assigned to the first landing destination floor call and a second candidate machine that can be assigned to the second landing destination floor call; and an allocation step of determining, from the first candidate machines, a machine to be assigned to the first landing destination floor call, and determining, from the second candidate machines, a machine to be assigned to the second landing destination floor call. In the selection step, if the permission information indicates that riding with the target self-propelled device is not permitted, the machine in which the target user and the target self-propelled device may ride together is excluded from the first candidate machines. [Explanation of symbols]

[0230] 3 Self-propelled device 8. Elevator 100, 100A, 100B, 100C Boarding area destination floor registration system 111, 111A Reception 112 Judgment section 113, 113B, 113C Acquisition Department 114 Selection Department 115 Allocation Section 12, 12A, 12B, 12C storage section 81 Basket S63, S69 Reception Step S72, S106 Judgment step S66 Acquisition Step S73, S107, S108, S134 Selection steps S74, S121 Allocation steps

Claims

1. An elevator hall destination floor registration system that is equipped with a plurality of elevators and is capable of using a plurality of types of self-propelled devices, A reception unit that receives a first hall destination floor call from a user and a second hall destination floor call from the self-propelled device; a determination unit that determines whether or not a noted user who has newly registered the first hall destination floor call is likely to ride together with a noted self-propelled device in which the second hall destination floor call has been registered, in the cage of the elevator; an acquisition unit that acquires permission / denial information indicating whether the noted user is permitted to ride together with the noted self-propelled device in the car of the vehicle when the noted user is likely to ride together with the noted self-propelled device in the car of the vehicle, the permission / denial information being determined according to the type of the noted self-propelled device; a selection unit that selects, based on the permission / denial information, from the plurality of elevators, a first candidate elevator that can be assigned to the first elevator-destination floor call and a second candidate elevator that can be assigned to the second elevator-destination floor call; an allocation unit that determines a car to be allocated to the first hall destination floor call from the first candidate car, and determines a car to be allocated to the second hall destination floor call from the second candidate car; Equipped with The selection unit is When the permission information indicates that the ride with the target self-propelled device is not permitted, the vehicle number in which the target user and the target self-propelled device may ride together is excluded from the first candidate vehicle number; The acquisition unit, when there is a possibility that the noted user will ride together with the noted self-propelled device in the cage of the elevator, queries the noted user about the permission information for the type of the noted self-propelled device that is determined to have the possibility of riding together with the noted user, in a boarding hall destination floor registration system.

2. An elevator hall destination floor registration system that is equipped with a plurality of elevators and is capable of using a plurality of types of self-propelled devices, A reception unit that receives a first hall destination floor call from a user and a second hall destination floor call from the self-propelled device; a determination unit that determines whether or not a noted user who has newly registered the first hall destination floor call is likely to ride together with a noted self-propelled device in which the second hall destination floor call has been registered, in the cage of the elevator; an acquisition unit that acquires permission / denial information indicating whether or not the noted user is permitted to ride together with the noted self-propelled device in the car of the vehicle, the permission / denial information being determined according to the type of the noted self-propelled device, only when the determination unit determines that the noted user is likely to ride together with the noted self-propelled device in the car of the vehicle; a selection unit that selects, from the plurality of elevators, a first candidate elevator that can be assigned to the first elevator-hall destination floor call and a second candidate elevator that can be assigned to the second elevator-hall destination floor call, based on the acquired permission / denial information; an allocation unit that determines a car to be allocated to the first hall destination floor call from the first candidate car, and determines a car to be allocated to the second hall destination floor call from the second candidate car; Equipped with The selection unit is In a case where the permission information indicates that riding together with the noted self-propelled device is not permitted, the vehicle number in which the noted user and the noted self-propelled device may ride together is excluded from the first candidate vehicle numbers, the boarding hall destination floor registration system.

3. An elevator hall destination floor registration system that is equipped with a plurality of elevators and is capable of using a plurality of types of self-propelled devices, A reception unit that receives a first hall destination floor call from a user and a second hall destination floor call from the self-propelled device; a determination unit that determines whether or not a noted user who has newly registered the first hall destination floor call is likely to ride together with a noted self-propelled device in which the second hall destination floor call has been registered, in the cage of the elevator; an acquisition unit that acquires permission / denial information indicating whether the noted user is permitted to ride together with the noted self-propelled device in the car of the vehicle when the noted user is likely to ride together with the noted self-propelled device in the car of the vehicle, the permission / denial information being determined according to the type of the noted self-propelled device; a selection unit that selects, based on the permission / denial information, from the plurality of elevators, a first candidate elevator that can be assigned to the first elevator-destination floor call and a second candidate elevator that can be assigned to the second elevator-destination floor call; an allocation unit that determines a car to be allocated to the first hall destination floor call from the first candidate car, and determines a car to be allocated to the second hall destination floor call from the second candidate car; Equipped with The selection unit is When the permission information indicates that the ride with the target self-propelled device is not permitted, the vehicle number in which the target user and the target self-propelled device may ride together is excluded from the first candidate vehicle number; a storage unit that stores, for each user, identification information of the user and the permission / denial information for each type of the self-propelled device of the user in association with each user; The acquisition unit refers to the storage unit when there is a possibility that the noted user will ride together with the noted self-propelled device in the car of the vehicle, When the permission information of the noted user and the noted self-propelled device is registered in the storage unit, the permission information is acquired. the storage unit is configured to inquire about the permission information of the noted user with respect to the noted self-propelled device, if the permission information of the noted user with respect to the noted self-propelled device is not registered therein;

4. The boarding hall destination floor registration system according to claim 2 or 3, wherein the acquisition unit inquires of the permission information from the noted user when there is a possibility that the noted user will ride together with the noted self-propelled device in the cage of the elevator.

5. The determination unit is determining whether or not there is a possibility that a user who has already registered the first hall destination floor call will ride together with the self-propelled device in which the second hall destination floor call has been newly registered, in the cage of the elevator; The acquisition unit is When there is a possibility that the user will ride together with the self-propelled device in the cage of the vehicle, the permission / denial information indicating whether or not the user is permitted to ride together with the self-propelled device is acquired; The selection unit is The platform destination floor registration system according to any one of claims 1 to 3, wherein, when the permission / denial information indicates that riding together with the self-propelled device is not permitted, the vehicle number in which the user and the self-propelled device may ride together is excluded from the second candidate vehicle numbers.

6. 3. The hall / destination floor registration system according to claim 1, further comprising a storage unit configured to store, for each user, identification information of the user and the permission / denial information for each type of the self-propelled device of the user in association with each user.

7. The acquisition unit refers to the storage unit when there is a possibility that the noted user will ride together with the noted self-propelled device in the car of the vehicle, When the permission information of the noted user and the noted self-propelled device is registered in the storage unit, the permission information is acquired.

7. The hall / destination floor registration system according to claim 6, wherein, when the permission / denial information of the noted user with respect to the noted self-propelled device is not registered in the storage unit, the permission / denial information is queried from the noted user.

8. The hall / destination floor registration system according to claim 1 , wherein the type of the self-propelled device is a type of function that the self-propelled device has.

9. A control method for an elevator landing destination floor registration system capable of using a plurality of types of self-propelled devices, executed by one or a plurality of computers, comprising: The elevator includes a plurality of elevator cars, a reception step of receiving a first hall destination floor call by a user and a second hall destination floor call by the self-propelled device; a determination step of determining whether or not the noted user who has newly registered the first hall destination floor call is likely to ride in the car of the elevator together with the noted self-propelled device in which the second hall destination floor call has been registered; an acquisition step of acquiring permission / denial information indicating whether the noted user is permitted to ride together with the noted self-propelled device in the car of the vehicle, the permission / denial information being determined according to the type of the noted self-propelled device; a selection step of selecting, from the plurality of elevators, a first candidate elevator that can be assigned to the first elevator-destination floor call and a second candidate elevator that can be assigned to the second elevator-destination floor call, based on the permission / denial information; an allocation step of determining a car to be allocated to the first hall destination floor call from the first candidate car, and determining a car to be allocated to the second hall destination floor call from the second candidate car; Including, In the selection step, When the permission information indicates that the ride with the target self-propelled device is not permitted, the vehicle number in which the target user and the target self-propelled device may ride together is excluded from the first candidate vehicle number; A control method for a hall destination floor registration system, in which, in the acquisition step, if there is a possibility that the noted user will ride together with the noted self-propelled device in the cage of the elevator, the noted user is inquired about the permission information for the type of the noted self-propelled device that is determined to have the possibility of riding together with the noted user.

10. A control method for an elevator landing destination floor registration system capable of using a plurality of types of self-propelled devices, executed by one or a plurality of computers, comprising: The elevator includes a plurality of elevator cars, a reception step of receiving a first hall destination floor call by a user and a second hall destination floor call by the self-propelled device; a determination step of determining whether or not the noted user who has newly registered the first hall destination floor call is likely to ride in the car of the elevator together with the noted self-propelled device in which the second hall destination floor call has been registered; an acquisition step of acquiring permission / denial information indicating whether the noted user is permitted to ride together with the noted self-propelled device in the car of the vehicle, the permission / denial information being determined according to the type of the noted self-propelled device, only when the determination step determines that the noted user is likely to ride together with the noted self-propelled device in the car of the vehicle; a selection step of selecting, from the plurality of elevators, a first candidate elevator that can be assigned to the first elevator-destination floor call and a second candidate elevator that can be assigned to the second elevator-destination floor call, based on the acquired permission / denial information; an allocation step of determining a car to be allocated to the first hall destination floor call from the first candidate car, and determining a car to be allocated to the second hall destination floor call from the second candidate car; Including, In the selection step, A control method for a hall destination floor registration system, in which, when the permission information indicates that riding together with the target self-propelled device is not permitted, the vehicle in which the target user and the target self-propelled device may ride together is excluded from the first candidate vehicle.

11. A control method for an elevator landing destination floor registration system capable of using a plurality of types of self-propelled devices, executed by one or a plurality of computers, comprising: The elevator includes a plurality of elevator cars, a reception step of receiving a first hall destination floor call by a user and a second hall destination floor call by the self-propelled device; a determination step of determining whether or not the noted user who has newly registered the first hall destination floor call is likely to ride in the car of the elevator together with the noted self-propelled device in which the second hall destination floor call has been registered; an acquisition step of acquiring permission / denial information indicating whether the noted user is permitted to ride together with the noted self-propelled device in the car of the vehicle, the permission / denial information being determined according to the type of the noted self-propelled device; a selection step of selecting, from the plurality of elevators, a first candidate elevator that can be assigned to the first elevator-destination floor call and a second candidate elevator that can be assigned to the second elevator-destination floor call, based on the permission / denial information; an allocation step of determining a car to be allocated to the first hall destination floor call from the first candidate car, and determining a car to be allocated to the second hall destination floor call from the second candidate car; Including, In the selection step, When the permission information indicates that the ride with the target self-propelled device is not permitted, the vehicle number in which the target user and the target self-propelled device may ride together is excluded from the first candidate vehicle number; In the acquisition step, when there is a possibility that the noted user will ride together with the noted self-propelled device in the car of the vehicle, a storage unit is referenced that stores the identification information of the user and the permission / denial information for each type of the self-propelled device for the user in association with each user; When the permission information of the noted user and the noted self-propelled device is registered in the storage unit, the permission information is acquired; The control method for a hall / destination floor registration system further comprises: inquiring of the permission information of the noted user with respect to the noted self-propelled device when the permission information of the noted user with respect to the noted self-propelled device is not registered in the storage unit.

Citation Information

Patent Citations

  • Elevator system, elevator group management control device and elevator number allocation method

    JP2020128279A

  • Elevator control device and moving body management device

    JP2022128045A

  • Elevator control device and autonomous moving body control device

    WO2018066054A1

  • Movement assist system

    WO2020230305A1

Cited By

  • Elevator control device and control method

    JP7882380B1