Landing destination floor registration system and method for controlling the same

Abstract

To effectively reduce the psychological load of a user of an elevator.SOLUTION: A landing destination floor registration system (100) comprises: a reception unit (111) that receives registration of a landing destination floor call; an allocation unit (112) that allocates an elevator machine in response to the landing destination floor call; and a presentation unit (113) that, when a machine of interest allocated in response to a second landing destination floor call of a mobile device (3) is also allocated to a first landing destination floor call of a user, and the mobile device and the user encounter each other, causes a presentation device (23) to present schedule information (122) indicating boarding schedule of the mobile device at one of a departure floor and a destination floor of the user.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a landing-destination floor registration system and a control method for a landing-destination floor registration system in which a user and a robot (mobile device) can use the same elevator. [Background technology]

[0002] Patent Document 1 discloses an elevator control method configured to detect when a robot gets into an elevator and indicate on a user interface of the elevator whether or not the elevator is being used by the robot. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-66605 Summary of the Invention [Problem to be solved by the invention]

[0004] Users who use the same elevator as a robot may experience psychological stress, for example, because they need to take into consideration securing space for the robot and avoiding collisions with the robot. For example, if a user who is planning to board an elevator at a floor where a robot will be getting off is not informed that the robot will be getting off, the user may experience psychological stress. Also, if a user who is waiting for the elevator to arrive on the same floor as a robot is not informed that the robot will be getting on the same elevator, the user may experience psychological stress.

[0005] The elevator control system disclosed in Patent Document 1 makes a user who is about to use an elevator confirm whether a robot is on board the elevator or whether the elevator is set as an elevator exclusively for robots. However, the elevator control method disclosed in Patent Document 1 leaves room for improvement as a method for reducing the psychological burden on users who use the same elevator as a robot. [Means for solving the problem]

[0006] In order to solve the above problems, a landing destination floor registration system according to one embodiment of the present invention includes a reception unit that receives registration of a first landing destination floor call by a user and registration of a second landing destination floor call by a mobile device or an operator of the mobile device; an assignment unit that assigns elevator numbers to the first landing destination floor call and the second landing destination floor call; and a presentation unit that causes a presentation device to present schedule information indicating the boarding and alighting schedule of the mobile device at at least one of a departure floor, which is a floor where the user boards the car of the target elevator, and a destination floor, which is a floor where the user alights from the car of the target elevator, when the target elevator is assigned to the first landing destination floor call during a period from when a target elevator is assigned to the second landing destination floor call to when the mobile device boards the target elevator and arrives at a destination floor of the mobile device, and when the mobile device and the user encounter each other when boarding and alighting, the mobile device using the same elevator car.

[0007] Furthermore, a control method of a landing destination floor registration system according to one embodiment of the present invention includes a receiving step of accepting registration of a first landing destination floor call by a user and registration of a second landing destination floor call by a mobile device or an operator of the mobile device, an assignment step of assigning elevator numbers to the first landing destination floor call and the second landing destination floor call, and a presentation step of causing a presentation device to present schedule information indicating the boarding and alighting schedule of the mobile device at at least one of a departure floor, which is a floor where the user boards the car of the target elevator, and a destination floor, which is a floor where the user alights from the car of the target elevator, when the target elevator is assigned to the first landing destination floor call during a period from when a target elevator is assigned to the second landing destination floor call to when the mobile device boards the target elevator and arrives at a destination floor of the mobile device, and when the mobile device and the user encounter each other when boarding and alighting, the mobile device using the same elevator car.

[0008] 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

[0009] According to one aspect of the present invention, the psychological stress on users who use elevators can be effectively reduced. [Brief description of the drawings]

[0010] [Figure 1] 1 is a block diagram showing a configuration of a hall / destination floor registration system according to a first embodiment of the present invention. [Diagram 2] FIG. 11 is a diagram illustrating an example of an allocation information DB. [Diagram 3] 1 is a schematic diagram for explaining an example of a situation in which a user and a mobile device encounter each other; [Figure 4] 13 is an example of a screen to be presented by a presentation device. [Diagram 5] 13 is an example of a screen to be presented by a presentation device. [Figure 6] 13 is an example of a screen to be presented by a presentation device. [Figure 7] 13 is an example of a screen to be presented by a presentation device. [Figure 8] 13 is an example of a screen to be presented by a presentation device. [Figure 9] 13 is an example of a screen to be presented by a presentation device. [Figure 10] 13 is an example of a screen to be presented by a presentation device. [Figure 11] FIG. 1 is a schematic diagram for explaining an example of a situation in which a user and a mobile device do not encounter each other. [Figure 12] 2 is a sequence diagram showing an example of a flow of processing (control method) performed by the hall destination floor registration system. FIG. [Figure 13] 2 is a sequence diagram showing an example of a flow of processing (control method) performed by the hall destination floor registration system. FIG. [Figure 14] FIG. 11 is a block diagram showing a configuration of a hall / destination floor registration system according to a second embodiment. [Figure 15] FIG. 11 is a diagram illustrating an example of an allocation information DB. [Figure 16] 10 is a flowchart for explaining an example of a flow of processes performed by a destination floor registration device according to the second embodiment. [Figure 17] 10 is a flowchart for explaining an example of a flow of a process performed by the elevator-hall / destination floor registration system according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] [Embodiment 1] <Platform 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 the first embodiment of the present invention. As shown in Fig. 1, the hall / destination floor registration system 100 includes a group management control device 1, a destination floor registration device 2, a movement device 3, an elevator control device 4, and an elevator 5.

[0012] The destination floor registration device 2, the movement device 3, the elevator control device 4, and the elevator 5 included in the hall destination floor registration system 100 may each be one or more. In this embodiment, a configuration in which a plurality of destination floor registration devices 2, a plurality of movement devices 3, a plurality of elevator control devices 4, and a plurality of elevators 5 are provided will be described as an example.

[0013] The group management control device 1 assigns an optimal elevator to a hall / destination floor call indicating a departure floor and a destination floor received from a user, a moving device 3, or an operator of the moving device 3. The elevator control device 4 operates the car 51 of the elevator 5 based on the assignment result of the group management control device 1.

[0014] Hereinafter, a hall destination floor call by a user is referred to as a "first hall destination floor call," and a hall destination floor call received from the moving device 3 or the operator of the moving device 3 is referred to as a "second hall destination floor call." In addition, the elevator 5 number assigned to the second hall destination floor call is referred to as a "focused elevator."

[0015] In the landing destination floor registration system 100, a situation may occur in which a target elevator is assigned to a first landing destination floor call during a period from when a target elevator is assigned to a second landing destination floor call until the moving device 3 boards the target elevator and arrives at the destination floor of the moving device 3. When such a situation occurs, the landing destination floor registration system 100 causes the presentation device 23 of the destination floor registration device 2 to present schedule information indicating the boarding and alighting schedule of the moving device 3 at the departure floor of the user.

[0016] As a result, the hall destination floor registration system 100 can register the first hall destination floor call and allow the user to whom the target vehicle is assigned to know the boarding and disembarking schedule of the transportation device 3 using the target vehicle.

[0017] In a conventional system that performs allocation based on a platform destination floor call, even if a user is assigned to the same car as a mobile device, if the user does not encounter a situation in which the user is present when boarding the car of the car, the user will not be psychologically stressed. On the other hand, in this system, if a situation occurs in which the user is present in the car of a mobile device, the user may be psychologically stressed. Examples of such situations include a situation in which the mobile device gets off the car of the car that the user is planning to board at the user's departure floor, a situation in which the mobile device boards the car of the car that the user is planning to board at the user's departure floor, and a situation in which the mobile device boards the car of the car that the user is planning to board.

[0018] In the invention described in Patent Document 1, at the time when a user registers a platform destination floor call, the user cannot know the state of the mobile device when the user boards the car in the future. For example, if a user boards from the third floor and the mobile device is in a car on the first floor, at the time when the user registers the platform destination floor call, it is not known whether the mobile device is also in a state of being in the car on the third floor.

[0019] In contrast, the landing destination floor registration system 100 according to the present embodiment includes a reception unit 111 that receives a first landing destination floor call and a second landing destination floor call, an allocation unit 112 that allocates a car to the received landing destination floor call, and a presentation unit 113 that causes the presentation device 23 to present information. The presentation unit 113 causes the presentation device 23 to present the boarding and alighting schedule of the mobile device 3 at either the departure floor or the destination floor of the user. The presentation unit 113 performs presentation control when a target car is assigned to a first landing destination floor call during a period from when a target car is assigned to a second landing destination floor call to when the mobile device 3 boards the target car and arrives at the destination floor of the mobile device 3, and when the mobile device and the user that use the cage of the same car encounter each other when the user boards and disembarks.

[0020] According to the above configuration, the hall destination floor registration system 100 can inform the user of schedule information 122 regarding the boarding and disembarking plans of the transportation device 3 using the vehicle assigned to the first hall destination floor call at the time the user registers the first hall destination floor call.

[0021] In this way, the hall-destination floor registration system 100 can effectively reduce the psychological burden on users. In addition, since it is possible to inform users in advance that they need to take care to secure space for the moving device 3 and to avoid collisions with the moving device, it also has the effect of enabling the moving device 3 to smoothly board and disembark.

[0022] <Destination floor registration device 2> The devices and processes of the elevator-hall / destination-floor registration system 100 will be described in detail below.

[0023] The destination floor registration device 2 is a device used by a user to register a destination floor call at the first landing. The destination floor registration device 2 may be provided at the landing of each floor. Also, multiple destination floor registration devices 2 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 2.

[0024] 1, the destination floor registration device 2 includes an input unit 21, a control unit 22, and a presentation device 23. The input unit 21 is, for example, a device such as a touch panel, and receives an operation for registering a first-hall destination floor call by a user, for example, an operation for inputting a destination floor. The input unit 21 outputs a signal indicating the received operation to the control unit 22. The presentation device 23 may be a display device such as a display provided in the destination floor registration device 2 used by the user to make the first-hall destination floor call, or may be a touch panel that also functions as the input unit 21.

[0025] When an input operation is performed on the input unit 21, the control unit 22 identifies information related to the first hall destination floor call based on the input operation, and transmits the information to the group management control device 1. For example, the control unit 22 transmits information indicating the destination floor input by the user to the group management control device 1.

[0026] Each destination floor registration device 2 is assigned with identification information for identifying each destination floor registration device 2. The control unit 22 transmits the identification information of the destination floor registration device 2 to the group management control device 1 in addition to the information indicating the destination floor.

[0027] The control unit 22 transmits the identification information of the destination floor registration device 2 in addition to the information indicating the destination floor, so that the group management control device 1 can identify the destination floor registration device 2 on which the operation for calling the first hall destination floor has been performed based on the identification information. Also, the departure floor of the user is identified based on the floor on which the destination floor registration device 2 is installed.

[0028] When the destination floor registration device 2 is a terminal device of the user, the control unit 22 also transmits to the group management control device 1 information indicating the departure floor.

[0029] Furthermore, when the control unit 22 receives information indicating the allocation result for the first hall destination floor call from the group management control device 1, the control unit 22 causes the presentation device 23 to present the information. When the information received from the group management control device 1 includes schedule information 122, the presentation unit 113 causes the presentation device 23 to present the schedule information 122 in addition to the information indicating the allocation result.

[0030] When the presentation device 23 is a display device such as a display, the control unit 22 causes the display device to display the information indicating the allocation result and the schedule information.

[0031] The destination floor registration device 2 may identify the user and specify the departure floor and destination floor according to the user. The user may be identified by, for example, reading a card with identification information for each user, image authentication, or other methods. With this configuration, the destination floor of the user is specified without the user having to perform an operation to input the destination floor.

[0032] <Mobile Device 3> The moving device 3 is an information processing device that can move between floors by using an elevator 5.

[0033] The mobile device 3 may be, for example, a device capable of autonomous travel, such as a robot or a drone. The mobile device 3 may be, for example, a security, cleaning, or delivery robot, and may be a device that utilizes an elevator 5 to perform a given task.

[0034] When the moving device 3 uses the elevator 5, the moving device 3 transmits a second hall destination floor call including the departure floor, the destination floor, and identification information for identifying the moving device 3 to the group management control device 1. As a result, the reception of the second hall destination floor call is registered in the group management control device 1, and a target elevator is assigned to the second hall destination floor call.

[0035] When the moving device 3 receives information indicating the allocation result from the group management control device 1, it waits for the car 51 of the assigned elevator 5 (the target car) at the landing of the departure floor. When the car 51 of the target car arrives, the moving device 3 gets on the car 51 and gets off the car 51 at the destination floor.

[0036] The moving device 3 may transmit a signal indicating that it has boarded the car 51 of the elevator of interest and that it has disembarked from the car 51 to the group management control device 1. In this case, the group management control device 1 can know that the moving device 3 is using the elevator 5 as scheduled.

[0037] The mobility device 3 may be a device capable of carrying a person and traveling, such as an electric wheelchair or a Segway, or may be a device that moves according to the operation of a rider or an operator, which may be another person. When the mobility device 3 is a device that moves based on the operation of an operator, it may be equipped with a device such as a display that can present the allocation result to the operator.

[0038] <Elevator control device 4 and elevator 5> The elevator control device 4 receives information about the hall / destination floor call for which registration has been completed from the group management control device 1. The information about the hall / destination floor call for which registration has been completed includes information indicating the number of the assigned elevator 5 and information indicating the departure floor and the destination floor. The elevator control device 4 controls the operation of the elevator 5 based on this information. The elevator 5 moves the car 51 between floors and opens and closes the doors under the control of the elevator control device 4.

[0039] The elevator control device 4 may control the operation of one elevator 5, or may control the operation of a plurality of elevators 5.

[0040] <Group management control device 1> The group management control device 1 receives hall destination floor calls, assigns elevators based on the received hall destination floor calls, and based on the assignment results, instructs the elevator control device 4 to control the movement of the elevator 5. The group management control device 1 also acquires the operating status of the elevator 5, and manages the registered hall destination floor calls based on the operating status.

[0041] In addition, the group management control device 1 determines the information to be presented by the presentation device 23 of the destination floor registration device 2 based on the allocation results for the first landing destination floor call and the second landing destination floor call received from the destination floor registration device 2, and transmits the determined information to the destination floor registration device 2.

[0042] For example, the group management control device 1 performs allocation to a first hall destination floor call, which is a hall destination floor call from a user. When the elevator assigned to the first hall destination floor call is also used by a moving device 3, the group management control device 1 determines information on the schedule of getting on and off the elevator 5 by the moving device 3 as information to be presented by the presentation device 23.

[0043] As shown in FIG. 1, the group management control device 1 includes a control unit 11, a storage unit 12, and an input / output interface 13.

[0044] The storage unit 12 stores various information used in the group management control device 1. As shown in Fig. 1, the storage unit 12 stores an allocation information DB (database) 121. The allocation information DB 121 stores information related to hall / destination floor calls that have been registered.

[0045] FIG. 2 is a diagram showing an example of the allocation information DB121. As shown in FIG. 2, the allocation information DB121 stores information indicating an assigned elevator, a boarding type, a departure floor, and a destination floor as information on a hall destination floor call for which registration has been completed. The boarding type is information indicating whether a person using the elevator 5 is a user who has registered a first hall destination floor call or a moving device 3 that has registered a second hall destination floor call. The boarding type may further include information indicating the type of the moving device 3. Among the information stored in the allocation information DB121, information on a hall destination floor call for which the boarding type is "moving device" is referred to as schedule information 122. FIG. 2 shows an example in which two schedule information 122 are included.

[0046] The memory unit 12 may also store information indicating the status of each elevator 5, for example, information indicating the floor on which the car 51 of each elevator is located and the current direction of movement.

[0047] The input / output interface 13 is a communication module for transmitting and receiving information between the group management control device 1 and each device included in the elevator-hall / destination floor registration system 100.

[0048] 1, the control unit 11 includes a reception unit 111, an allocation unit 112, and a presentation unit 113. The control unit 11 executes each process performed in the group management control device 1. Each processing unit included in the control unit 11 will be described in detail below.

[0049] (Reception Department 111) The reception unit 111 receives registration of a first hall destination floor call by a user, and registration of a second hall destination floor call by the mobile device 3 or the operator of the mobile device 3.

[0050] When a user operates the destination floor registration device 2, the reception unit 111 receives information including the destination floor and identification information of the destination floor registration device 2 from the destination floor registration device 2. Upon receiving this information, the reception unit 111 accepts the registration of a first landing destination floor call. Specifically, upon receiving the information, the reception unit 111 identifies the operated destination floor registration device 2 based on the identification information, identifies the departure floor of the user based on the floor on which the identified destination floor registration device 2 is located, and outputs information regarding the first landing destination floor call to the allocation unit 112.

[0051] Furthermore, when the reception unit 111 receives information including the destination floor, the departure floor, and the identification information of the moving device 3 from the moving device 3, the reception unit 111 accepts the registration of the second hall destination floor call.

[0052] The information on the landing destination floor call that the reception unit 111 outputs to the allocation unit 112 includes the departure floor, the destination floor, and the boarding type of the person using the elevator 5, i.e., information indicating whether the person using the elevator 5 is the user or the transportation device 3. The information on the landing destination floor call also includes identification information of the destination floor registration device 2 or the transportation device 3.

[0053] (Allocation unit 112) When the allocation unit 112 acquires information relating to the first landing destination floor call or the second landing destination floor call from the reception unit 111, the allocation unit 112 allocates elevator numbers of the elevator 5 to the first landing destination floor call and the second landing destination floor call based on the information. The method by which the allocation unit 112 allocates elevator numbers to landing destination floor calls may be a method based on selective collective operation similar to the allocation method in a general landing destination floor call registration system.

[0054] The allocation unit 112 stores information indicating the allocation result in the allocation information DB 121 of the storage unit 12. When the hall destination floor call is a second hall destination floor call, the allocation information DB 121 stores schedule information 122 indicating a schedule of the movement device 3 using the elevator 5.

[0055] When the elevator-hall destination floor call accepted by the acceptance unit 111 is the first elevator-hall destination floor call, the allocation unit 112 outputs information indicating the allocation result to the presentation unit 113.

[0056] When the landing destination floor call received by the reception unit 111 is a second landing destination floor call, the allocation unit 112 identifies the mobile device 3 that has registered the second landing destination floor call based on the identification information of the mobile device, and transmits information indicating the allocation result to the mobile device 3.

[0057] (Presentation part 113) When the landing-destination floor call received by the reception unit 111 is a first landing-destination floor call, the presentation unit 113 The presentation device 23 of the destination floor registration device 2 that the user operated to register the first hall destination floor call is caused to present information related to the first hall destination floor call.

[0058] When the presentation unit 113 acquires the information indicating the allocation result from the allocation unit 112, the presentation unit 113 transmits the information indicating the allocation result to the destination floor registration device 2 where the operation for registering the first hall destination floor call was performed, as information to be presented by the presentation device 23. The information indicating the allocation result includes information indicating the destination floor and the assigned car number.

[0059] Furthermore, the presentation unit 113 transmits schedule information 122 indicating the user's plan to get on and off the transportation device 3 at the departure floor to the destination floor registration device 2, and causes the presentation device 23 to present the schedule information 122.

[0060] When the presentation device 23 is a display device included in the destination floor registration device 2, the presentation unit 113 causes the display device to display the schedule information 122.

[0061] The destination floor registration device 2 used by a user to make a first-hall destination floor call is provided with a display device for notifying the user of information indicating the car number assigned to the first-hall destination floor call. By presenting the schedule information 122 using this display device, the user who made the first-hall destination floor call can be more reliably notified of the schedule information 122 regarding the boarding and alighting schedule of the moving device 3 that is present at the departure floor where the user gets on the car 51.

[0062] Furthermore, when a target elevator is assigned to a first hall destination floor call during a period from when the target elevator is assigned to a second hall destination floor call until the target elevator boards the moving device 3 and arrives at the destination floor of the moving device 3, the presentation unit 113 causes the presentation device 23 to present information other than the allocation result. For example, the presentation unit 113 causes the presentation device 23 to present schedule information 122 indicating the boarding and alighting schedule of the moving device 3 at the departure floor, which is the floor where a user boards the cage 51 of the target elevator.

[0063] The period from when a target elevator is assigned to a second hall destination floor call to when the mobile device 3 boards the target elevator and arrives at the destination floor of the mobile device 3 can also be rephrased as the period from when schedule information 122, which is information related to the second hall destination floor call, is stored in the memory unit 12 to when it is deleted.

[0064] During this period, when the target elevator assigned to the second landing destination floor call is assigned to the first landing destination floor call, the presentation unit 113 determines the schedule information 122 of the mobile device 3 that has registered the second landing destination floor call to which the target elevator is assigned, as information to be presented by the presentation device 23. The presentation unit 113 transmits the determined information to the destination floor registration device 2. As a result, the information determined by the presentation unit 113 is presented on the presentation device 23 of the destination floor registration device 2.

[0065] Specifically, when the presentation unit 113 acquires information indicating the allocation result for the first hall destination floor call from the allocation unit 112, it refers to the schedule information 122 in the storage unit 12. The presentation unit 113 determines whether or not there is schedule information 122 for a second hall destination floor call to which the same car number as the car number assigned to the first hall destination floor call by the user is assigned. If there is schedule information 122 for a mobile device 3 to which the same car number as the car number assigned to the user is assigned, the presentation unit 113 identifies the boarding and alighting schedule of the mobile device 3 at the departure floor of the user.

[0066] A case where there is schedule information 122 of a moving device 3 assigned the same car number as that assigned to a user is a case where a situation occurs in which the user and the moving device 3 encounter each other at a landing or car 51. A case where a user and a moving device 3 encounter each other at a landing or car 51 is, for example, a case where a user and a moving device 3 simultaneously use a car 51 of the same car number at the departure floor of the user. In such a case, the presentation unit 113 determines the schedule information 122 indicating the boarding and alighting schedule of the moving device 3 at the departure floor of the user as information to be presented by the presentation device 23 provided in the destination floor registration device 2.

[0067] The situation in which the user and the moving device 3 simultaneously use the cage 51 of the same target cage is, for example, the following situations (A) to (C). (A) A situation in which the transportation device 3 disembarks from the cage 51 when a user boards. (B) When a user boards, the transportation device 3 is in the cage 51 and the user does not disembark at the departure floor. (C) A situation in which the transportation device 3 also boards the same cage 51 when the user boards.

[0068] When the focused car assigned to the second landing destination floor call is assigned to the first landing destination floor call, if any of the situations (A) to (C) occurs, a situation occurs in which a user and a moving device 3 simultaneously use the cage 51 of the same focused car. In this case, the presentation unit 113 determines schedule information 122 indicating the boarding and alighting schedule of the moving device 3 at the departure floor of the user as information to be presented by the presentation device 23, and transmits the determined information to the destination floor registration device 2, thereby causing the presentation device 23 to present the information.

[0069] According to the above configuration, the hall-destination-floor registration system 100 can allow a user to know the status of a transportation device 3 to which the same vehicle number as the user is assigned at the departure floor of the user.

[0070] In addition, in cases where the user and the moving device 3 use the car 51 of the same car at the same time at the departure floor, the user and the moving device 3 may encounter each other. In this case, there is schedule information 122 of the moving device 3 that is assigned as a target car the same as the car assigned to the user. In such a case, the presentation unit 113 may determine the schedule information 122 of the moving device 3 that is assigned as the same car as the user as information to be presented by the presentation device 23. In this case, the information presented by the presentation unit 113 to the presentation device 23 may not be the boarding and alighting schedule of the moving device 3 at the departure floor of the user. For example, when a situation occurs where the user and the moving device 3 use the car 51 of the same car at the same time at the destination floor, the user and the moving device 3 encounter each other. In this case, the presentation unit 113 may present the boarding and alighting schedule of the moving device 3 at the destination floor of the user to the presentation device 23.

[0071] <Specific examples of situations where a user encounters a mobile device 3 and the contents presented> Below, examples of situations in which a user and a mobile device 3 encounter each other and examples of presentation of information determined by the presentation unit 113 will be described in more detail with reference to Figs. 3 to 10. Fig. 3 is a schematic diagram for explaining examples of situations in which a user and a mobile device 3 encounter each other. Figs. 4 to 10 are examples of screens presented by the presentation device 23. In Fig. 3, the arrows of a user (reference symbols X1 to X5 in Fig. 3) and the mobile device 3 indicate the direction of movement, the departure floor, and the destination floor based on the first hall destination floor call by the user and the second hall destination floor call by the mobile device 3.

[0072] Fig. 4 is an example of a screen for accepting an operation for registering a first hall destination floor call. As shown in Fig. 4, the presentation device 23 is a touch panel also functioning as the input unit 21, and the presentation unit 113 may cause the presentation device 23 to present a screen showing numbers or the like indicating floors. When a user performs an operation of inputting numbers or the like indicating a destination floor into the presentation device 23, the first hall destination floor call is registered in the hall destination floor registration system 100.

[0073] Fig. 5 is another example of a screen for accepting an operation for registering a first hall destination floor call. As shown in Fig. 5, the presentation unit 113 may cause the presentation device 23 to present a screen showing floors that can be serviced. In this case, the first hall destination floor call is registered in the hall destination floor registration system 100 by the user performing an operation on the presentation device 23 to select a number or the like that indicates a destination floor from the floors that can be serviced.

[0074] 6 to 10 are diagrams showing examples of screens that are displayed on the presentation device 23 when the registration of the first hall destination floor call is completed.

[0075] In the following, as shown in Figure 3, an example will be described in which a cage 51 is scheduled to move upward from the first floor in a 10-story building, and a second landing destination floor call with the fifth floor as the departure floor and the eighth floor as the destination floor has already been registered by the moving device 3 prior to the first landing destination floor call by the user.

[0076] When the moving device 3 already aboard the cage 51 of a target car that has arrived at the departure floor of the user is scheduled to disembark at the departure floor of the user, the user encounters the moving device 3 disembarking from the cage 51 at the departure floor of the user. In this case, the presentation unit 113 may present information indicating the schedule as schedule information.

[0077] Specifically, as shown in FIG. 3, when a first-board destination floor call is registered by user X1 with the 8th floor as the departure floor and the 9th floor as the destination floor, and when a target elevator is assigned to the first-board destination floor call, the transportation device 3 disembarks user X1 at the departure floor.

[0078] When the mobile device 3 gets off at the departure floor of user X1, the presentation unit 113 determines, in addition to the information indicating the allocation result, schedule information 122 indicating that the mobile device 3 is scheduled to get off at the departure floor of user X1, as information to be presented by the presentation device 23.

[0079] As shown in FIG. 6, the presentation device 23 of the destination floor registration device 2 used by the user to register the first hall destination floor call presents information 601 indicating the destination floor, information 602 indicating the assigned car number, and a message 603 indicating that the transportation device 3 is scheduled to disembark as the schedule information 122.

[0080] In addition, when the transportation device 3 already in the cage 51 of the target car that has arrived at the departure floor of the user is not scheduled to disembark at the departure floor of the user, the user encounters the transportation device 3 in the cage 51 at the departure floor of the user. In this case, the presentation unit 113 may present information indicating the schedule as the schedule information 122.

[0081] For example, as shown in Fig. 3, when a first hall destination floor call is registered by user X2 with the sixth floor as the departure floor and the seventh floor as the destination floor, and when a target elevator is assigned to the first hall destination floor call, the moving device 3 has already boarded the car 51 at the departure floor of the user. In addition, the moving device 3 does not get off at the departure floor of user X2, but maintains the boarded state.

[0082] In this case, the presentation unit 113 determines, in addition to the information indicating the allocation result, the schedule information 122 indicating that the mobile device 3 remains aboard at the departure floor of user X2 and that user X2 does not plan to disembark, as the information to be presented by the presentation device 23.

[0083] Also, as shown in FIG. 7, the presentation device 23 of the destination floor registration device 2 used by user X2 presents information 701 indicating the destination floor, information 702 indicating the assigned car number, and a message 703 indicating that the transportation device 3 is boarding at the user's departure floor as schedule information 122.

[0084] In addition, when the moving device 3 is scheduled to board the cage 51 of a target car at the departure floor of the user, the user encounters the moving device 3 boarding the cage 51 at the departure floor of the user. In this case, the presentation unit 113 may present information indicating the schedule as schedule information.

[0085] For example, as shown in FIG. 3, when a first-board destination floor call is registered by user X3 with the fifth floor as the departure floor and the seventh floor as the destination floor, and when a target elevator is assigned to the first-board destination floor call, the transportation device 3 is scheduled to board cage 51 at the departure floor of user X3.

[0086] In this case, the presentation unit 113 determines, as information to be presented by the presentation device 23, in addition to the information indicating the allocation result, schedule information 122 indicating that the mobile device 3 is scheduled to board at the departure floor of user X3.

[0087] Also, as shown in FIG. 8, the presentation device 23 of the destination floor registration device 2 used by user X3 presents information 801 indicating the destination floor, information 802 indicating the assigned car number, and a message 803 indicating that the mobile device 3 is scheduled to board at the user's departure floor as schedule information 122.

[0088] In addition, the presentation unit 113 may cause the presentation device 23 to present information other than the boarding / alighting schedule at the departure floor, i.e., the boarding / alighting schedule, as the schedule information 122 of the mobility device 3.

[0089] For example, when the same target vehicle is assigned to a first landing destination floor call and a second landing destination floor call, the presentation unit 113 may present schedule information 122 of the transportation device 3 from when the cage 51 of the target vehicle departs from the departure floor to when it arrives at the destination floor where the user plans to disembark.

[0090] Furthermore, in the case where a display device is provided in the car 51, the presentation unit 113 may also cause the display device to present the schedule information 122.

[0091] According to the above configuration, the hall-destination-floor registration system 100 can inform the user of information regarding the transportation device 3 using the same car 51 as the user, and the transportation device 3 that the user plans to use.

[0092] Furthermore, when the mobile device 3 is scheduled to board or disembark at the destination floor of the user, the user encounters the mobile device 3 getting on or off the car 51 at the destination floor of the user. In this case, the presentation unit 113 may cause the presentation device 23 to present schedule information 122 indicating the boarding and disembarking schedule of the mobile device 3 at the destination floor of the user.

[0093] For example, as shown in FIG. 3, when a first-board destination floor call is registered by user X4 with the third floor as the departure floor and the fifth floor as the destination floor, and when a target elevator is assigned to the first-board destination floor call, the transportation device 3 is scheduled to board cage 51 at the destination floor of user X4.

[0094] In this case, the presentation unit 113 determines, as information to be presented by the presentation device 23, in addition to the information indicating the allocation result, schedule information 122 indicating that the mobile device 3 is scheduled to board at the destination floor of the user X4.

[0095] Also, as shown in FIG. 9, the presentation device 23 of the destination floor registration device 2 used by user X4 presents information 901 indicating the destination floor, information 902 indicating the assigned car number, and a message 903 indicating that the mobile device 3 is scheduled to board at the user's destination floor as schedule information 122.

[0096] Furthermore, when the user is scheduled to board or disembark the mobile device 3 after boarding at a departure floor and before disembarking at a destination floor, the user encounters the mobile device 3 inside the car 51. In this case, the presentation unit 113 may determine, as the schedule information 122 to be presented by the presentation device 23, the boarding and disembarking schedule of the mobile device 3 while the user is traveling in the car 51.

[0097] For example, as shown in FIG. 3, when a first-board destination floor call is registered by user X5 with the fourth floor as the departure floor and the sixth floor as the destination floor, and when a target elevator is assigned to the first-board destination floor call, the mobile device 3 boards the elevator during the period when user X5 is riding in the cage 51.

[0098] In this case, the presentation unit 113 determines, in addition to the information indicating the allocation result, the information to be presented by the presentation device 23, as schedule information 122 indicating that the mobile device 3 is scheduled to board the cage 51 during the period in which the user X5 is boarding the cage 51.

[0099] Also, as shown in FIG. 10, the presentation device 23 of the destination floor registration device 2 used by user X5 presents information 1001 indicating the destination floor, information 1002 indicating the assigned car number, and, as schedule information 122, a message 1003 indicating that the transportation device 3 is scheduled to board at the 5th floor while user X5 is riding in the car 51.

[0100] Furthermore, when the mobile device 3 is in the car 51 when the user gets on and does not get off at the departure floor of the user (user X2), or when the mobile device 3 is also in the same car 51 when the user gets on (user X3), the presentation unit 113 causes the presentation device 23 to present the schedule information 122 of the mobile device 3. At this time, the presentation unit 113 may cause the presentation device 23 to present the schedule information 122 including the destination floor of the mobile device 3 in addition to the boarding and alighting schedule of the mobile device 3 at the departure floor of the user.

[0101] Furthermore, the presentation unit 113 may transmit information indicating the type of the moving device 3 to the destination floor registration device 2 in addition to the schedule information 122 of the moving device 3, and cause the presentation device 23 to present the information. Specifically, as shown in Figs. 6 to 10, the presentation unit 113 may cause the message indicating the schedule information 122 of the moving device 3 to be presented together with the information indicating the type of the moving device 3.

[0102] According to the above configuration, the boarding hall destination floor registration system 100 informs the user in advance of the type of transportation device 3 that the user plans to use for the vehicle number that he or she plans to board, thereby further reducing the psychological burden on the user.

[0103] <Specific example of a situation where the user and the mobile device 3 do not encounter each other> As described above, in the landing destination floor registration system 100, the same target vehicle is assigned to the first landing destination floor call and the second landing destination floor call, and when a user who has registered the first landing destination floor call encounters a mobile device 3 that has registered the second landing destination floor call, schedule information indicating the boarding and disembarking plans of the mobile device 3 is presented to the user.

[0104] Here, in the landing destination floor registration system 100, even if the same target vehicle is assigned to the first landing destination floor call and the second landing destination floor call, if the user does not encounter the mobile device 3, the user does not need to know the boarding and alighting schedule of the mobile device 3.

[0105] In the following, a specific example of a situation in which the same target car is assigned to a first hall destination floor call and a second hall destination floor call, and the user and the moving device 3 do not encounter each other, will be described with reference to Fig. 11. Fig. 11 is a schematic diagram for explaining an example of a situation in which the user and the moving device 3 do not encounter each other. In addition, in the following, as shown in Fig. 11, an example will be described in which, in a 10-story building, a car 51 is scheduled to move upward from the first floor, and a second hall destination floor call with the fifth floor as the departure floor and the eighth floor as the destination floor by the moving device 3 has been registered prior to the first hall destination floor call by the user.

[0106] For example, if the section in which the moving device 3 uses the cage 51 does not overlap with the section in which the user uses the cage 51, the user and the moving device 3 do not encounter each other. Specifically, as shown in Fig. 11, if a target elevator is assigned to a first hall destination floor call by user X6 with the second floor as the departure floor and the fourth floor as the destination floor, after user X6 gets off from the cage 51, the moving device 3 gets on the same cage 51. In this case, user X6 does not encounter each other with the moving device 3, and the presentation unit 113 does not cause the presentation device 23 of the destination floor registration device 2 operated by the user to present the schedule information.

[0107] Furthermore, if a user gets on the car 51 after the moving device 3 arrives at the destination floor, the user and the moving device 3 do not encounter each other. Specifically, as shown in Fig. 11, when a target elevator is assigned to a first hall destination floor call by user X7 with the 9th floor as the departure floor and the 10th floor as the destination floor, user X7 gets on to the car 51 after the moving device 3 gets off from the car 51. In this case, user X7 and the moving device 3 do not encounter each other, and the presentation unit 113 does not cause the presentation device 23 of the destination floor registration device 2 operated by the user to present the schedule information.

[0108] In addition, even if the section in which the moving device 3 uses the cage 51 overlaps with the section in which the user uses the cage 51, a situation may occur in which the user and the moving device 3 do not encounter each other. For example, when the moving direction of the user and the moving device 3 are different, a situation may occur in which the user and the moving device 3 do not encounter each other even if the boarding section of the user and the moving device 3 to the cage 51 overlap. Specifically, as shown in FIG. 11, when the target car is assigned to a first boarding hall destination floor call by user X8 with the 7th floor as the departure floor and the 4th floor as the destination floor, after the moving device 3 gets off the cage 51, the moving direction of the cage 51 is reversed, and user X8 gets on the cage 51. In this case, user X8 and the moving device 3 do not encounter each other. 11, when the target elevator is assigned to a first hall destination floor call by user X9 with the departure floor being the sixth floor and the destination floor being the fifth floor, the moving device 3 gets off the car 51, and then the moving direction of the car 51 is reversed, and user X9 gets on to the car 51. Therefore, user X9 and the moving device 3 do not encounter each other, and the presentation unit 113 does not cause the presentation device 23 of the destination floor registration device 2 operated by the user to present the schedule information.

[0109] 11, no matter which floor the car 51 is located on, the users X7 to X8 do not encounter the moving device 3, and the presentation unit 113 does not cause the presentation device 23 of the destination floor registration device 2 operated by the users to present the schedule information. However, if the car 51 is located on the 10th floor and the 5th floor is the reversal floor, the moving device 3 gets on when the user X9 gets off on the 5th floor, so the user X9 and the moving device 3 encounter each other. In this case, the presentation unit 113 causes the presentation device 23 of the destination floor registration device 2 operated by the user X9 to present the schedule information.

[0110] <An example of a process flow performed by the landing destination floor registration system 100> 12 and 13 are sequence diagrams showing an example of the flow of processing (control method) performed by the landing-destination-floor registration system 100. Hereinafter, an example of the flow of processing performed by the landing-destination-floor registration system 100 will be described with reference to FIGS. 12 and 13.

[0111] (An example of a flow of processes performed when the moving device 3 uses the elevator 5) First, a process flow performed in the hall destination floor registration system 100 when the moving device 3 uses the elevator 5 will be described with reference to Fig. 12. Fig. 12 is a sequence diagram showing an example of a process flow performed in the hall destination floor registration system 100 when the moving device 3 registers a hall destination floor call for the elevator 5 and uses the elevator 5.

[0112] First, when the moving device 3 uses the elevator 5, it transmits information about the second hall destination floor call to the group management control device 1. The information about the second hall destination floor call includes the departure floor where the moving device 3 plans to board the cage 51 of the elevator 5, the destination floor where the moving device 3 plans to disembark from the cage 51, and identification information for identifying the moving device 3. Note that the information about the second hall destination floor call may include information indicating the type of the moving device 3.

[0113] The reception unit 111 of the group management control device 1 waits for processing until it receives information on the second hall destination floor call from the mobile device 3 (i.e., until YES is returned in S11). When the reception unit 111 receives the information on the second hall destination floor call from the mobile device 3, it accepts the registration of the second hall destination floor call of the mobile device 3 (YES in S11: reception step). The reception unit 111 outputs the received information on the second hall destination floor to the allocation unit 112.

[0114] When the allocation unit 112 acquires information regarding the second hall destination floor from the reception unit 111, it allocates a target elevator that is the optimal elevator for the second hall destination floor call based on the information and the operating status of each elevator 5 (S12: allocation step).

[0115] The allocation unit 112 identifies the mobile device 3 that transmitted the information on the second hall destination floor call based on the identification information of the mobile device 3, and transmits information indicating the allocation result to the mobile device 3 that transmitted the information on the second hall destination floor call (S13). The information indicating the allocation result includes information indicating the allocated target car.

[0116] When the moving device 3 receives information indicating the allocation result (YES in S1), it waits for the cage 51 of the allocated target car at the boarding area of ​​the departure floor. When the cage 51 of the target car arrives at the departure floor, the moving device 3 gets on the cage 51, and when the cage 51 arrives at the destination floor, the moving device 3 gets off the cage 51.

[0117] When the moving device 3 disembarks from the car 51 (YES in S2), the moving device 3 may transmit to the group management control device 1 disembarking information indicating that the passenger has disembarked from the car 51 of the noted car.

[0118] When the control unit 11 of the group management control device 1 receives the disembarking information (YES in S14), it deletes the registration of the second hall destination floor call made by the moving device 3 that has disembarked from the car 51 and completed use of the elevator 5 (S15).

[0119] (An example of a process flow when a user uses elevator 5) Next, a process flow performed in the hall destination floor registration system 100 when a user uses the elevator 5 will be described with reference to Fig. 13. Fig. 13 is a sequence diagram showing an example of a process flow performed in the hall destination floor registration system 100 when a user registers a hall destination floor call.

[0120] When a user uses the elevator 5, an operation is performed to input information regarding a first hall destination floor call to the input unit 21 of the destination floor registration device 2.

[0121] When the input unit 21 of the destination floor registration device 2 accepts an operation to input information regarding the first landing destination floor call (YES in S21), the control unit 22 of the destination floor registration device 2 transmits information regarding the first landing destination floor call based on the accepted input operation to the group management control device 1. The information regarding the first landing destination floor call includes information indicating the destination floor input by the user and identification information for identifying the destination floor registration device 2 on which the input operation was performed.

[0122] When the reception unit 111 receives information related to the first hall destination floor call from the destination floor registration device 2, it identifies the destination floor registration device 2 on which the input operation related to the first hall destination floor call was performed, based on the identification information of the destination floor registration device 2. The reception unit 111 also identifies the floor on which the destination floor registration device 2 on which the input operation was performed is installed, as the departure floor of the user. This completes the acceptance of the registration of the first hall destination floor call in the reception unit 111 (YES in S31: acceptance step). The reception unit 111 outputs to the allocation unit 112 the information related to the accepted first hall destination floor call and information indicating the identified departure floor of the user.

[0123] When the allocation unit 112 acquires information regarding the first hall destination floor call and information indicating the departure floor of the identified user from the reception unit 111, the allocation unit 112 allocates the optimal elevator to the first hall destination floor call based on the user's departure floor, destination floor, and the operating status of each elevator 5 (S32: allocation step).

[0124] After step S32, the allocation unit 112 refers to the allocation information DB 121 in the storage unit 12 and determines whether or not there is a transportation device 3 that is scheduled to use the vehicle allocated to the first hall destination floor call (S33).

[0125] When the target vehicle is assigned to the first hall destination floor call during the period from when the target vehicle is assigned to the second hall destination floor call until the mobile device 3 boards the target vehicle and arrives at the destination floor of the mobile device 3, the mobile device 3 is scheduled to use the vehicle assigned to the first hall destination floor call. In this case, the assignment unit 112 determines that there is a mobile device 3 that is scheduled to use the vehicle assigned to the first hall destination floor call.

[0126] The period from when a target elevator is assigned to a second hall destination floor call to when the mobile device 3 boards the target elevator and arrives at the destination floor of the mobile device 3 is, for example, the period during which the processing from step S12 to step S15 in the processing shown in Figure 12 is executed.

[0127] 2, the second hall destination floor call of the moving device 3 to which the elevator B of the elevator 5 is assigned is registered. Here, when the elevator B of the elevator 5 is assigned to the first hall destination floor call, the assignment unit 112 determines that there is a moving device 3 that plans to use the assigned elevator for the first hall destination floor call (YES in S33).

[0128] 2, the second hall destination floor call of the moving device 3 to which the elevator A of the elevator 5 is assigned is not registered. Here, when the elevator A of the elevator 5 is assigned to the first hall destination floor call, the assignment unit 112 determines that there is no moving device 3 that plans to use the elevator assigned to the first hall destination floor call (NO in S33). Note that other examples of the situation in which there is a moving device 3 that plans to use the elevator assigned to the first hall destination floor call have already been described, and therefore will not be described here.

[0129] If there is a moving device 3 that is scheduled to use the vehicle assigned to the first hall destination floor call (YES in S33), the allocation unit 112 further determines whether the moving device 3 and the user will use the target vehicle at the same time (S34). In addition, the allocation unit 112 outputs information indicating the result of the determination to the presentation unit 113.

[0130] For example, in the example shown in FIG. 2, the second hall destination floor call of the moving device 3 to which the elevator F of the elevator 5 is assigned is registered, and the departure floor is the 5th floor and the destination floor is the 8th floor. Here, if the departure floor of the user specified by the first hall destination floor call to which the elevator F of the elevator 5 is assigned is the 8th floor and the destination floor is the 9th floor, the moving device 3 gets off from the cage 51 of the elevator F on the 8th floor, and the user gets on to the cage 51 of the elevator F. In such a case, the allocation unit 112 determines that the moving device 3 and the user use the target vehicle at the same time (YES in S34). Note that other examples of situations in which the moving device 3 and the user use the target vehicle at the same time have already been described, and therefore will not be described here.

[0131] 2, when the departure floor of the user specified by the first hall destination floor call to which elevator F of elevator 5 is assigned is floor 9 and the destination floor is floor 10, the moving device 3 does not use the car 51 during the period from when the user gets on to when he or she gets off the car 51. In such a case, the allocation unit 112 determines that the moving device 3 and the user do not use the target car at the same time (NO in S34).

[0132] When it is determined that the moving device 3 and the user will use the target car at the same time (YES in S34), the allocation unit 112 outputs information indicating the result of the determination and the allocation result to the presentation unit 113. Upon acquiring the result of the determination and the information indicating the allocation result, the presentation unit 113 refers to the allocation information DB 121 and determines the information to be presented by the presentation device 23.

[0133] Specifically, information indicating the boarding and disembarking schedule of the user at the departure floor of the transportation device 3 that is scheduled to use the target car at the same time as the user is determined as the schedule information 122 of the transportation device 3 to be presented by the presentation device 23.

[0134] The presentation unit 113 may include information other than the information indicating the boarding and alighting schedule of the user's travel device 3 at the departure floor in the schedule information 122 of the travel device 3 to be presented by the presentation device 23. For example, the presentation unit 113 may include the boarding and alighting schedule of the travel device 3 at the user's destination floor, the boarding and alighting schedule of the travel device 3 in the user's boarding section, and information indicating the type of travel device in the schedule information 122 of the travel device 3 to be presented by the presentation device 23.

[0135] The presentation unit 113 transmits information indicating the allocation result and the schedule information 122 determined as the information to be presented by the presentation device 23 to the destination floor registration device 2 that transmitted the information regarding the first hall destination floor call (S35). The information indicating the allocation result includes information indicating the destination floor of the user and the assigned elevator.

[0136] If there is no transportation device 3 that is scheduled to use the vehicle assigned to the first hall destination floor call (NO in S33), the assignment unit 112 outputs to the presentation unit 113 the result of the determination and information indicating the assignment result.

[0137] Furthermore, if the moving device 3 and the user do not use the target car at the same time (NO in S34), the allocation unit 112 outputs information indicating the determination result and the allocation result to the presentation unit 113. Upon acquiring the information indicating the determination result and the allocation result, the presentation unit 113 refers to the allocation information DB 121 and determines the information to be presented by the presentation device 23.

[0138] If the answer is NO in step S33 or step S34, the presentation unit 113 determines that only the information indicating the allocation result is to be presented by the presentation device 23, and transmits the information to the destination floor registration device 2 where the operation for registering the first hall destination floor call was performed (S36). The information indicating the allocation result includes information indicating the destination floor of the user and the assigned elevator.

[0139] After step S35 or step S36, the control unit 22 of the destination floor registration device 2 receives at least information indicating the allocation result from the group management control device 1 (YES in S22), and causes the presentation device 23 to present the received information.

[0140] Here, if the control unit 22 receives the schedule information 122 together with information indicating the allocation result (YES in S23), the control unit 22 causes the presentation device 23 to present the schedule information 122 of the mobile device 3 at the user's destination floor, the assigned elevator, and the user's departure floor (S24: presentation step).

[0141] On the other hand, when only the information indicating the allocation result is received (NO in S23), the control unit 22 causes the presentation device 23 to present the destination floor of the user and the assigned elevator (S25).

[0142] In this manner, in the elevator-hall / destination floor registration system 100, appropriate information is presented to the user who has registered the first elevator-hall / destination floor call.

[0143] In the above description, an example has been described in which the hall destination floor registration system 100 presents to the presentation device 23 the schedule information 122 indicating the boarding and alighting schedule of the mobility device 3 when the mobility device 3 and the user use the same target vehicle at the same time at the departure floor of the user. However, the hall destination floor registration system 100 may also cause the presentation device 23 to present the schedule information 122 indicating the boarding and alighting schedule of the mobility device 3 even when the mobility device 3 and the user do not use the same target vehicle at the same time at the departure floor of the user.

[0144] For example, when the moving device 3 does not get on or off at the departure floor of the user, or does not pass through the departure floor of the user, the moving device 3 and the user do not use the same target vehicle at the same time at the departure floor of the user. Even in such a case, when the moving device 3 and the user are assigned the same target vehicle, the presentation unit 113 may determine information indicating the boarding and alighting schedule of the moving device 3 as information to be presented by the presentation device 23. For example, when the user and the moving device 3 plan to use the same vehicle, the presentation unit 113 may also identify schedule information 122 indicating the boarding and alighting schedule of the moving device 3 at a floor other than the departure floor of the user, and determine it as information to be presented by the presentation device 23. In this case, the step of determining whether the moving device 3 and the user use the target vehicle at the same time (step S34) may be omitted.

[0145] [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.

[0146] <Platform destination floor registration system 100A> Fig. 14 is a block diagram showing the configuration of a landing-destination floor registration system 100A according to embodiment 2. As shown in Fig. 14, the landing-destination floor registration system 100A includes a group management control device 1A, a destination floor registration device 2A, a movement device 3, an elevator control device 4, and an elevator 5.

[0147] In the landing destination floor registration system 100A, allocation control is performed for the first landing destination floor calls and the second landing destination floor calls based on the tolerance information 123 indicating whether or not it is permissible for the user and the mobile device 3 to encounter each other when using the same elevator car 51.

[0148] If it is not permitted for the user and the transportation device 3 to encounter each other when using the same car 51, the hall / destination floor registration system 100A performs at least one of the following controls (1) and (2).

[0149] (1) Control of assigning car numbers so that a user does not encounter a transportation device 3 using the same car 51 when boarding and disembarking.

[0150] (2) Control for allocating elevators so that the moving device 3 does not board an elevator car 51 in which a user is currently riding.

[0151] According to the above configuration, it is possible to assign car numbers taking into consideration users who wish to avoid riding in the same car as the moving device 3 or encountering the moving device 3 when getting on or off.

[0152] <Destination floor registration device 2A> As shown in Fig. 14, the destination floor registration device 2A includes a control unit 22A. The control unit 22A is capable of receiving an inquiry from the group management control device 1A. Upon receiving the inquiry from the group management control device 1A, the control unit 22A causes the presentation device 23 to present tolerance information 123 indicating whether it is acceptable for the user and the mobility device 3 to encounter each other when using the same car 51, and an acceptability selection button for allowing the user to select it. The control unit 22A transmits the tolerance information 123 indicating the selected acceptability to the group management control device 1A.

[0153] <Group management control device 1A> As shown in FIG. 14, the group management control device 1A includes a control unit 11A, a storage unit 12A, and an input / output interface 13.

[0154] As shown in Fig. 14, the storage unit 12A stores an allocation information DB 121A. Fig. 15 is a diagram showing an example of the allocation information DB 121A. As shown in Figs. 14 and 15, the allocation information DB 121A includes schedule information 122A and allowable information 123.

[0155] The tolerance information 123 is information indicating whether it is acceptable for a user and a moving device 3 to encounter each other when using the same car 51. As shown in Fig. 15, the tolerance information 123 is stored in association with information related to a first hall destination floor call by a user. Also, as shown in Fig. 15, the tolerance information 123 may be set for each type of moving device 3.

[0156] Also, as shown in FIG. 15, in the allocation information DB 121A, information in which the boarding type is “transportation device”, i.e., schedule information 122A regarding a second hall destination floor call, may be stored in association with information indicating the type of transportation device 3.

[0157] When the tolerance information 123 indicates tolerance, the group management control device 1A performs car allocation control that permits a situation in which a user uses the same car 51 as the moving device 3. On the other hand, when the tolerance information 123 indicates impermissibility, the group management control device 1A performs car allocation control so as to prevent a situation in which a user uses the same car 51 as the moving device 3.

[0158] 14, the control unit 11A includes a reception unit 111, an allocation unit 112A, and a presentation unit 113A. The control unit 11A of the group management control device 1A also includes an allowance information reception unit 114.

[0159] (Permissible information receiving unit 114) The tolerance information receiving unit 114 can receive, by a user, input of tolerance information 123 indicating whether it is tolerable for the user and the moving device 3 to encounter each other when using the same car 51.

[0160] The permissible information 123 selected by the user is received from the destination floor registration device 2A. The permissible information receiving unit 114 outputs the received permissible information 123 and the identification information of the destination floor registration device 2 where the operation to select the permissible information 123 was performed to the allocation unit 112A.

[0161] (Allocation section 112A) The allocation unit 112A allocates a car number based on the tolerance information 123, which indicates whether it is acceptable for the user and the moving device 3 to encounter each other when using a car 51 of the same car, selected by the user.

[0162] [Allocation when a destination floor call is received from the first boarding area] When the reception unit 111 receives a registration of a first hall destination floor call and the permissible information 123 received by the permissible information reception unit 114 indicates that the call is not permissible, the allocation unit 112A performs at least one of the following controls (1) and (2).

[0163] (1) Control of assigning car numbers so that a user does not encounter a transportation device 3 using the same car 51 when boarding and disembarking.

[0164] (2) Control for allocating elevators so that the moving device 3 does not board an elevator car 51 in which a user is currently riding.

[0165] When the tolerance information 123 indicates impermissibility, the allocation unit 112A searches for candidates for vehicles that can be allocated to the first hall destination floor call. When a certain vehicle of the elevator 5 is allocated, if at least one of the following occurs: a user encounters a moving device 3 using the cage 51 of the same vehicle when the user boards and disembarks, and the moving device 3 boards the cage 51 of the vehicle in which the user is boarding, the allocation unit 112A excludes the vehicle from candidates for allocation to the first hall destination floor call. The allocation unit 112A makes a similar determination for each vehicle of the elevator 5, determines candidates for allocation to the first hall destination floor call, and allocates the optimal vehicle from the candidates to the first hall destination floor call.

[0166] On the other hand, when the tolerance information 123 indicates tolerance, the allocation unit 112A sets all elevators 5 as candidates for allocation, and allocates the optimal elevator to the first hall destination floor call.

[0167] A specific example of the allocation control of the allocation unit 112A will be described with reference to Fig. 15. In the example shown in Fig. 15, car F is allocated to a second hall destination floor call with the 5th floor as the departure floor and the 8th floor as the destination floor, and car B is allocated to a second hall destination floor call with the 1st floor as the departure floor and the 10th floor as the destination floor.

[0168] First, an example will be given in which the reception unit 111 receives a registration of a first hall destination floor call with the 8th floor as the departure floor and the 9th floor as the destination floor, and the acceptance information reception unit 114 receives acceptance information 123 indicating that acceptance is not permitted. In the example shown in Fig. 15, if car F is assigned to this first hall destination floor call, when the user boards the car, the user encounters a moving device 3 that disembarks from the cage 51 of the same car. In such a case, the allocation unit 112A performs allocation by excluding car F from candidates for cars to be assigned to the first hall destination floor call.

[0169] Next, a case will be taken as an example in which the reception unit 111 receives a registration of a first hall destination floor call with the 8th floor as the departure floor and the 9th floor as the destination floor, and the acceptance information reception unit 114 receives acceptance information 123 indicating that acceptance is not possible. In the example shown in Fig. 15, if vehicle B is assigned to this first hall destination floor call, the user will encounter a transportation device 3 aboard the same vehicle when the user boards the vehicle. In such a case, the assignment unit 112A performs assignment by excluding vehicle B from candidates for vehicles to be assigned to the first hall destination floor call.

[0170] Next, a case will be described as an example in which the reception unit 111 receives the registration of a first hall destination floor call having the third floor as the departure floor and the fourth floor as the destination floor, and the acceptance information reception unit 114 receives the acceptance information 123 indicating that the acceptance is not acceptable. In the example shown in FIG. 15, even if the F-numbered car is assigned to this first hall destination floor call, the user will not encounter the mobile device 3 using the cage 51 of the same car when the user boards and disembarks. In addition, even if the F-numbered car is assigned to the first hall destination floor call, the mobile device 3 will not board the cage 51 of the car in which the user is boarding. In this case, the allocation unit 112A performs allocation by including the F-numbered car in candidates for cars to be assigned to the first hall destination floor call.

[0171] Next, a case will be described as an example in which the reception unit 111 receives the registration of a first hall destination floor call having the 8th floor as the departure floor and the 9th floor as the destination floor, and the permissible information reception unit 114 receives the permissible information 123 indicating permissible. In the example shown in Fig. 15, if the F car is assigned to this first hall destination floor call, when the user boards the vehicle, the user encounters a moving device 3 that gets off from the cage 51 of the same car. However, since the user who registered the first hall destination floor call has selected the permissible information 123 indicating permissible, the allocation unit 112A assigns from among all the cars, including the F car, to the candidates for cars to be assigned to the first hall destination floor call.

[0172] [Inquiry for Permitted Information 123] Furthermore, when the reception unit 111 has received a registration of a first hall destination floor call and the permissible information reception unit 114 has not received the permissible information 123 indicating permissibility, the allocation unit 112A determines whether or not the user and the moving device 3 will simultaneously use the car 51 of any car. When the user and the moving device 3 will simultaneously use the car 51 of any car, the allocation unit 112A outputs information indicating that an inquiry about the permissible information 123 needs to be made to the user to the presentation unit 113A.

[0173] [Allocation when a destination floor call is received at the 3rd platform] In the hall destination floor registration system 100A, during the period from when any car is assigned to the first hall destination floor call until the mobile device 3 boards the car and arrives at the user's destination floor, a situation may occur in which the reception unit 111 accepts a new registration of a hall destination floor call from the mobile device 3. When such a situation occurs, the allocation unit 112A may allocate a car to the hall destination floor call from the mobile device 3 based on the user's tolerance information 123.

[0174] Hereinafter, a landing-destination floor call from a moving device 3 newly received by the reception unit 111 after the allocation to the second landing-destination floor call has been completed will be referred to as a "third landing-destination floor call".

[0175] For example, when the tolerance information 123 received by the tolerance information receiving unit 114 indicates non-permission and the receiving unit 111 receives the registration of a third-hall destination floor call during a period in which a first-hall destination floor call is registered, the allocation unit 112A performs at least one of the following controls (1) and (2) for the third-hall destination floor call.

[0176] (1) Control of assigning car numbers so that a user does not encounter a transportation device 3 using the same car 51 when boarding and disembarking.

[0177] (2) Control for allocating elevators so that the moving device 3 does not board an elevator car 51 in which a user is currently riding.

[0178] The allocation control by the allocation unit 112A when the reception unit 111 receives a third-hall destination floor call will be described with reference to FIG.

[0179] For example, it is assumed that the reception unit 111 receives a registration of a third hall destination floor call with the 8th floor as the departure floor and the 9th floor as the destination floor from the moving device 3, which is a cleaning robot. In the example shown in FIG. 15, when the D-unit is assigned to the third hall destination floor call, the moving device 3 gets on when the user gets off, that is, a situation occurs in which the user and the moving device 3 encounter each other. Also, in the example shown in FIG. 15, when the D-unit is assigned to the third hall destination floor call, a situation occurs in which the moving device 3 gets on the car 51 in which the user is riding. Also, the first hall destination floor call to which the D-unit is assigned is associated with the permission information 123 indicating that it is not permissible. In this case, the assignment unit 112A excludes the D-unit from candidates for elevators 5 to be assigned to the third hall destination floor call.

[0180] Also, assume that the reception unit 111 receives a registration of a third hall destination floor call with the 8th floor as the departure floor and the 9th floor as the destination floor from the moving device 3 which is a cleaning robot. In the example shown in FIG. 15, when the elevator C is assigned to the third hall destination floor call, the moving device 3 gets on when the user gets off, that is, the situation where the user and the moving device 3 encounter each other and the moving device 3 gets on the car 51 in which the user is riding do not occur. In this case, although the first hall destination floor call to which the elevator C is assigned is associated with the permission information 123 indicating that it is not permissible, the assignment unit 112A assigns the elevator C to the third hall destination floor call by including the elevator C in the candidates for the elevators 5 to be assigned.

[0181] Also, assume that the reception unit 111 receives a registration of a third hall destination floor call with the fifth floor as the departure floor and the seventh floor as the destination floor from the moving device 3, which is a cleaning robot. In the example shown in FIG. 15, when the elevator A is assigned to the third hall destination floor call, the moving device 3 gets on when the user gets off, that is, a situation occurs in which the user and the moving device 3 encounter each other, and a situation occurs in which the moving device 3 gets on the car 51 in which the user is riding. However, as shown in FIG. 15, the first hall destination floor call to which the elevator A is assigned is associated with the allowance information 123 indicating that all of the first hall destination floor calls are allowable. In this case, the allocation unit 112A assigns the elevator A to the elevator 5 by including the elevator A in the candidates for the elevators 5 to be assigned to the third hall destination floor call.

[0182] According to the above configuration, in consideration of users who wish to avoid using the same car number as the mobile device 3 or encountering the mobile device 3 when boarding or disembarking, a car number can be assigned to the third boarding hall destination floor call, which is a new boarding hall destination floor call by the mobile device 3 or the operator of the mobile device 3.

[0183] Furthermore, the allocation unit 112A may control the allocation depending on the type of the mobile device 3.

[0184] For example, assume that the reception unit 111 receives a registration of a third hall destination floor call with the 8th floor as the departure floor and the 9th floor as the destination floor from the mobile device 3 which is a delivery robot. In the example shown in Fig. 15, when the D-unit is assigned to the third hall destination floor call, the mobile device 3 gets on when the user gets off, that is, a situation occurs in which the user and the mobile device 3 encounter each other. Also, in the example shown in Fig. 15, when the D-unit is assigned to the third hall destination floor call, a situation occurs in which the mobile device 3 gets on in the car 51 in which the user is riding.

[0185] Here, the first hall destination floor call to which elevator D is assigned is associated with tolerance information 123 indicating that it is not acceptable for cleaning robots and security robots, but is associated with tolerance information 123 indicating that it is acceptable for home delivery robots. In this case, the allocation unit 112A assigns elevator D to the third hall destination floor call by including it in the candidates for elevators 5 to be assigned to the third hall destination floor call.

[0186] This allows the elevator-hall / destination floor registration system 100A to perform allocation according to the type of the transportation device 3.

[0187] In addition, when a user who has registered the first landing destination floor call has not selected acceptability, that is, when the first landing destination floor call registered in the allocation information DB 121A does not include the acceptance information 123, the acceptance information 123 of the user may be treated as a preset state. For example, when any of the first landing destination floor calls registered in the allocation information DB 121A does not include the acceptance information 123 and a third landing destination floor call is registered, the allocation unit 112A may allocate the acceptance information 123 corresponding to the first landing destination floor call to the third landing destination floor call as acceptability.

[0188] (Presentation part 113A) When the presentation unit 113A acquires information indicating that an inquiry about the permissible information 123 is necessary from the allocation unit 112A, it transmits an inquiry about the permissible information 123 to the destination floor registration device 2A operated by the user. The inquiry about the permissible information 123 includes information instructing the presentation of an acceptance / rejection button capable of accepting a selection of the permissible information 123. As a result, the acceptance / rejection button is displayed on the presentation device 23 of the destination floor registration device 2A.

[0189] <An example of a process flow performed by the landing destination floor registration system 100A> An example of the flow of processing performed by the hall destination floor registration system 100A according to the second embodiment will be described below with reference to Fig. 16 and Fig. 17. Fig. 16 is a flowchart for explaining an example of the flow of processing performed by the destination floor registration device 2A according to the second embodiment. Fig. 17 is a flowchart for explaining an example of the flow of processing performed by the group management control device 1A according to the second embodiment.

[0190] (Processing flow performed by the destination floor registration device 2A) First, the flow of processing performed by the destination floor registration device 2A will be described with reference to Fig. 16. In the destination floor registration device 2A, when an operation for a first-hall destination floor call is performed on the input unit 21 (YES in S41), the control unit 22A transmits information related to the first-hall destination floor call to the group management control device 1.

[0191] Next, when the presentation unit 113A acquires information indicating that an inquiry about the permissible information 123 is necessary from the allocation unit 112A, the presentation unit 113A transmits the inquiry about the permissible information 123 to the destination floor registration device 2 operated by the user.

[0192] When the control unit 22A receives an inquiry about the acceptable information 123 from the group management control device 1A, which includes information instructing the presentation of an acceptable / unacceptable button capable of accepting selection of the acceptable information 123 (YES in S42), the control unit 22A causes the presentation device 23 to present the acceptable / unacceptable button (S43).

[0193] Control unit 22A waits for the next process until the user selects tolerance information 123 indicating tolerance or impermissibility (that is, until YES is returned in S44 or S46).

[0194] After the presentation device 23 is caused to present the permissible / unpermissible button, if the permissible information 123 indicating permissible is selected by the user (YES in S44), the control unit 22A transmits to the group management control device 1A information relating to the first hall destination floor call and information indicating that the permissible information 123 indicating permissible has been selected (S45). The information relating to the first hall destination floor call by the control unit 22A may be the same information as that transmitted to the group management control device 1A in the case of YES in step S41.

[0195] If the tolerance information 123 indicating acceptability is not selected (NO in S44) and the tolerance information 123 indicating inadmissibility is selected (YES in S46), the control unit 22A transmits to the group management control device 1A information regarding the first hall destination floor call and information indicating that the tolerance information 123 indicating inadmissibility has been selected (S47).

[0196] After step S45 or step S47, the control unit 22A waits for information indicating the allocation result from the group management control device 1A. When information indicating the allocation result is received from the group management control device 1A (YES in S48), the control unit 22A performs the process of the next step S49.

[0197] Alternatively, after the control unit 22A transmits information regarding the first hall destination floor call to the group management control device 1A, if the control unit 22A does not receive an inquiry about the tolerance information 123 (NO in S42) but receives information indicating the allocation result from the group management control device 1A (YES in S48), the control unit 22A performs the processing of the next step S49 without performing the processing of steps S43 to S47.

[0198] The processing of steps S48 to S51 after receiving the information indicating the allocation result from the group management control device 1A is similar to the processing of steps S22 to S25 described using FIG. 14, and therefore a description thereof will be omitted here.

[0199] (Flow of processing performed by the group management control device 1A) Next, the flow of processing performed by the group management control device 1A will be described with reference to Fig. 17. When the reception unit 111 receives information relating to the first landing destination floor call from the destination floor registration device 2A (YES in S61), it outputs the received information to the permissible information reception unit 114. The permissible information reception unit 114 determines whether or not the information relating to the first landing destination floor call received from the destination floor registration device 2A includes permissible information 123 indicating whether or not the information is permissible (S62), and outputs information indicating the determination result to the reception unit 111 and the allocation unit 112A.

[0200] If the information regarding the first hall destination floor call does not include the acceptance information 123 indicating acceptance or rejection (NO in S62), the allocation unit 112A determines whether the user and the transportation device 3 will use the same car 51 at the same time (S63).

[0201] If the information on the first hall destination floor call does not include the permissible information 123 indicating permissible or not (NO in S62) and the user and the transportation device 3 use either car 51 at the same time (YES in S63), the reception unit 111 does not accept the registration of the first hall destination floor call. In this case, the reception unit 111 waits for processing until it receives information on the first hall destination floor call including the permissible information 123 after sending the inquiry on the permissible information 123 (S64 described later).

[0202] When the user and the moving device 3 use the same car 51 at the same time (YES in S63), the allocation unit 112A outputs information indicating that an inquiry about the allowable information 123 is required to the user to the presentation unit 113A.

[0203] When the presentation unit 113A acquires information indicating that an inquiry about the permissible information 123 is necessary from the allocation unit 112A, it transmits an inquiry about the permissible information 123 to the destination floor registration device 2A operated by the user (S64). As a result, an acceptance / rejection button is displayed on the presentation device 23 of the destination floor registration device 2A, and the user selects the permissible information 123 on the destination floor registration device 2A.

[0204] If the information regarding the first hall destination floor call includes tolerance information 123 indicating whether or not the call is acceptable (YES in S62), the tolerance information receiving unit 114 determines whether or not the call is acceptable based on the tolerance information 123 (S65) and outputs the determination result to the allocation unit 112A.

[0205] The allocation unit 112A controls the allocation of elevators based on the determination result of the permissible information receiving unit 114 and the information related to the first hall destination floor call received by the receiving unit 111.

[0206] When the tolerance information 123 indicates tolerance (YES in S65), the allocation unit 112A allocates the optimal elevator number from among all elevator numbers of the elevators 5 to the first hall destination floor call (S66).

[0207] Furthermore, if the information on the first hall destination floor call does not include the permissible information 123 indicating permissibility (NO in S62) and the user and the moving device 3 do not use any car 51 of the elevator at the same time (NO in S63), the reception unit 111 accepts the registration of the first hall destination floor call. In this case, the allocation unit 112 allocates the optimal car from among all the elevators 5 to the first hall destination floor call (S66).

[0208] If the permission information 123 indicates that permission is not permitted (NO in S65), the allocation unit 112A allocates the optimal car number from among the cars that are not used simultaneously by the user and the mobile device 3 (S67). For example, the allocation unit 112A performs at least one of the following controls (1) and (2). The controls (1) and (2) have already been described, so their description will be omitted here.

[0209] (1) Control of assigning car numbers so that a user does not encounter a transportation device 3 using the same car 51 when boarding and disembarking.

[0210] (2) Control for allocating elevators so that the moving device 3 does not board an elevator car 51 in which a user is currently riding.

[0211] The processes (S68 to S71) after the allocation unit 112A allocates a car to the first hall destination floor call are similar to the processes of steps S33 to S36 described using Fig. 14, and therefore the description thereof will be omitted here. Note that, when the allocation unit 112A performs the process of step S71, a situation does not occur in which the moving device 3 and the user use the same car at the same time, so the processes of steps S68 and S69 are not performed and the process directly proceeds to the process of step S71.

[0212] In the manner described above, the first hall destination floor call is registered in the hall destination floor registration system 100A, the allowable information 123 is queried, elevator numbers are assigned, and the information is presented by the presentation device 23.

[0213] [Software implementation example] The functions of the landing / destination floor registration system 100, 100A (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 units 11, 11A, 22, 22A).

[0214] 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.

[0215] 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.

[0216] 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.

[0217] 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).

[0218] 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.

[0219] 〔summary〕 The landing destination floor registration system according to aspect 1 of the present invention comprises a reception unit that receives registration of a first landing destination floor call by a user and registration of a second landing destination floor call by a mobile device or an operator of the mobile device, an assignment unit that assigns elevator numbers to the first landing destination floor call and the second landing destination floor call, and a presentation unit that causes a presentation device to present schedule information indicating the boarding and alighting schedule of the mobile device at at least one of the departure floor, which is a floor where the user boards the cage of the mobile device, and the destination floor, which is a floor where the user alights from the cage of the mobile device, when the mobile device of interest is assigned to the first landing destination floor call during a period from when a target elevator is assigned to the second landing destination floor call to when the mobile device boards the target elevator and arrives at a destination floor of the mobile device, and when the mobile device and the user encounter each other when boarding and alighting, the mobile device using the same elevator car.

[0220] In the boarding hall destination floor registration system of aspect 2 of the present invention, in the above-mentioned aspect 1, when the mobile device that has boarded the cage of the target elevator that has arrived at the departure floor is scheduled to disembark at the departure floor, the presentation unit may present information indicating the schedule as the schedule information.

[0221] In the boarding hall destination floor registration system of aspect 3 of the present invention, in aspect 1 or 2 above, if the mobile device that has boarded the cage of the target elevator that has arrived at the departure floor is not scheduled to disembark at the departure floor, the presentation unit may present information indicating the schedule as the schedule information.

[0222] A boarding-hall destination floor registration system according to aspect 4 of the present invention is the boarding-hall destination floor registration system described in claim 1, wherein, in any of aspects 1 to 3 above, when the mobile device is scheduled to board the cage of the target elevator at the departure floor, the presentation unit presents information indicating the schedule as the schedule information.

[0223] In the elevator / destination floor registration system according to a fifth aspect of the present invention, in any one of the first to fourth aspects, the presentation unit may further cause the presentation device to present information indicating a type of the transportation device.

[0224] A sixth aspect of the present invention relates to a hall destination floor registration system, in any one of the first to fifth aspects above, wherein the presentation device is a display device provided in a destination floor registration device used by the user to make a call for the first hall destination floor, and the presentation unit may cause the display device to display the schedule information.

[0225] The boarding hall destination floor registration system of aspect 7 of the present invention, in any of aspects 1 to 6 above, further includes an tolerance information receiving unit capable of receiving input of tolerance information by the user indicating whether it is acceptable for the user and the mobile device to encounter each other when using the cage of the same vehicle, and when the received tolerance information indicates that it is not acceptable, the allocation unit may perform at least one of the following controls: (1) control to allocate the vehicle so that the user and the mobile device using the cage of the same vehicle when the user boards and disembarks do not encounter each other, and (2) control to allocate the vehicle so that the mobile device does not board the cage of the vehicle while the user is riding.

[0226] In the above-mentioned elevator destination floor registration system according to aspect 7 of the present invention, when the acceptable information received by the acceptable information receiving unit indicates that the acceptable information is unacceptable and the receiving unit receives registration of a third elevator destination floor call, which is a new elevator destination floor call, by the mobile device or the operator of the mobile device during the period from when the elevator is assigned to the first elevator destination floor call to when the mobile device boards the elevator and arrives at the user's destination floor, the allocation unit may perform at least one of the following controls for the third elevator destination floor call: (1) control to allocate the elevator such that the user and the mobile device using the same elevator car when the user boards and disembarks do not encounter each other, and (2) control to allocate the elevator such that the mobile device does not board the elevator car of the elevator while the user is boarding.

[0227] A ninth aspect of the present invention relates to a landing destination floor registration system, as described in claim 1, wherein, in any of the above-mentioned aspects 1 to 8, when the same target elevator is assigned to the first landing destination floor call and the second landing destination floor call, the presentation unit presents the schedule information of the mobile device from the time when the cage of the target elevator departs from the departure floor to the time when the cage arrives at the destination floor where the user plans to disembark.

[0228] A control method for a landing destination floor registration system according to aspect 10 of the present invention includes a reception step of accepting registration of a first landing destination floor call by a user and registration of a second landing destination floor call by a mobile device or an operator of the mobile device, an assignment step of assigning elevator numbers to the first landing destination floor call and the second landing destination floor call, and a presentation step of causing a presentation device to present schedule information indicating the boarding and alighting schedule of the mobile device at at least one of the departure floor, which is a floor where the user boards the car of the target elevator, and the destination floor, which is a floor where the user alights from the car of the target elevator, when the target elevator is assigned to the first landing destination floor call during a period from when a target elevator is assigned to the second landing destination floor call to when the mobile device boards the target elevator and arrives at the destination floor of the mobile device, and when the mobile device and the user encounter each other when boarding and alighting, the mobile device using the same elevator car. [Explanation of symbols]

[0229] 1, 1A Group Management Control Device 2, 2A Destination floor registration device 3. Mobility Devices 4 Elevator control device 5. Elevator 23 Presentation device 51 Basket 111 Reception 112, 112A allocation section 113, 113A presentation section 114 Permitted Information Reception Department 122, 122A Schedule Information 123 Acceptable Information

Claims

1. a reception unit that receives registration of a first hall destination floor call by a user and registration of a second hall destination floor call by a mobile device or an operator of the mobile device; an allocation unit that allocates elevator numbers to the first hall destination floor call and the second hall destination floor call; a presentation unit that causes a presentation device to present schedule information indicating the boarding and disembarking schedule of the mobile device at at least one of a departure floor, which is a floor where the user boards the cage of the target device, and a destination floor, which is a floor where the user disembarks from the cage of the target device, when the target device is assigned to the first boarding hall destination floor call during a period from when the target device is assigned to the second boarding hall destination floor call to when the mobile device boards the target device and arrives at the destination floor of the mobile device, and when the mobile device and the user encounter each other when the user boards and disembarks, the departure floor being the floor where the user boards and disembarks from the cage of the target device.

2. The boarding hall destination floor registration system of claim 1, wherein, when the mobile device that has boarded the cage of the target vehicle that has arrived at the departure floor is scheduled to disembark at the departure floor, the presentation unit presents information indicating the schedule as the schedule information.

3. The boarding hall destination floor registration system of claim 1, wherein, when the mobile device that has boarded the cage of the target vehicle that has arrived at the departure floor does not plan to disembark at the departure floor, the presentation unit presents information indicating the plan as the plan information.

4. 2. The hall / destination floor registration system according to claim 1, wherein, when the transportation device is scheduled to board the cage of the elevator of interest at the departure floor, the presentation unit presents information indicating the schedule as the schedule information.

5. The hall / destination floor registration system according to claim 1 , wherein the presentation unit further causes the presentation device to present information indicating a type of the transportation device.

6. the presentation device is a display device included in a destination floor registration device used by the user to make the first elevator destination floor call, The elevator-hall / destination floor registration system according to claim 1 , wherein the presentation unit causes the display device to display the schedule information.

7. The system further includes an allowance information receiving unit capable of receiving an input of allowance information by the user indicating whether or not it is allowable for the user and the mobile device to encounter each other when using the car of the same elevator, When the accepted permission information indicates non-permission, (1) Control of allocating the car number so that the user does not encounter the transportation device using the car of the same car when the user boards and disembarks; and (2) control to assign the elevator so that the transportation device does not board the elevator car in which the user is riding.

8. When the tolerance information received by the tolerance information receiving unit indicates that the tolerance is not acceptable, and the receiving unit receives registration of a third hall destination floor call, which is a new hall destination floor call, by the mobile device or the operator of the mobile device during a period from when the vehicle is assigned to the first hall destination floor call to when the mobile device boards the vehicle and arrives at the destination floor of the user, The allocation unit, for the third hall destination floor call, (1) Control of allocating the car number so that the user does not encounter the transportation device using the car of the same car when the user boards and disembarks; and (2) control to assign the elevator so that the transportation device does not board the car of the elevator in which the user is riding.

9. The platform destination floor registration system of claim 1, wherein when the same platform destination floor call is assigned to the first platform destination floor call and the second platform destination floor call, the presentation unit presents the schedule information of the mobile device from when the cage of the platform destination floor call departs from the departure floor to when the cage arrives at the destination floor where the user plans to disembark.

10. a receiving step of receiving a registration of a first hall destination floor call by a user and a registration of a second hall destination floor call by a mobile device or an operator of the mobile device; an allocating step of allocating elevator numbers to the first landing destination floor call and the second landing destination floor call; a presentation step of causing a presentation device to present schedule information indicating the boarding and alighting schedule of the mobile device at at least one of a departure floor, which is a floor where the user boards the cage of the target device, and a destination floor, which is a floor where the user disembarks from the cage of the target device, when the target device is assigned to the first boarding hall destination floor call during a period from when the target device is assigned to the second boarding hall destination floor call to when the mobile device boards the target device and arrives at the destination floor of the mobile device, and when the mobile device and the user encounter each other when the user boards and disembarks, the departure floor being a floor where the user boards and disembarks from the cage of the target device.

Images