JP6915643B2 - Elevator control system - Google Patents

Description

The present invention relates to an elevator control technique capable of performing call registration based on user identification information.

Elevator control technology uses a destination floor registration device installed at the landing to accept landing calls from users, and assigns the landing calls to any one of the cars in consideration of transportation efficiency and security. There is something to register. In such a control technology, call registration is usually performed for each user. Therefore, even if multiple users want to act in a group, they are not always able to board the same car because they are assigned individual cars when using the elevator. In some cases, it was necessary to act individually up to the destination (destination floor) in the elevator. For this reason, it was inconvenient for users who acted in groups.

Therefore, a technique has been proposed in which the number of users can be input by the destination floor registration device, and when the number of users entered by the destination floor registration device is received together with the boarding call, the call registration is performed using the number of users. (See, for example, Patent Document 1).

Patent No. 5087281

However, if the destination floor registration device enables input of the number of users, there is a risk that a malicious user may input a larger number of users than the actual number of users when calling the landing. If an unnecessarily large number of people are registered for calling, the elevator must actually be operated by a smaller number of people than the number of people registered for calling, which reduces the operating efficiency of the elevator.

Therefore, an object of the present invention is to provide a control system capable of monitoring a landing call made by a user in an elevator.

The control system according to the present invention relays a control device that controls an elevator, a reading device that reads user identification information, and management information corresponding to the identification information read by the reading device, and transmits the management information to the control device. It is equipped with a relay device. Then, when the control device receives the management information from the relay device, the control device calls and registers the management information as a target.

According to the above control system, the control device can manage the history of call registration performed for each landing call of the user by associating it with the management information.

The control system may further include a registration device having a first reading device, which is one of the reading devices. In this configuration, when the identification information is read by the first reading device, the relay device may also transmit the management information corresponding to the identification information to the registration device. Further, the registration device may enable input of the number of users when the management information is received from the relay device, and may transmit the input number of users to the control device together with the management information received from the relay device. Further, when the control device also receives the same management information as the management information received from the relay device from the registration device, the control device may perform call registration using the number of users transmitted from the registration device together with the management information. According to this configuration, the control device can reflect the number of users input by the registration device in the call registration.

In the control system, the control device may broadcast information related to the call registration together with the management information that is the target of the call registration. According to this configuration, using the management information as a clue, it is possible to have only the device that requires the above information related to the call registration acquire the information.

The control system may be applied to an elevator equipped with a regulatory device that regulates entry into the landing. In this configuration, the regulator may have a second reader, which is one of the readers. Further, when the identification information is read by either the first reading device or the second reading device, the relay device receives the management information corresponding to the identification information, and the identification information is the first reading device and the second reading device. It may be transmitted to the control device together with the attribute information indicating which of the reading devices has read it.

According to the above configuration, when the control device calls and registers the management information, the type of the device that reads the identification information corresponding to the management information (that is, the type of the regulation device or the registration device). Is it?) Can be specified from the attribute information. Then, when the information on the number of users is not transmitted from the regulation device and the attribute information corresponds to the regulation device, the control device thereby determines the number of users before executing the call registration. It can be determined that there is no need to receive. Therefore, when the user is permitted to pass through the regulation device, the control device can be immediately called and registered.

In the above control system, the control device may have destination floor management data in which destination floors are associated with each management information. Further, when the control device receives the management information from the relay device, the control device may read the destination floor associated with the management information from the destination floor management data, and perform call registration using the read destination floor. .. By giving the information of the destination floor to the control device in this way, the amount of data transmitted from the relay device to the control device can be reduced, and the processing speed can be increased.

According to the present invention, it is possible to monitor a landing call made by a user in an elevator.

It is a conceptual diagram which showed the whole structure of the elevator to which the control system which concerns on embodiment is applied. It is a conceptual diagram which showed the structure of the elevator landing on each floor. It is a flowchart which showed the authentication process executed by a security server. It is a conceptual diagram which showed an example of (A) apparatus management data and (B) an example of medium management data used in an embodiment, respectively. It is a conceptual diagram which showed an example of the installation floor management data used in an embodiment. It is a conceptual diagram which showed an example of (A) destination floor management data and (B) an example of history management data used in the embodiment, respectively. It is a flowchart which showed the relay process executed in an embodiment. It is a flowchart which showed the destination floor registration process which is executed in embodiment. It is a conceptual diagram which showed an example of the number of people input screen. It is a flowchart which showed the call registration process which is executed in embodiment. It is a conceptual diagram which showed an example of the attribute management data used in the 4th modification. It is a flowchart which showed the relay process executed in the 4th modification. It is a flowchart which showed the destination floor registration process executed in 4th modification. It is a flowchart which showed the call registration process executed in the 4th modification.

[1] Configuration of Elevator and Control System FIG. 1 is a conceptual diagram showing the overall configuration of an elevator to which the control system according to the embodiment is applied. Further, FIG. 2 is a conceptual diagram showing the configuration of the elevator landing H on each floor. In the present embodiment, the elevator includes three car 100s, two control devices 101A installed on a specific floor (lobby floor, etc.) of the building, a destination floor registration device 101B installed at the landing H on each floor, and the like. It includes a security server 102, a relay device 103, an elevator control device 104, and a group management control device 105. Further, device information Pd for identifying them is set in the regulation device 101A and the destination floor registration device 101B.

In the present embodiment, the elevator control system includes a destination floor registration device 101B installed at the landing H on each floor, a relay device 103, an elevator control device 104, and a group management control device 105. .. In addition, each part configuration of the control system of the present embodiment described below includes an elevator having a plurality of car 100s not limited to three and a regulation device 101A having a number (including one) not limited to two. It can also be applied to elevators equipped with it.

<Regulatory device>
The regulation device 101A is a device that regulates the entry of the elevator to the landing H on a specific floor such as a security gate, and is a reader 1A that reads information from a recording medium Q (IC card, magnetic card, etc.) possessed by the user. It also has a display device 2A for displaying information such as a car 100 on which the user should board. Here, the recording medium Q records the identification information Pi (unique information for identifying the recording medium Q, such as a unique ID) of the user who possesses the recording medium Q, and the reading device 1A identifies the information from the recording medium Q. Read information Pi.

The reading method of the recording medium Q by the reading device 1A may be a contact type or a non-contact type that reads information by short-range communication such as NFC (Near Field Communication). Not limited. Further, the recording medium Q is not limited to a card-shaped one, but may be a stick-shaped one or a chip-shaped one. Further, a portable information terminal such as a smartphone capable of short-range communication (NFC or the like) with the reading device 1A may be used as the recording medium Q.

When the reading device 1A reads the identification information Pi, the regulation device 101A transmits the identification information Pi together with the device information Pd of the regulation device 101A to the security server 102 (see FIG. 1). The regulation device 101A may transmit the device information of the reading device 1A that has read the identification information Pi to the security server 102 as the device information Pd.

Then, the authentication (authentication process) of the identification information Pi is executed by the security server 102, and when the authentication is successful, the user is allowed to pass through the regulation device 101A. That is, the determination as to whether or not to allow the user to pass through the regulation device 101A is made based on the user's identification information Pi.

Further, when the authentication of the identification information Pi on the security server 102 is successful, the management information Pj (for example, a serial number attached to the IC card) corresponding to the identification information Pi on a one-to-one basis is the security server. It is transmitted from 102 to the group management control device 105 via the relay device 103 (relay process). Then, the call registration (call registration process) for the management information Pj is executed by the group management control device 105 (call registration process). Specifically, the group management control device 105 uses the information required for call registration (information such as the destination floor Fd corresponding to the management information Pj) as one landing call, and uses the landing call as the elevator transportation efficiency and the like. Assign to any one of a plurality of car 100s in consideration.

<Destination floor registration device>
The destination floor registration device 101B includes a destination floor registration device 101Bp installed at the elevator landing H on a specific floor and a destination floor registration device 101Bq installed at the elevator landing H on each floor (other floor) other than the specific floor. ,including. In the present embodiment, the destination floor registration device 101Bp may be used when the user misses the car 100 assigned when passing through the regulation device 101A and calls the landing again, or when the destination floor is set to another floor (to the user). It is used when changing to another permitted destination floor). Further, the destination floor registration device 101Bq is used when a user calls a landing from each floor other than a specific floor, or when the number of users Nr or the like is input when calling a landing.

Each of the destination floor registration devices 101B (101Bp and 101Bq) has a reading device 1B for reading information from the recording medium Q possessed by the user, and a display device 2B with an operation function. In the present embodiment, the display device 2B is a display panel with a touch panel. The display device 2B may be provided with a function of performing a selection operation or the like with a button. The method of reading the recording medium Q by the reading device 1B is the same as that of the reading device 1A described above.

When the reading device 1B reads the identification information Pi, the destination floor registration device 101B transmits the identification information Pi together with the device information Pd of the destination floor registration device 101B to the security server 102 (see FIG. 1). The destination floor registration device 101B may transmit the device information of the reading device 1B that has read the identification information Pi to the security server 102 as the device information Pd.

Then, when the authentication (authentication process) of the identification information Pi is executed on the security server 102 and the authentication is successful, the destination floor registration device 101B can perform operations such as changing the destination floor and inputting the number of users. Then, the information input in the operation is transmitted to the group management control device 105 (destination floor registration process).

The processing unit for performing such destination floor registration processing may be configured by hardware by constructing a circuit in the destination floor registration device 101B, or a CPU (Central Processing Unit) included in the destination floor registration device 101B. ) Etc. may be configured by software by causing a processing device such as) to execute a program. Then, such a program may be stored in a portable storage device (for example, a flash memory or the like) in a readable state, or stored in a downloadable state on another server or the like, and the downloaded program is the destination. It may be stored in the storage unit (not shown) of the floor registration device 101B. The details of the destination floor registration process executed by the destination floor registration device 101Bq will be described later.

<Security server>
The security server 102 authenticates the identification information Pi transmitted from the regulation device 101A and the destination floor registration device 101B, and only when the authentication is successful, the user can pass through the regulation device 101A or operate the destination floor registration device 101B. Maintain high security by allowing for (authentication processing). The details of the authentication process will be described below.

FIG. 3 is a flowchart showing the authentication process executed by the security server 102. The authentication process is started when the security server 102 receives the identification information Pi from the regulation device 101A or the destination floor registration device 101B. When the authentication process is started, the security server 102 authenticates the received identification information Pi (step S101 in FIG. 3).

When the security server 102 succeeds in authenticating the identification information Pi in step S101, the security server 102 causes the device (regulatory device 101A or destination floor registration device 101B) that is the source of the identification information Pi to execute an operation according to the authentication result. Therefore, the device that is the transmission source is specified based on the device information Pd transmitted together with the identification information Pi (step S102 in FIG. 3).

Specifically, the security server 102 has device management data D1. FIG. 4A is a conceptual diagram showing an example of the device management data D1 used in the present embodiment. In the device management data D1, for each device information Pd, the device address Pa (IP address, etc.) used for transmitting information to the device (regulatory device 101A or destination floor registration device 101B) identified by the device information Pd, and Attribute information Pb for specifying the type of the device (that is, information for specifying whether the type is the regulation device 101A or the destination floor registration device 101B) is associated with the attribute information Pb. In FIG. 4A, “0” and “1” are used as the attribute information Pb in order to distinguish between the regulation device 101A and the destination floor registration device 101B.

Then, the security server 102 reads the device address Pa and the attribute information Pb corresponding to the received device information Pd from the device management data D1 to read the device (regulatory device 101A or destination floor registration device) that is the source of the identification information Pi. 101B) is specified. At this time, the attribute information Pb was read by whether the identification information Pi was read by the regulation device 101A (reading device 1A) or the destination floor registration device 101B (reading device 1B) (that is, by what type of device). ) Is used as information.

After that, the security server 102 indicates whether the attribute information Pb read from the device management data D1 in step S102 corresponds to the regulation device 101A (Pb = 0) or corresponds to the destination floor registration device 101B (Pb). = 1) is determined (step S103 in FIG. 3).

Then, when the security server 102 is determined in step S103 to be "corresponding to the regulation device 101A (Pb = 0)", the security server 102 is specified by the device address Pa read from the device management data D1 in step S102. By controlling the operation of the regulation device 101A, the passage of the user is permitted (step S104 in FIG. 3).

After that, the security server 102 transmits the device information Pd of the device specified in step S102 to the relay device 103 (step S105 in FIG. 3, see FIG. 1). At this time, the security server 102 also transmits the management information Pj corresponding to the authentication-successful identification information Pi on a one-to-one basis to the relay device 103 (step S105 in FIG. 3). Specifically, the security server 102 has media management data D2 in addition to device management data D1. FIG. 4B is a conceptual diagram showing an example of the medium management data D2 used in the present embodiment. In the medium management data D2, in order to prevent the identification information Pi recorded on the recording medium Q from leaking to the outside, the management information Pj (for example, IC) corresponding to each of the identification information Pis on a one-to-one basis is provided. (Something like a serial number attached to a card) is associated. Then, the security server 102 reads the management information Pj corresponding to the authentication information Pi that has succeeded in authentication from the medium management data D2 and transmits the management information Pj to the relay device 103. Then, the security server 102 ends the authentication process after executing step S105.

On the other hand, if the security server 102 determines in step S103 that "it corresponds to the destination floor registration device 101B (Pb = 1)", the security server 102 proceeds to step S105 and provides device information to the relay device 103. Pd and management information Pj are transmitted. At this time, the security server 102 may cause the destination floor registration device 101B to perform an operation according to the authentication result (notification of successful authentication, etc.) before moving to step S105. Then, the security server 102 ends the authentication process after executing step S105.

Even if the authentication of the identification information Pi fails in step S101, the security server 102 causes the device (regulator device 101A or destination floor registration device 101B) that is the source of the identification information Pi to operate according to the authentication result. In order to execute the device, the device as the source is specified based on the device information Pd transmitted together with the identification information Pi in the same manner as in step S102 (step S106 in FIG. 3).

After that, as in step S103, the security server 102 asks whether the attribute information Pb read from the device management data D1 in step S106 corresponds to the regulation device 101A (Pb = 0) or the destination floor registration device 101B. It is determined whether or not it corresponds (Pb = 1) (step S107 in FIG. 3).

Then, when the security server 102 is determined in step S107 to be "corresponding to the regulation device 101A (Pb = 0)", the security server 102 is specified by the device address Pa read from the device management data D1 in step S106. By controlling the operation of the regulation device 101A, the passage of the user is restricted (specifically, prohibited) (step S108 in FIG. 3).

On the other hand, when the security server 102 determines in step S107 that "it corresponds to the destination floor registration device 101B (Pb = 1)", the device address Pa read from the device management data D1 in step S106 is set. , A disapproval signal that does not permit the user's operation on the destination floor registration device 101B is transmitted (step S109 in FIG. 3).

The processing unit that performs such an authentication process may be configured by hardware by constructing a circuit in the security server 102, or software by causing a processing device such as a CPU included in the security server 102 to execute a program. It may be composed of. Then, such a program may be stored in a portable storage device (for example, a flash memory or the like) in a readable state, or stored in a downloadable state on another server or the like, and the downloaded one is secured. It may be stored in a storage unit (not shown) of the server 102. The details of the authentication process will be described later.

<Relay device>
The relay device 103 is a device that relays the transmission of information from the security server 102 to the group management control device 105. Specifically, when the relay device 103 receives the information (including the management information Pj and the device information Pd) transmitted from the security server 102, the relay device 103 calls the management information Pj and the management information Pj. Information necessary for registration (in this embodiment, the departure floor, etc.) and information are transmitted to the group management control device 105 (relay processing, see FIG. 1).

More specifically, the relay device 103 has the installation floor management data D3. FIG. 5 is a conceptual diagram showing an example of the installation floor management data D3 used in the present embodiment. In the installation floor management data D3, the device address Pa and the attribute information Pb are associated with each device information Pd in the same manner as the device management data D1, and the device identified by the device information Pd (regulatory device 101A or destination floor registration). The installation floor Fs of the device 101B) is further associated. Then, the relay device 103 reads the installation floor Fs corresponding to the device information Pd received from the security server 102 from the installation floor management data D3, and sets the read installation floor Fs as the departure floor to the group management control device 105 together with the management information Pj. Send. At this time, in the present embodiment, the relay device 103 also reads the attribute information Pb corresponding to the device information Pd from the installation floor management data D3, and reads the read attribute information Pb together with the management information Pj and the installation floor Fs in the group management control device 105. Send to.

Further, the relay device 103 reads the device address Pa corresponding to the device information Pd received from the security server 102 from the installation floor management data D3, and is specified by the read device address Pa (regulation device 101A or destination floor registration device). By transmitting the management information Pj to 101B (hereinafter, referred to as “target device 101T”), the target device 101T is made to recognize the management information Pj. As a result, the information of the car 100 assigned by the call registration (information such as a number and a symbol for identifying the car 100; hereinafter referred to as "car information Pg") becomes the management information Pj as described later. When the group management control device 105 is broadcasted together with the group management control device 105, the car information Pg is acquired only by the target device 101T (that is, the device that should display the car information Pg) using the management information Pj as a clue. Becomes possible.

Further, when the destination floor registration device 101B receives the management information Pj from the relay device 103 as the target device 101T, the destination floor registration device 101B enables operations such as changing the destination floor and inputting the number of users. The information input in is transmitted to the group management control device 105 together with the management information Pj. As a result, the group management control device 105 can reflect the information input by the destination floor registration device 101B in the call registration.

As for the device address Pa and the attribute information Pb, those read from the device management data D1 by the security server 102 may be transmitted to the relay device 103 together with the device information Pd and used in the relay device 103. .. In this case, in the installation floor management data D3, it is not necessary to associate the device address Pa and the attribute information Pb with each of the device information Pd.

The processing unit for performing the relay processing described above may be configured by hardware by constructing a circuit in the relay device 103, or by causing a processing device such as a CPU included in the relay device 103 to execute a program. It may be composed of software. Then, such a program may be stored in a portable storage device (for example, a flash memory or the like) in a readable state, or stored in a downloadable state on another server or the like, and the downloaded program is relayed. It may be stored in a storage unit (not shown) of the device 103. The details of the relay process will be described later.

<Elevator control device>
The elevator control device 104 is provided corresponding to each of the car 100, and each elevator control device 104 controls the operation of the car 100 corresponding to the elevator control device 104. The elevator control device 104 is centrally managed and controlled by the group management control device 105.

<Group management control device>
When the group management control device 105 receives the management information Pj from the relay device 103, the group management control device 105 calls and registers the management information Pj as a target. Specifically, the group management control device 105 uses the information required for call registration (information such as the destination floor Fd corresponding to the management information Pj) as one landing call, and uses the landing call as the elevator transportation efficiency and the like. Assign to any one of a plurality of car 100s in consideration (call registration process).

In the present embodiment, the group management control device 105 has the destination floor management data D4. FIG. 6A is a conceptual diagram showing an example of destination floor management data D4 used in the present embodiment. In the destination floor management data D4, the destination floor Fd initially set as the disembarkation floor permitted to the user corresponding to the management information Pj is associated with each management information Pj. Then, the group management control device 105 reads the destination floor Fd corresponding to the management information Pj received from the relay device 103 from the destination floor management data D4, and transmits the read destination floor Fd together with the management information Pj from the relay device 103. Call registration is performed for the management information Pj using the coming installation floor Fs (departure floor) and attribute information Pb. By having the group management control device 105 have the information of the destination floor Fd in this way, the amount of data transmitted from the relay device 103 to the group management control device 105 can be reduced, and the processing speed can be increased. ..

Further, the group management control device 105 broadcasts the information of the car 100 (car information Pg) assigned in the call registration as information related to the call registration together with the management information Pj which is the target of the call registration. (See FIG. 1).

Further, the group management control device 105 further has history management data D5. FIG. 6B is a conceptual diagram showing an example of the history management data D5 used in the present embodiment. In the history management data D5, the information used in the call registration is recorded each time the call registration is executed. Specifically, the group management control device 105 inputs the management information Pj targeted for call registration and the information used in the call registration (installation floor Fs (departure floor), destination floor Fd, number of users Nr). Record in the history management data D5 in correspondence with each other. As a result, the group management control device 105 can manage the history of call registration performed for each landing call of the user by associating it with the management information Pj.

The processing unit for performing such a call registration process may be configured by hardware by constructing a circuit in the group management control device 105, or may be a processing device such as a CPU included in the group management control device 105. It may be composed of software by executing a program. Then, such a program may be stored in a portable storage device (for example, a flash memory or the like) in a readable state, or stored in a downloadable state on another server or the like, and the downloaded programs are grouped. It may be stored in a storage unit (not shown) of the management control device 105. The details of the call registration process will be described later.

[2] Control processing executed by the control system [2-1] Relay processing executed by the relay device FIG. 7 is a flowchart showing the relay processing executed by the relay device 103. The relay process is started when the relay device 103 receives information (including management information Pj and device information Pd) from the security server 102. When the relay process is started, the relay device 103 serves as the departure floor, which is one of the information required for call registration in the group management control device 105, and is the installation floor Fs corresponding to the device information Pd received from the security server 102. Is read from the installation floor management data D3 (step S11 in FIG. 7). At this time, in the present embodiment, the relay device 103 also reads the attribute information Pb corresponding to the device information Pd from the installation floor management data D3.

Further, in order to transmit the management information Pj to the device (regulatory device 101A or the destination floor registration device 101B) identified by the device information Pd received from the security server 102, the relay device 103 is a device corresponding to the device information Pd. The address Pa is read from the installation floor management data D3 (step S11 in FIG. 7).

After that, the relay device 103 transmits the installation floor Fs read in step S11 to the group management control device 105 together with the management information Pj and the attribute information Pb received from the security server 102 (step S12 in FIG. 7). As a result, the group management control device 105 can execute the call registration for the management information Pj. Further, the call registration history can be linked to the management information Pj and managed by the group management control device 105.

Further, the relay device 103 transmits the management information Pj to the target device 101T (regulation device 101A or destination floor registration device 101B) specified by the device address Pa read in step S11 (step S13 in FIG. 7). As a result, when the car information Pg is broadcasted from the group management control device 105, the car information Pg can be acquired only by the target device 101T using the management information Pj as a clue. Further, when the target device 101T is the destination floor registration device 101B, the destination floor registration device 101B is moved to a state in which operations such as changing the destination floor and inputting the number of users can be performed by using the management information Pj as a trigger. Can be made to.

[2-2] Destination floor registration process executed by the destination floor registration device FIG. 8 is a flowchart showing a destination floor registration process executed by the destination floor registration device 101Bq. The destination floor registration process is started when the destination floor registration device 101Bq transmits the identification information Pi read by its own reading device 1B to the security server 102 together with the device information Pd of the destination floor registration device 101Bq. When the destination floor registration process is started, the destination floor registration device 101Bq determines whether or not a disapproval signal has been received from the security server 102 (step S21 in FIG. 8).

When the destination floor registration device 101Bq determines in step S21 that "received (Yes)", the destination floor registration device 101Bq does not allow the user to input the number of users Nr (in the present embodiment, the number of people input screen (see FIG. 9)). Is not displayed on the display device 2B), and the destination floor registration process is completed. On the other hand, when the destination floor registration device 101Bq determines in step S21 that "not received (No)", it determines whether or not the management information Pj has been received from the relay device 103 (step S22 in FIG. 8). .. Then, the destination floor registration device 101Bq repeatedly executes steps S21 and S22 until it can be determined in step S21 or S22 that "received (Yes)".

When the destination floor registration device 101Bq determines in step S22 that it has “received (Yes)”, the destination floor registration device 101Bq temporarily stores the received management information Pj in its own storage unit (not shown) (step S221 in FIG. 8). Further, the destination floor registration device 101Bq enables the user to input the number of users Nr (step S222 in FIG. 8). Specifically, the destination floor registration device 101Bq displays a screen (number of people input screen) on which the number of users Nr can be input on its own display device 2B. FIG. 9 is a conceptual diagram showing an example of a number input screen. The number of people input screen of FIG. 9 includes a numeric keypad for inputting the number of users Nr, a display area for displaying the number of users Nr entered with the numeric keypad, and a confirmation button for confirming the number of users Nr entered with the numeric keypad. Includes. As shown in FIG. 9, the number of people input screen may further display a management information Pj, a cancel button for canceling the input of the number of users Nr, and the like. Further, the number of people input screen is not limited to the one in which the number of users Nr is input by the numeric keypad, and may be appropriately changed to one in which the user selects one from a plurality of options. Further, the destination floor registration device 101Bq is not limited to the one that operates on the touch panel, and may be the one that performs the selection operation with the mechanical buttons while looking at the screen of the display device 2B.

Next, the destination floor registration device 101Bq starts measuring the elapsed time Tm from the time when step S222 (display of the number of people input screen) is executed (step S223 in FIG. 8). After that, the destination floor registration device 101Bq determines whether or not the elapsed time Tm during measurement exceeds the predetermined time T0 (step S224 in FIG. 8). Here, the predetermined time T0 is used to limit the time for allowing the user to input the number of users Nr.

When the destination floor registration device 101Bq determines in step S224 that it does not exceed (No), it determines whether or not the number of users Nr has been input (step S225 in FIG. 8). Specifically, the destination floor registration device 101Bq determines whether or not the number of users Nr has been determined on the number of people input screen (see FIG. 9) displayed on its own display device 2B.

When the destination floor registration device 101Bq determines in step S225 that "input (Yes)" (confirmed), the input (confirmed) number of users Nr is grouped together with the management information Pj stored in step S221. It is transmitted to the management control device 105 (step S226 in FIG. 8). As a result, the group management control device 105 can reflect the number of users Nr input by the destination floor registration device 101Bq in the call registration for the management information Pj.

On the other hand, if the destination floor registration device 101Bq determines in step S225 that "it has not been input (No)" (it has not been confirmed), it returns to step S224.

Then, if the destination floor registration device 101Bq cannot determine "input (Yes)" in step S225 and determines "elapsed (Yes)" in step S224, that determination is made. Therefore, it can be determined that the user has no intention of inputting the number of users Nr, that is, the user is trying to use the elevator by himself / herself. Therefore, the destination floor registration device 101Bq sets the number of users Nr to "1" (step S227 in FIG. 8). After that, the destination floor registration device 101Bq transmits the number of users Nr set in step S227 to the group management control device 105 together with the management information Pj stored in step S221 (step S226 in FIG. 8).

After executing step S226, the destination floor registration device 101Bq determines whether or not the car information Pg has been received from the group management control device 105 (step S23 in FIG. 8). Then, the destination floor registration device 101Bq repeatedly executes step S23 until it can be determined in step S23 that "received (Yes)".

When the destination floor registration device 101Bq determines that "received (Yes)" in step S23, whether or not the destination floor registration device 101Bq itself stores the same management information Pj as the management information Pj transmitted together with the received car information Pg. It is further determined (step S231 in FIG. 8). As a result, the destination floor registration device 101Bq transmits the management information Pj transmitted together with the car information Pg indicating whether or not the car information Pg delivered by the broadcast should notify the user. It becomes possible to judge as a clue.

Therefore, when the destination floor registration device 101Bq determines in step S231 that it "remembers (Yes)", the destination floor registration device 101Bq displays the received car information Pg on its own display device 2B (step S232 in FIG. 8). After that, the destination floor registration device 101Bq erases the management information Pj from its own storage unit (step S233 in FIG. 8), and then ends the destination floor registration process. On the other hand, if the destination floor registration device 101Bq determines in step S231 that "it is not stored (No)", the destination floor registration device 101Bq returns to step S23.

[2-3] Call registration process executed by the group management control device FIG. 10 is a flowchart showing a call registration process executed by the group management control device 105. The call registration process is performed when the group management control device 105 receives information (information required for call registration. In this embodiment, management information Pj, installation floor Fs (departure floor), and attribute information Pb) from the relay device 103. Is started on. When the call registration process is started, the group management control device 105 reads the destination floor Fd corresponding to the management information Pj received from the relay device 103 from the destination floor management data D4 (step S31 in FIG. 10). As a result, the group management control device 105 acquires the information required for call registration, which is insufficient.

After that, the group management control device 105 determines whether the attribute information Pb received from the relay device 103 corresponds to the type of the regulation device 101A or the destination floor registration device 101B (step S32 in FIG. 10). .. By using the attribute information Pb in this way, the group management control device 105 reads the identification information Pi corresponding to the management information Pj when calling and registering the management information Pj. (That is, which type is the regulation device 101A or the destination floor registration device 101B) can be specified.

Then, in the present embodiment, since the information on the number of users Nr is not transmitted from the regulation device 101A, when it is determined in step S32 that the group management control device 105 corresponds to the "regulation device 101A". Based on this judgment, it can be determined that it is not necessary to receive the number of users Nr before executing the call registration. On the other hand, since the information on the number of users Nr is transmitted from the destination floor registration device 101B, if the group management control device 105 determines in step S32 that it corresponds to the "destination floor registration device 101B", the information is transmitted. Based on the judgment, it can be determined that it is necessary to receive the number of users Nr before executing the call registration.

Therefore, when the group management control device 105 determines in step S32 that "the device corresponds to the regulation device 101A (Pb = 0)", the group management control device 105 is called normally for the management information Pj received from the relay device 103. Registration (that is, call registration for one person) is performed (step S33A in FIG. 10). Specifically, the group management control device 105 uses information including the installation floor Fs (departure floor) and the destination floor Fd as one landing call, and multiple landing calls in consideration of the transportation efficiency of the elevator and the like. Assign to any one of the 100 cars. In this way, when the user is permitted to pass through the regulation device 101A, the group management control device 105 can be immediately called and registered.

After executing the call registration in step S33A, the group management control device 105 broadcasts the car information Pg (number, symbol, etc.) of the car 100 assigned in step S33A together with the management information Pj which is the target of the call registration. Deliver (step S33B in FIG. 10).

On the other hand, when the group management control device 105 determines in step S32 that "it corresponds to the destination floor registration device 101B (Pb = 1)", before receiving the number of users Nr from the destination floor registration device 101B. , The destination floor Fd read out in step S31 is temporarily stored in its own storage unit (not shown) together with the management information Pj and the installation floor Fs received from the relay device 103 (not shown). ).

After that, the group management control device 105 determines whether or not the number of users Nr has been received from the destination floor registration device 101Bq (step S35 in FIG. 10). Then, the group management control device 105 repeatedly executes step S35 until it can be determined in step S35 that "received (Yes)".

When the group management control device 105 determines in step S33 that "received (Yes)", the group management control device 105 supplies the same management information Pj as the management information Pj transmitted from the destination floor registration device 101Bq together with the number of users Nr received. It is read from its own storage unit together with the corresponding installation floor Fs and destination floor Fd (step S36 in FIG. 10). Then, the group management control device 105 uses the number of users Nr received from the destination floor registration device 101Bq and the information read in step S36 (management information Pj, installation floor Fs, and destination floor Fd) to perform call registration. (Step S37A in FIG. 10). That is, when the group management control device 105 also receives the same management information Pj as the management information Pj received from the relay device 103 from the destination floor registration device 101Bq, the group management control device 105 is transmitted from the destination floor registration device 101Bq together with the management information Pj. Call registration is performed using the number of users Nr.

Specifically, the group management control device 105 uses information including the installation floor Fs (departure floor) and the destination floor Fd as one landing call, and multiple landing calls in consideration of the transportation efficiency of the elevator and the like. Assign to any one of the 100 cars. At this time, the group management control device 105 further considers the number of passengers Nr and allocates the landing call to the car 100. Specifically, when the number of users Nr is plural (Nr> 1), the group management control device 105 further includes information including the number of users Nr in addition to the installation floor Fs (departure floor) and the destination floor Fd. As a landing call, the landing call is assigned to any one of a plurality of car 100s. As an example, the group management control device 105 selects a car 100 capable of accommodating all users for Nr users from a plurality of cars 100, and puts together the landing calls for Nr users in the selected car 100. And assign. As a result, the number of users Nr input by the destination floor registration device 101Bq is reflected in the call registration for the management information Pj.

After executing the call registration in step S37A, the group management control device 105 broadcasts the car information Pg (number, symbol, etc.) of the car 100 assigned in step S37A together with the management information Pj which is the target of the call registration. Deliver (step S37B in FIG. 10).

Then, the group management control device 105 includes the management information Pj targeted for call registration in step S37A, the information used in the call registration (installation floor Fs (departure floor), destination floor Fd, number of users Nr), and Are recorded in the history management data D5 in correspondence with each other (step S38 in FIG. 10). As a result, the group management control device 105 can manage the history of call registration performed for each landing call of the user by associating it with the management information Pj.

By managing the call registration history in association with the management information Pj in this way, it is possible to suppress the actions of malicious users such as inputting a larger number of people than the actual number of users with the destination floor registration device 101Bq. can. As an example, when a large number of users Nr are frequently recorded for the same management information Pj in the history management data D5, the group management control device 105 performs the user's action regarding the management information Pj. Call registration for the management information Pj can be restricted (for example, temporarily prohibited) by determining that it is a malicious act. As another example, the group management control device 105 assigns the number of users Nr recorded in the history management data D5 to the photographed image in the car 100 assigned in the call registration (step S37A in FIG. 10) using the number of users Nr. When the actual number of passengers is less than the number of passengers Nr (for example, when it can be determined that the number of passengers is clearly smaller) than the actual number of passengers that can be extracted from, the management information associated with the number of passengers Nr. The user's actions regarding Pj may be determined to be malicious actions, and call registration for the management information Pj may be restricted (for example, temporarily prohibited). As described above, according to the control system of the present embodiment, it is possible to monitor the landing call made by the user in the elevator.

After that, the group management control device 105 erases the management information Pj and the corresponding information (including the installation floor Fs and the destination floor Fd) targeted for call registration in step S37A from its own storage unit (FIG. 10). Step S39), and then the call registration process is completed.

[3] Modification Example [3-1] First Modification Example In the control system described above, the group management control device 105 is a device (regulator device 101A) as a transmission destination instead of delivering the car information Pg by broadcasting. Alternatively, the device information Pd (or device address Pa) of the destination floor registration device 101B) is acquired from the relay device 103, and the car information Pg is transmitted to the device identified by the device information Pd based on the device information Pd. You may.

[3-2] Second Modification Example The control system described above can also be applied to an elevator in which the regulation device 101A is not installed. In this case, the group management control device 105 reads the identification information Pi corresponding to the management information Pj when calling and registering the management information Pj (that is, the regulation device 101A or the destination floor registration device). Since it is not necessary to specify which type of 101B), the attribute information Pb is unnecessary for the group management control device 105. Therefore, in this case, it is not necessary to transmit the attribute information Pb from the relay device 103 to the group management control device 105, and therefore, even if the attribute information Pb is not associated with each device information Pd in the installation floor management data D3. good.

[3-3] Third Modified Example The control system described above is not limited to the one constructed without including the regulation device 101A and the security server 102, but is constructed with at least one of them or a part thereof. It may be a new one.

[3-4] Fourth Modified Example In the control system described above, the relay device 103 may further have the attribute management data D6. FIG. 11 is a conceptual diagram showing an example of the attribute management data D6 used in this modification. In the attribute management data D6, the attribute information Pc indicating whether or not the use of the elevator in the group is permitted is associated with each management information Pj. In FIG. 11, “0” and “1” are used as the attribute information Pc in order to distinguish whether or not the use of the elevator in the group is permitted. Hereinafter, the relay process, the destination floor registration process, and the call registration process executed in this modification will be described.

12 to 14 are flowcharts showing the relay process, the destination floor registration process, and the call registration process executed in this modification, respectively. In the relay process (FIG. 12) of this modification, the relay device 103 further reads the attribute information Pc corresponding to the management information Pj received from the security server 102 from the attribute management data D6 in step S11. Then, in step S12, the relay device 103 transmits the attribute information Pc together with the information such as the installation floor Fs to the group management control device 105, and in step S13, the attribute information Pc is transmitted to the target device 101T together with the management information Pj. ..

According to such a configuration, the following processing can be executed by the destination floor registration device 101Bq and the group management control device 105. That is, when the attribute information Pc indicates that the use of the elevator in the group is permitted (Pc = 1) in the destination floor registration device 101Bq (specifically, step S220 in FIG. 13). The number input screen (see FIG. 9) can be displayed only when it is determined that "Pc = 1" (step S222 in FIG. 13). Further, when the attribute information Pc indicates to the group management control device 105 that the use of the elevator in the group is permitted (Pc = 1) (specifically, step S320 in FIG. 14). Only when it is determined that "Pc = 1"), the call registration using the number of users Nr input by the destination floor registration device 101Bq can be executed (step S37A in FIG. 14).

In other words, if the attribute information Pc indicates that the use of the elevator in the group is not permitted (Pc = 0), the destination floor registration device 101Bq does not display the number input screen. (End of destination floor registration process) Further, the group management control device 105 can immediately execute normal call registration (call registration for one person. Step S33A in FIG. 14).

The description of the embodiments described above should be considered exemplary in all respects and not restrictive. The scope of the present invention is shown not by the above-described embodiment but by the scope of claims. Furthermore, the scope of the present invention is intended to include all modifications within the meaning and scope equivalent to the claims.

In addition to the inventions described in the claims, the description of the above-described embodiment includes an invention characterized by extracting the point that the car information Pg is distributed by broadcasting using the management information Pj. Also included are inventions characterized by extracting the fact that the group management control device 105 has information on the destination floor Fd (in the above-described embodiment, the destination floor management data D4).

1A, 1B Reader 2A, 2B Display device H Landing area Q Recording medium D1 Device management data D2 Media management data D3 Installation floor management data D4 Destination floor management data D5 History management data D6 Attribute management data Fd Destination floor Fs Installation floor Nr Number of users Pa Device address Pb, Pc Attribute information Pd Device information Pg Vehicle information Pi Identification information Pj Management information T0 Predetermined time Tm Elapsed time 100 Vehicle 101A Control device 101B, 101Bp, 101Bq Destination floor registration device 101T Target device 102 Security server 103 Relay Device 104 Elevator control device 105 Group management control device

Claims (4)

A control device that controls the elevator and
A reader that reads the user's identification information,
A relay device that relays management information corresponding to the identification information read by the reading device and transmits the management information to the control device.
Registration device and
With
The registration device is provided with a first reading device, which is one of the reading devices.
When the identification information is read by the first reading device, the relay device also transmits the management information corresponding to the identification information to the registration device.
When the registration device receives the management information from the relay device, the registration device enables input of the number of users, and transmits the input number of users to the control device together with the management information received from the relay device. death,
The control device is a device that calls and registers the management information when the management information is received from the relay device, and receives the same management information as the management information received from the relay device from the registration device. When the information is also received, the elevator control system performs the call registration using the number of users transmitted from the registration device together with the management information. The elevator control system according to claim 1 , wherein the control device broadcasts information related to the call registration together with the management information that is the target of the call registration. The control system according to claim 1 or 2 , which is applied to an elevator in which a regulation device for restricting entry to a landing is installed.
Wherein the regulating device, which is one and the second reading device is provided for the reading device,
When the identification information is read by either the first reading device or the second reading device, the relay device reads the management information corresponding to the identification information by the identification information in the first reading. An elevator control system that transmits to the control device together with attribute information indicating whether the device or the second reading device has read the information. The control device has destination floor management data in which destination floors are associated with each management information.
When the control device receives the management information from the relay device, the control device reads the destination floor associated with the management information from the destination floor management data, and uses the read destination floor to register the call. The elevator control system according to any one of claims 1 to 3.

Images