Elevator control system
Patent Information
- Application Number
- JP2025202842
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2025-11-25
- Publication Date
- 2026-10-16
- Estimated Expiration
- 2045-11-25
AI Technical Summary
【0020】 本発明によれば、乗りかごへの乗車前に行先階の登録を行う必要があるエレベータにおいて、待機状態になった乗りかご内に利用者が取り残された場合でも、当該利用者にとってのエレベータの利便性が損なわれないようにすることが可能になる。
Smart Images

Figure 0007936650000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to an elevator control technology in which a destination floor is registered before a user boards a car.
Background Art
[0002] Patent Document 1 discloses, as an elevator control technology, a technology for assigning a hall call for a user to one selected car (assignment target) from among a plurality of cars included in the elevator, each time the user registers their own destination floor using a destination floor registration device installed at a hall.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of Invention
Problems to be Solved by the Invention
[0004] In an elevator where a destination floor is registered before a user boards a car as described above, a destination button for specifying a destination floor may not be provided inside the car. In an elevator with such a configuration, if a user forgets to alight at their destination floor, and thereafter the car in which the user is riding enters a standby state without stopping again at the user's destination floor, the user will be left stranded inside the car. In such a situation, the user had to temporarily alight from the car that has entered the standby state, and re-register the destination floor at the hall on the floor where they alighted.
[0005] Accordingly, an object of the present invention is to prevent the convenience of the elevator for the user from being impaired even when the user is left stranded in a car that has entered a standby state, in an elevator that requires registration of a destination floor before the user boards the car. [Means for solving the problem]
[0006] The control system according to the present invention is applicable to elevators in which a destination floor registration device is installed on at least one floor, and has the following configuration (Aspect 1). This control system comprises a reader and a control device. The reader is a device that reads the recording medium held by each user and is installed inside the elevator car. The control device, each time a user registers their destination floor in the registration device, assigns a landing call to the elevator car for that user, and disables the reading of the recording medium by the reader until the elevator car enters a standby state, and then enables the reading of the recording medium by the reader when the elevator car enters a standby state.
[0007] According to the above embodiment 1, when the elevator car is in operation, the registration of the destination floor using the reader inside the elevator car is disabled, while when the elevator car is in standby mode, the registration of the destination floor using the reader inside the elevator car is enabled. This makes it possible to restrict the locations where destination floors can be registered to the boarding areas on each floor when the elevator car is in operation. On the other hand, when the elevator car is in standby mode and a passenger is left inside the elevator car, that passenger can register their destination floor again even inside the elevator car by having their recording medium read by the reader inside the elevator car.
[0008] The control system according to Embodiment 1 above may have the following configuration (Embodiment 2). The control system may further include a reader device installed in the registration device that reads the recording medium possessed by each user. Furthermore, each user's recording medium may have readable identification information for distinguishing that user from other users. The control device may then perform the following processing, with the reader device installed in the registration device being designated as the first reader device and the reader device installed inside the elevator car being designated as the second reader device.
[0009] Each time a user registers a destination floor by having their recording medium read by the first reader at the registration device, the control device records the destination floor in the registration information management data, associating it with the user's identification information. Subsequently, when the reading of the recording medium by the second reader is enabled, and any user has their recording medium read by the second reader, the control device uses the user's identification information as focus information and makes a determination (A) to determine whether the focus information matches any of the identification information in the registration information management data. If the control device determines in determination (A) that they "match", it controls the operation of the elevator car using the destination floor associated with the identification information in the registration information management data that matches the focus information.
[0010] According to the above embodiment 2, if a user who has registered their destination floor before boarding the elevator car is left behind in the waiting elevator car, that user can re-register the destination floor they intended to go to when boarding simply by having their recording medium read by the second reader device while inside the elevator car.
[0011] The control system according to the above embodiment 2 may have the following configuration (embodiment 3). If the control device determines in the above determination (A) that there is a "mismatch", it may control the operation of the elevator car using a default floor that is pre-associated with the focus information.
[0012] According to the above embodiment 3, if a user boards a train car without registering their destination floor, and that user is left behind in the train car while it is in standby mode, that user can register their destination floor (=default floor) while inside the train car by having the second reader read their recording medium.
[0013] A control system according to any of the above embodiments 1 to 3 may have the following configuration (embodiment 4). The control system may further include a detection device that detects changes occurring in the elevator car depending on whether or not there are passengers inside the car. The control device may then perform the following processing.
[0014] When a train car enters a standby state, the control device makes a determination (B) based on the detection result of the detection device to determine whether or not there is a user inside the train car. If the control device determines in determination (B) that there is a user inside the train car, it enables the reading of the recording medium by the reading device (second reading device) inside the train car. On the other hand, if the control device determines in determination (B) that there is no user inside the train car, it leaves the reading of the recording medium by the reading device (second reading device) inside the train car disabled.
[0015] According to the above embodiment 4, the reading of the recording medium by the reading device (second reading device) installed inside the elevator car can be enabled only when a user is left inside the elevator car in a standby state.
[0016] A control system according to any of the above embodiments 1 to 4 may have the following configuration (embodiment 5). The control system may further include a door open button installed inside the elevator car. When the elevator car is in a standby state and the door open button is pressed inside the elevator car, the control device may cause the elevator car to move to a predetermined floor without opening the doors, and then open the doors when it arrives at the predetermined floor.
[0017] In this case, a user who is unable to have the recording medium read by the reader (second reader) while the elevator car is in standby mode may be a suspicious person who does not possess a storage medium. Therefore, in the above embodiment 5, if the door open button is pressed while the elevator car is in standby mode, the elevator car is made to move to a designated floor (such as the lobby floor) without opening the doors. This makes it possible to prevent suspicious persons from entering floors other than the designated floor as much as possible.
[0018] The control system according to any one of the above aspects 1 to 4 may have the following configuration (aspect 6). The control system may further include a door open button installed in the car. Then, when the car enters a standby state, the control device may invalidate a door opening operation using the door open button in the car.
[0019] Here, a user who cannot have a recording medium read by a reading device (second reading device) in a car that has entered a standby state may be a suspicious person who does not have the storage medium. Therefore, in the above aspect 6, when the car enters the standby state, the door opening operation using the door open button in the car is invalidated. This makes it possible to confine the suspicious person in the car. Effects of the Invention
[0020] According to the present invention, in an elevator that requires a destination floor to be registered before a user boards the car, even if the user is left behind in the car that has entered a standby state, the convenience of the elevator for the user can be prevented from being impaired. Brief Description of the Drawings
[0021] [Figure 1] It is a conceptual diagram showing the overall configuration of the elevator according to the embodiment. [Figure 2] It is a conceptual diagram illustrating (A) device management data for a registration device, (B) device management data for a second reading device, and (C) user management data used in the embodiment, respectively. [Figure 3] It is a flowchart showing a switching process executed in the embodiment. [Figure 4] It is a flowchart showing a reception process executed in the embodiment and an allocation process executed subsequent to the process. [Figure 5] It is a flowchart showing the process continuing from connector Z2 in Fig. 4 among the reception processes executed in the embodiment, and a registration process executed subsequent to the process. [Figure 6]This is a conceptual diagram illustrating an example of registration information management data used in the first modified example. [Figure 7] This is a flowchart showing a reception process executed in the first modified example and an assignment process executed subsequent to the process. [Figure 8] This is a flowchart showing the process continuing from connector Z2 in FIG. 7 among the reception processes executed in the first modified example, and a registration process executed subsequent to that process. [Figure 9] This is a flowchart showing a switching process executed in the third modified example. [Modes for Carrying Out the Invention]
[0022] [1] Embodiment [1-1] Overall Configuration of Elevator FIG. 1 is a conceptual diagram showing the overall configuration of an elevator according to an embodiment. In the present embodiment, a registration device 1 used for registering a destination floor Fd is installed on each floor of the elevator, and when a user wishes to board a car G, the user needs to register their own destination floor Fd in advance via the registration device 1 installed on the boarding floor. In addition, this elevator includes a plurality of cars G, and further includes a group management control device 2 that centrally manages these cars G. Hereinafter, the configuration of each unit will be specifically described.
[0023] <Registration Device> Each registration device 1 has a configuration in which a first reading device 3A that reads a recording medium (IC card, magnetic card, smartphone, etc.) carried by each user, and a touch panel type display device 4 are installed. Note that the display device 4 may be appropriately modified to a device that allows operations (selection operations and the like) using mechanical buttons while viewing the screen.
[0024] Each user's recording medium has readable identification information Pi (such as a user ID) recorded on it to distinguish that user from other users. When any user has their recording medium read by the first reader 3A in registration device 1, that user's identification information Pi is transmitted to the group management control device 2. At this time, in order for the group management control device 2 to recognize which registration device 1 it is that read the identification information Pi, device information Pd1 to distinguish that registration device 1 from other registration devices 1 is also transmitted to the group management control device 2. As a result, each time a user has their recording medium read by the first reader 3A in registration device 1, a request is made to the group management control device 2 to register the destination floor Fd for that user (registration request).
[0025] The display device 4 shows the destination floor selection screen Fd (described later) and assignment information (car information Pg for the car G that the user should board).
[0026] Furthermore, the registration device 1 may be modified as appropriate to include, in addition to its function as a user interface for registering destination floors, a function that performs authentication using the user's identification information Pi and physically restricts the user's passage (for example, by opening and closing a gate) based on the result of that authentication (such as a security gate). Also, the registration device 1 is not limited to a configuration in which the first reader 3A is integrated with the registration device 1, but may be modified as appropriate to include a configuration in which the first reader 3A is separate from the registration device 1 (for example, a configuration in which the first reader 3A is retrofitted to the registration device 1).
[0027] <Riding car> In this embodiment, each elevator car G is configured without a destination button for specifying the destination floor Fd.
[0028] In elevators like the one in car G, where there are no destination buttons inside, if a user forgets to get off at their destination floor Fd, and the elevator car G then remains in standby mode without stopping again at the user's destination floor Fd, the user will be trapped inside the elevator car G. In such a situation, the user will need to get off the elevator car G, which is in standby mode, and re-register their destination floor Fd using the registration device 1 installed on the floor where they got off.
[0029] Therefore, in an elevator where it is necessary to register the destination floor Fd before boarding the elevator car G, a control system is constructed using some or all of the configuration of the elevator in this embodiment to ensure that the convenience of the elevator is not impaired for the user even if the user is left behind in the elevator car G while it is in standby mode.
[0030] In this embodiment, as one configuration of such a control system, a second reading device 3B that reads the recording medium held by each user is installed inside each elevator car G (see Figure 1). Furthermore, the second reading device 3B is configured to be able to selectively switch its own reading function on or off by a command from the group control device 2, and to notify the user of whether its reading function is set to on or off by a change in the color of a lamp or the like.
[0031] Then, when any user inside the elevator car G has their recording medium read by the second reader 3B (a second reader 3B with the reading function enabled), the user's identification information Pi is transmitted to the group control device 2. At this time, in order to allow the group control device 2 to recognize which second reader 3B read the identification information Pi, device information Pd2, which identifies the second reader 3B from other readers, is also transmitted to the group control device 2. As a result, even when a user inside the elevator car G has their recording medium read by the second reader 3B, the group control device 2 is requested to register the destination floor Fd for that user (registration request).
[0032] <Group Control System> The group control device 2 centrally manages the multiple elevator cars G provided in this embodiment through elevator control devices installed for each elevator car G (see Figure 1).
[0033] Specifically, each time the group management control device 2 receives identification information Pi as a registration request from the registration device 1, it performs the following reception processing (see Figure 4). First, the group management control device 2 authenticates the identification information Pi received from the registration device 1. If the group management control device 2 fails to authenticate the identification information Pi, it rejects the registration request from the registration device 1. On the other hand, if the group management control device 2 succeeds in authenticating the identification information Pi, it accepts the registration request from the registration device 1. In this case, the group management control device 2 enables the user of the registration device 1 that sent the registration request to input (including selection) the destination floor Fd. Then, by the user inputting the destination floor Fd at the registration device 1, the destination floor Fd is registered before boarding the elevator G.
[0034] When a destination floor Fd is entered in the above-mentioned registration device 1 (i.e., when a destination floor Fd is registered), that destination floor Fd is transmitted to the group control device 2, and a request for the allocation of a platform call X for the user is sent to the group control device 2. At this time, in order to allow the group control device 2 to recognize which registration device 1 it is that received the input of the destination floor Fd, the device information Pd1 of that registration device 1 is also transmitted to the group control device 2.
[0035] Each time the group control device 2 receives an assignment request from any of the registration devices 1, it determines the departure floor Fc and destination floor Fd of the user registered by that registration device 1 as a single landing call X, and then determines the elevator car G to which that landing call X will be assigned, and then assigns the landing call X to that elevator car G (assignment process; see Figure 4). Then, at an appropriate timing, the group control device 2 causes the assigned elevator car G to start responding to the landing call X (response process).
[0036] Subsequently, when the assigned elevator car G arrives at the departure floor Fc indicated by the landing call X, the group control device 2 registers the destination floor Fd indicated by the landing call X as the elevator car call Y for the user (registration process). Then, at the appropriate timing, the group control device 2 causes the registered elevator car G to start responding to the elevator car call Y (response process).
[0037] Furthermore, the group control device 2 disables the reading function of the second reading device 3B installed in each elevator car G until the elevator car G enters a standby state, and then switches it to enabled when the elevator car G enters a standby state (switching process; see Figure 3). Here, an elevator car G being in a standby state means that neither a landing call X is assigned to the elevator car G nor a car call Y is registered for the elevator car G, and the elevator car G is stopped with its doors closed on any floor.
[0038] Furthermore, when the group control device 2 receives identification information Pi as a registration request from any of the second readers 3B whose reading function is enabled, it performs the following reception process (see Figure 5). First, the group control device 2 authenticates the identification information Pi received from the second readers 3B. If the group control device 2 fails to authenticate the identification information Pi, it rejects the registration request from the second readers 3B. On the other hand, if the group control device 2 succeeds in authenticating the identification information Pi, it accepts the registration request from the second readers 3B.
[0039] When the group control device 2 receives a registration request from the second reader device 3B, it uses the destination floor Fd (in this embodiment, the default floor Fk described later) associated with the identification information Pi received from the second reader device 3B to register the destination floor Fd as the car call Y for a user who has caused the second reader device 3B to read its recording medium while the car G is in standby mode, and registers the car call Y to the car G (here, this car G is called the "focus car Gw") (registration process; see Figure 5). Immediately after that, the group control device 2 causes the focus car Gw to start responding to the car call Y (response process).
[0040] As a result, if the current stopping floor (the floor where it was stopped in standby mode) of the target elevator Gw is the same as the destination floor Fd indicated by the elevator call Y, the elevator will remain stopped and immediately open its doors to complete its response to the elevator call Y. On the other hand, if the current stopping floor of the target elevator Gw is different from the destination floor Fd indicated by the elevator call Y, the elevator will begin moving to the destination floor Fd, and then open its doors after arriving at the destination floor Fd to complete its response to the elevator call Y.
[0041] Furthermore, if the stopping floor of the car Gw of interest (the floor where it was stopped in standby mode) is the same as the destination floor Fd indicated by the car call Y, the group control device 2 may directly command the car Gw of interest to open its doors at that stopping floor instead of registering the car call Y.
[0042] In terms of its specific configuration, the group control device 2 comprises a storage unit 21 and a control unit 22 (see Figure 1).
[0043] The memory unit 21 is a part composed of memory devices such as ROM and RAM, and stores information necessary for control processing performed by the group control device 2. In this embodiment, such information stored in the memory unit 21 includes device management data Dp, user management data Dq, landing call management data Dx, and car call management data Dy.
[0044] The device management data Dp includes device management data Dp1 for registered device 1 (see Figure 2(A)) and device management data Dp2 for second reader device 3B (see Figure 2(B)). Device management data Dp1 is a database for managing multiple pieces of information related to each registered device 1 by linking them together. Device management data Dp2 is a database for managing multiple pieces of information related to each second reader device 3B by linking them together.
[0045] User management data Dq is a database used to manage multiple pieces of information related to each user who is authorized to use the elevator, linking them together.
[0046] The landing call management data Dx is data used to manage the assignment information (landing call X information) for each elevator car G. The elevator car call management data Dy is data used to manage the registration information (elevator call Y information) for each elevator car G.
[0047] Figure 2(A) is a conceptual diagram illustrating the device management data Dp1 for the registration device 1 used in this embodiment. In the device management data Dp1, the device information Pd1 and installation floor Fs of each registration device 1 are recorded in a manner that is associated with each other.
[0048] As a result, when the group management control device 2 receives device information Pd1 along with identification information Pi from the registration device 1, it can identify the installation floor Fs of the registration device 1 (the registration device 1 from which the identification information Pi was read) from the device information Pd1. In this embodiment, the installation floor Fs of the registration device 1 is used as the departure floor Fc (boarding floor) of the user who caused the first reader device 3A of the registration device 1 to read its recording medium.
[0049] Figure 2(B) is a conceptual diagram illustrating the device management data Dp2 for the second reader device 3B used in this embodiment. In the device management data Dp2, for each second reader device 3B, the device information Pd2 of the reader device and the car information Pg for identifying the elevator car G on which the reader device is installed from other cars are recorded in a manner that is associated with each other.
[0050] As a result, the group control device 2 can identify the second reading device 3B installed inside each elevator car G from the elevator car information Pg of that elevator car G. Therefore, the group control device 2 can identify the second reading device 3B installed inside each elevator car G and control the enable / disable of the reading function according to whether or not each elevator car G is in a standby state. Furthermore, when the group control device 2 receives device information Pd2 along with identification information Pi from the second reading device 3B, it can identify the elevator car G in which the second reading device 3B is installed (the elevator car G in which the identification information Pi was read) from the device information Pd2. Therefore, when the group control device 2 registers the destination floor Fd associated with the identification information Pi received from the second reading device 3B as the elevator car call Y, it can identify the elevator car G to which it should be registered.
[0051] Figure 2(C) is a conceptual diagram illustrating the user management data Dq used in this embodiment. In the user management data Dq, for each user permitted to use the elevator, the user's identification information Pi and the permitted disembarking floors (default floor Fk and other permitted disembarking floors Fm) are recorded in a manner that they are associated with each other. In this embodiment, one of the permitted disembarking floors for the user is set as the default floor Fk.
[0052] As a result, when the group management control device 2 receives identification information Pi from the registration device 1 or the second reader device 3B, it can perform authentication of the identification information Pi by comparing it with the identification information Pi in the user management data Dq. Furthermore, if authentication of the identification information Pi is successful, it becomes possible to identify the disembarking floor permitted for the user identified by the identification information Pi.
[0053] The control unit 22 is responsible for executing the control processes performed by the group management control device 2 (including reception processing, allocation processing, registration processing, response processing, and switching processing). Specifically, the control unit 22 is composed of processing devices such as a CPU and an MPU, and executes the control processes it is responsible for using software by running a control program installed in the group management control device 2. Before installation in the group management control device 2, this control program may be stored in a readable state on a portable storage medium (e.g., flash memory) or in a downloadable state on a server. Furthermore, some of the control processes performed by the group management control device 2 may be performed on an elevator server located in the cloud. In addition, the control processes performed by the group management control device 2 are not limited to being implemented in software by executing a program, but may also be implemented in hardware by processing circuits built into the group management control device 2.
[0054] [1-2] Control processes performed in the elevator [1-2-1] Switching process performed by the group control unit Figure 3 is a flowchart showing the switching process performed in this embodiment. The group control device 2 performs this switching process for each elevator car G. A detailed explanation follows below.
[0055] In the switching process, the group control device 2 determines whether the elevator car G targeted in that process (hereinafter referred to as "target car Gt") is in a standby state (step S101). Specifically, the group control device 2 makes the determination in step S101 based on the current status of landing call X assignments and car call Y registrations for the target car Gt, as well as the operating status of the target car Gt. Here, a target car Gt being in a standby state means that neither landing call X nor car call Y registrations exist for the target car Gt, and that the target car Gt is stopped with its doors closed on any floor.
[0056] If the group control device 2 determines in step S101 that it is "not in standby mode (No)", it disables the reading function of the second reader device 3B installed in the target cage Gt (step S102A). On the other hand, if the group control device 2 determines in step S101 that it is "in standby mode (Yes)", it enables the reading function of the second reader device 3B installed in the target cage Gt (step S102B). After that, the group control device 2 returns to step S101 and repeatedly executes the process from step S101.
[0057] In this way, the group control device 2 disables the reading function of the second reading device 3B installed in the target cage Gt until the target cage Gt enters a standby state, and then switches it to enabled when the target cage Gt enters a standby state.
[0058] [1-2-2] Reception processing, assignment processing, and registration processing performed by the group management control device Figures 4 and 5 are flowcharts showing the reception process performed in this embodiment, as well as the assignment and registration processes performed subsequently. These processes begin with the reception process each time the group control device 2 receives a registration request from the registration device 1 or the second reading device 3B.
[0059] Here, the information received by the group management control device 2 each time a registration request is made is collectively referred to as "received information Pr". Specifically, if the registration request originates from the registration device 1, this received information Pr will consist of a set of information including identification information Pi and device information Pd1, and if the registration request originates from the second reader device 3B, it will consist of a set of information including identification information Pi and device information Pd2.
[0060] When the reception process begins, the group management control device 2 determines whether the received registration request originated from the registration device 1 or the second reading device 3B (in this embodiment, the second reading device 3B with the reading function enabled) by determining which of the device information Pd1 or device information Pd2 is included in the received information Pr (step S200).
[0061] If the group control device 2 determines in step S200 that "device information Pd1" is included, it can determine that the received registration request originated from registration device 1. In this case, the group control device 2 executes the following process.
[0062] The group management control device 2 first performs authentication on the identification information Pi (here, this identification information Pi is called "focus information Piw") in the received information Pr in order to determine whether the user identified by the identification information Pi is authorized to use the elevator (step S201). Specifically, the group management control device 2 compares the focus information Piw with the identification information Pi in the user management data Dq (see Figure 2(C)).
[0063] If the group management control device 2 "fails" to authenticate in step S201, it rejects the registration request from the registration device 1 (step S210). In this case, the group management control device 2 notifies the user of the authentication failure through the registration device 1 that sent the registration request (step S211). After that, the group management control device 2 terminates the control process.
[0064] On the other hand, if the group management control device 2 "succeeds" in authentication in step S201, it accepts a registration request from the registration device 1 (step S202). In this case, the group management control device 2 instructs the registration device 1 that sent the registration request (the registration device 1 identified by the device information Pd1 in the received information Pr; here, this registration device 1 is referred to as the "target registration device 1w") to display the destination floor Fd selection screen on the display device 4 (step S203). Specifically, the group management control device 2 uses the user management data Dq to extract the default floor Fk and the disembarkation permission floor Fm that are associated with the identification information Piw among the identification information Pi recorded therein that matches the target information Piw, and then instructs the target registration device 1w to display a selection screen targeting those floors.
[0065] Subsequently, if the destination floor Fd is selected on the selection screen in the target registration device 1w (i.e., if the destination floor Fd is registered), the destination floor Fd is transmitted to the group control device 2, thereby sending a request to the group control device 2 to assign a platform call X for the user. At this time, in order to allow the group control device 2 to recognize which registration device 1 it is that received the input of the destination floor Fd, the device information Pd1 of that registration device 1 is also transmitted to the group control device 2.
[0066] After step S203, the group management control device 2 executes the following assignment process.
[0067] The group control device 2 first determines whether or not it has received an assignment request (including the destination floor Fd selected on the selection screen) from the focus registration device 1w (step S301). The group control device 2 repeatedly executes step S301 until it can determine that it has received the request (Yes).
[0068] If the group control device 2 determines in step S301 that it has "received (Yes)" an assignment request from the focus registration device 1w, it performs the assignment of a landing call X in accordance with that request (step S302). Specifically, the group control device 2 uses the device management data Dp1 (see Figure 2(A)) to find a device information Pd1 that matches the device information Pd1 of the focus registration device 1w, and then extracts the corresponding installation floor Fs. The group control device 2 then sets the installation floor Fs as the user's departure floor Fc, and determines that the departure floor Fc and the destination floor Fd (the destination floor Fd selected by the user) received in the assignment request from the focus registration device 1w as the landing call X for that user. Furthermore, the group control device 2 determines the elevator car G to which the landing call X will be assigned. Then, the group control device 2 assigns the landing call X to the elevator car G. Then, the group control device 2 records the assignment information (the information of the landing call X mentioned above) that was assigned in step S302 into the landing call management data Dx.
[0069] After step S302, the group control device 2 notifies the user of the allocation information (in this case, the car information Pg of the assigned car G) performed in step S302 via the focus registration device 1w (step S303). After that, the group control device 2 terminates the control process.
[0070] On the other hand, if the group control device 2 determines in step S200 that "device information Pd2" is included, it can determine that the received registration request is from the second reading device 3B (in this embodiment, the second reading device 3B with the reading function enabled). In this case, the group control device 2 performs the following processing (see Figure 5).
[0071] The group management control device 2 first performs authentication on the identification information Pi (here, this identification information Pi is called "focus information Piw") in the received information Pr in order to determine whether the user identified by the identification information Pi is authorized to use the elevator (step S221). Specifically, the group management control device 2 compares the focus information Piw with the identification information Pi in the user management data Dq (see Figure 2(C)).
[0072] If the group control device 2 "fails" to authenticate in step S221, it rejects the registration request from the second reader device 3B (step S230). In this case, the group control device 2 notifies the user of the authentication failure through a lamp or buzzer provided by the second reader device 3B (step S231). After that, the group control device 2 terminates the control process.
[0073] On the other hand, if the group control device 2 "succeeds" in authentication in step S221, it accepts a registration request from the second reader device 3B (step S222). In this case, the group control device 2 executes the following registration process.
[0074] The group control device 2 first identifies the elevator car G on which the second reading device 3B, identified by the device information Pd2 in the received information Pr, is installed (step S401). Here, the elevator car G identified in step S401 (an elevator car G in standby mode) is called the "focused elevator car Gw". Specifically, the group control device 2 uses the device management data Dp2 to find a device information Pd2 recorded therein that matches the device information Pd2 in the received information Pr, and then identifies the elevator car G identified by the elevator information Pg associated with that device information Pd2 as the "focused elevator car Gw".
[0075] Next, the group management control device 2 uses the user management data Dq to extract the default floor Fk that matches the focus information Piw among the identification information Pi recorded therein (step S402). Then, the group management control device 2 sets the default floor Fk as the destination floor Fd and registers the destination floor Fd as a new car call Y for the user who caused the second reader device 3B to read its recording medium within the focus car Gw, and registers the car call Y with the focus car Gw (step S403). Immediately after that, the group management control device 2 causes the focus car Gw to start responding to the car call Y (step S404. response processing). Then, the group management control device 2 terminates the control processing.
[0076] As a result, if the current stopping floor (the floor where it was stopped in standby mode) of the target elevator Gw is the same as the destination floor Fd indicated by the elevator call Y, the elevator will remain stopped and immediately open its doors to complete its response to the elevator call Y. On the other hand, if the current stopping floor of the target elevator Gw is different from the destination floor Fd indicated by the elevator call Y, the elevator will begin moving to the destination floor Fd, and then open its doors after arriving at the destination floor Fd to complete its response to the elevator call Y.
[0077] Furthermore, in step S403, the group control device 2 may control the operation of the car Gw of interest using the default floor Fk extracted in step S402 as follows: If the default floor Fk extracted in step S402 matches the stopping floor of the car Gw of interest (the floor where it is stopped in standby mode), the group control device 2 may directly command the car Gw of interest to open the doors at that stopping floor instead of registering the car call Y. The group control device 2 may then register the car call Y for the car Gw of interest only if the default floor Fk is different from the stopping floor of the car Gw of interest.
[0078] According to this embodiment, when the elevator car G is in operation, the registration of the destination floor Fd using the second reader 3B inside the elevator car G is disabled, while when the elevator car G is in standby mode, the registration of the destination floor Fd using the second reader 3B inside the elevator car G is enabled. This makes it possible to restrict the locations where the destination floor Fd can be registered to the landings on each floor when the elevator car G is in operation. On the other hand, when the elevator car G is in standby mode, if a passenger is left inside the elevator car G, that passenger can register the destination floor Fd (default floor Fk in this embodiment) again even inside the elevator car G by having the second reader 3B read their recording medium.
[0079] Therefore, in elevators where it is necessary to register the destination floor Fd before boarding elevator car G, it becomes possible to ensure that the convenience of the elevator for the user is not compromised even if the user is left behind inside elevator car G while it is in standby mode.
[0080] [2] Variant [2-1] First variation In the embodiment described above, the group control device 2 may have the following configuration.
[0081] In this modified example, registration information management data Dr is stored in the storage unit 21 as additional information necessary for the control processing performed by the group management control device 2. Here, registration information management data Dr is data for managing the destination floor Fd information registered by the registration device 1.
[0082] Figure 6 is a conceptual diagram illustrating the registration information management data Dr used in the first modified example. In the registration information management data Dr, each time a user registers a destination floor Fd in the registration device 1 (specifically, each time the group management control device 2 receives a registration request from the registration device 1), that destination floor Fd is recorded in association with the user's identification information Pi. Furthermore, each time the same user registers a destination floor Fd again in the registration device 1, the destination floor Fd associated with the user's identification information Pi in the registration information management data Dr is updated with the destination floor Fd registered at that time.
[0083] Figures 7 and 8 are flowcharts showing the reception process performed in the first modified example, as well as the assignment and registration processes performed following that process.
[0084] In this modified example, if the group management control device 2 determines in step S301 (see Figure 7) that it has "received (Yes)" an assignment request from the focus registration device 1w, it records the destination floor Fd of the user (the destination floor Fd selected by the user) received in that assignment request in the registration information management data Dr, associating it with the focus information Piw (the user's identification information Pi) (step S310). Subsequently, the group management control device 2 executes the processing from step S302.
[0085] Furthermore, if the group control device 2 receives a registration request from the second reader 3B in step S222 (see Figure 8), it executes the following registration process.
[0086] After step S401 is executed, the group management control device 2 first determines whether the user who made the registration request (i.e., the user who had the second reading device 3B read their recording medium) is the same user who registered the destination floor Fd with the registration device 1 before boarding the target car Gw, by checking whether the target information Piw (the user's identification information Pi) matches any of the identification information Pi in the registration information management data Dr (step S410).
[0087] If the group control device 2 determines in step S410 that there is a "match (Yes)", it can use that determination to determine that the user who made the registration request is a user who registered their destination floor Fd with the registration device 1 before boarding the target car Gw, in other words, a user whose destination floor Fd is recorded in the registration information management data Dr. In this case, the group control device 2 uses the registration information management data Dr to extract the destination floor Fd that is associated with the identification information Piw among the identification information Pi recorded therein that matches the target information Piw (step S411). Then, the group control device 2 takes the destination floor Fd extracted in step S411 as a new car call Y for the user who had the second reading device 3B read its recording medium inside the target car Gw, and registers that car call Y to the target car Gw (step S412). Immediately afterward, the group control device 2 causes the target cage Gw to begin responding to the cage call Y (step S404. response processing). Then, the group control device 2 terminates the control processing.
[0088] As a result, if the current stopping floor (the floor where it was stopped in standby mode) of the target elevator Gw is the same as the destination floor Fd indicated by the elevator call Y, the elevator will remain stopped and immediately open its doors to complete its response to the elevator call Y. On the other hand, if the current stopping floor of the target elevator Gw is different from the destination floor Fd indicated by the elevator call Y, the elevator will begin moving to the destination floor Fd, and then open its doors after arriving at the destination floor Fd to complete its response to the elevator call Y.
[0089] Furthermore, in step S412, the group control device 2 may control the operation of the car Gw of interest using the destination floor Fd extracted in step S411 as follows: If the destination floor Fd extracted in step S411 matches the stopping floor of the car Gw of interest (the floor where it is stopped in standby mode), the group control device 2 may directly command the car Gw of interest to open the doors at that stopping floor instead of registering the car call Y. The group control device 2 may then register the car call Y for the car Gw of interest only if the destination floor Fd is different from the stopping floor of the car Gw of interest.
[0090] On the other hand, if the group control device 2 determines in step S410 that there is a "no match", it can use that determination to determine that the user who made the registration request is a user who did not register their destination floor Fd with the registration device 1 before boarding the target car Gw (a user who boarded the target car Gw without registering their destination floor Fd), in other words, a user whose destination floor Fd is not recorded in the registration information management data Dr. In this case, the group control device 2 executes steps S402 and S403 to register the car call Y for the target car Gw using the user's default floor Fk.
[0091] According to the first modified example, if a user who has registered their destination floor Fd before boarding elevator G is left behind inside elevator G while it is in a waiting state, that user can re-register the destination floor Fd they were heading to when they boarded simply by having their recording medium read by the second reader device 3B inside elevator G (focused elevator Gw).
[0092] Furthermore, if a passenger boards elevator car G without registering their destination floor Fd, and is left behind inside elevator car G while it is in standby mode, that passenger can register their destination floor Fd (=default floor Fk) inside elevator car G by having the second reader device 3B read their recording medium.
[0093] [2-2] Second variation In both the above-described embodiment and the first modified example, the group control device 2 may, instead of performing a switching process for each elevator car G (i.e., instead of having the second reader device 3B of each elevator car G switch between enabling and disabling the reading function), keep the second reader device 3B of each elevator car G in a state where it can always read the recording medium, and determine whether to enable or disable the reading of the recording medium by the second reader device 3B during the reception process (i.e., in internal processing by the group control device 2).
[0094] [2-3] Third variation In both the above-described embodiment and the first modification, the elevator may have the following configuration.
[0095] In this modified elevator, each elevator car G is equipped with a detection device 5 (not shown) that detects changes occurring in the elevator car G depending on whether or not there are passengers inside the car. As an example, the detection device 5 is a load cell that detects the load inside the elevator car G. As another example, the detection device 5 is a camera that takes pictures inside the elevator car G.
[0096] Figure 9 is a flowchart showing the switching process performed in the third modified example.
[0097] In this modified example, if the group control device 2 determines in step S101 that the target car Gt is in a "standby state (Yes)", it does not immediately activate the reading function of the second reading device 3B installed inside the target car Gt. Instead, it first determines whether or not there is a user inside the target car Gt based on the detection result of the detection device 5 installed inside the target car Gt (step S110).
[0098] Then, if the group control device 2 determines in step S110 that "there is a user (Yes)", it enables the reading function of the second reader device 3B installed in the target car Gt (step S102B). On the other hand, if the group control device 2 determines in step S110 that "there is no user (No)", it leaves the reading function of the second reader device 3B installed in the target car Gt disabled (step S102B).
[0099] According to the third modification, the reading function of the second reader device 3B installed inside the elevator car G can be activated only when a passenger is left inside the elevator car G while it is in standby mode.
[0100] [2-4] Fourth variation In the embodiments described above, the elevator may have the following configuration. The configuration described below can also be applied to the first to third modifications.
[0101] In this modified elevator configuration, each elevator car G is equipped with a door open button 6 (not shown) inside the car. The group control device 2, when any elevator car G is in standby mode and the second reading device 3B installed inside that elevator car G is activated, but the recording medium is not read by the second reading device 3B, and the door open button 6 is pressed inside the elevator car G, will cause the elevator car G to move to a predetermined floor (for example, the lobby floor) without opening its doors, and then open its doors when it arrives at the predetermined floor.
[0102] In this case, a user who is unable to have the recording medium read by the second reader 3B while the elevator car G is in standby mode may be a suspicious person who does not possess a storage medium. Therefore, in this modified example, when the door open button 6 is pressed while the elevator car G is in standby mode, the elevator car G is instructed to move to a designated floor (such as the lobby floor) without opening the doors. This makes it possible to prevent suspicious persons from entering floors other than the designated floor as much as possible.
[0103] [2-5] Fifth variation In the fourth modified example described above, the group control device 2 may disable the door opening operation using the door opening button 6 inside any of the elevator cars G when the elevator car G is in standby mode and the second reading device 3B installed inside that elevator car G is enabled.
[0104] According to the fifth modification, it becomes possible to confine a suspicious person inside the elevator car G.
[0105] [2-6] Sixth variation In the embodiment described above, the elevator may be modified as appropriate so that a second reading device 3B is installed in each elevator car G, while a first reading device 3A is not installed in each registration device 1, and the destination floor Fd is registered by manual input (including pressing a button) before boarding.
[0106] The above-described embodiments and modifications should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims, rather than by the above-described embodiments and modifications. Furthermore, the scope of the present invention is intended to include all modifications within the meaning and scope equivalent to the claims.
[0107] From the embodiments and modifications described above, the subject matter of the invention may not be limited to a control system, but may also be a part or all of the control processing (including the control method corresponding to the control processing) or program executed by the control system. Furthermore, a part or all of the elevator (such as the group control device 2, including the elevator server), or even a part or all of the control processing or program executed by the elevator (such as the control processing or program executed by the group control device 2), may be extracted as the subject matter of the invention. [Explanation of Symbols]
[0108] 1. Registered device Group 2 Control System 3A First Reader 3B 2nd reader 4 Display device 5. Detection device 6. Door Open Button G Car X boarding area call Y Calling 1w Focus Registration Device 21 Memory section 22 Control Unit Dp Device Management Data Dq User Management Data Dr. Registration Information Management Data Dx boarding area call management data Dy Basket Call Management Data FC Departure Floor Fd Destination Floor Fk Default Floor Fm Disembarkation Permit Floor Fs installation floor Gt Target Cart GW (Golden Week) Featured Basket Pg Shopping Cart Information Pi identification information Pr Received Information Dp1, Dp2 Device Management Data Pd1, Pd2 Device Information Piw Featured Information
Claims
1. A control system applicable to elevators in which a destination floor registration device is installed on at least one floor, A reader device installed inside the elevator car that reads recording media held by each user, Each time the user registers their destination floor in the registration device, a platform call is assigned to the elevator car for that user, and the reading of the recording medium by the reading device is disabled until the elevator car enters a standby state. Subsequently, when the elevator car enters a standby state, the reading of the recording medium by the reading device is enabled. An elevator control system equipped with [a specific feature].
2. The device further comprises a reading device installed in the registration device, which reads recording media owned by each user, Each user's recording medium has readable identification information recorded on it to distinguish that user from other users. The reading device installed in the registration device is designated as the first reading device, and the reading device installed inside the elevator car is designated as the second reading device. The control device is In the registration device, each time the user has their recording medium read by the first reader and registers the destination floor, the destination floor is recorded in the registration information management data in association with the user's identification information. Subsequently, when the reading of the recording medium by the second reader is enabled, if any user has the second reader read their own recording medium, the user's identification information is used as the focus information, and a determination (A) is made as to whether the focus information matches any of the identification information in the registration information management data. If the judgment (A) determines that there is a match, the elevator control system according to claim 1 controls the operation of the elevator car using the destination floor associated with the identification information in the registered information management data that matches the information of interest.
3. The elevator control system according to claim 2, wherein if the control device determines in the judgment (A) that there is no match, it controls the operation of the elevator car using a default floor that is pre-associated with the focus information.
4. The system further includes a detection device that detects changes occurring in the elevator car depending on whether or not there are passengers inside the elevator car, The control device is When the aforementioned elevator car enters a standby state, a determination (B) is made based on the detection result of the detection device to determine whether or not there is a user inside the elevator car. An elevator control system according to any one of claims 1 to 3, wherein if the judgment (B) determines that there is a user inside the elevator car, the reading of the recording medium by the reading device inside the elevator car is enabled, and on the other hand, if the judgment (B) determines that there is no user inside the elevator car, the reading of the recording medium by the reading device inside the elevator car is left disabled.
5. The elevator car is further equipped with a door open button, The control device, when the elevator car is in a standby state and the door open button is pressed inside the elevator car, causes the elevator car to move to a predetermined floor without opening its doors, and then opens its doors when it arrives at the predetermined floor, as described in any one of claims 1 to 3.
6. The elevator car is further equipped with a door open button, The elevator control system according to any one of claims 1 to 3, wherein the control device disables the operation of opening the doors using the door open button inside the elevator car when the elevator car is in a standby state.
Citation Information
Patent Citations
Elevator device
JP2010184777A
Group control system of elevator
JP2016055976A
Elevator group management system
JP2018111585A
Elevator group management system
JP2019156577A