Elevator system

Abstract

The embodiment of the invention relates to an elevator system. In a system using a portable terminal to perform call registration, calls other than normal elevator hall calls are simply registered. An elevator system according to one embodiment of the present invention performs call registration using a portable terminal, and has a plurality of elevator control devices and a server device. A portable terminal is provided with: an attribute setting unit that sets attribute information indicating an attribute of a user; a storage unit that stores attribute information; and a call registration unit which adds the attribute information to the call information and sends the call information to the server device when the user registers the call information in the elevator hall of any of the plurality of buildings. The server device is provided with an operation control part, and when the call information and the attribute information are received from the portable terminal, the operation control part replaces the call information with a specific call according to the attribute information and sends the specific call to the elevator control device arranged on any building, so that operation considering the attribute of the user is executed.

Description

[0001] This application is based on Japanese Patent Application No. 2024-002515 (filing date: January 11, 2024), and this application claims the priority of this Japanese application. This application incorporates the entire content of this Japanese application by reference thereto. Technical Field

[0002] An embodiment of the present invention relates to an elevator system. Background Art

[0003] Generally, a landing call button for registering a landing call is provided in an elevator landing hall. When the landing call button is operated by an elevator user, the passenger car responds to the landing call.

[0004] In recent years, a system that can register a landing call from a portable terminal such as a user's smartphone has been considered instead of the landing call button. Specifically, when a user inputs call information (building information, registration floor, destination direction) on a call registration screen displayed on the portable terminal, this call information is sent to an elevator control device via a cloud server on the Internet and registered as a landing call.

[0005] Here, sometimes a wheelchair call button is provided in the elevator for wheelchair users. When a wheelchair call is registered by the wheelchair call button, for example, a passenger car with a long door opening time is made to respond. Thereby, a wheelchair user can board the passenger car without haste.

[0006] In the above system, the call information sent from the portable terminal is treated as a normal landing call. In order to be able to register a wheelchair call different from a normal landing call, it is necessary to add an interface (button, etc.) for wheelchair call registration on the call registration screen. Summary of the Invention

[0007] However, if a button or the like is added to the call registration screen, the operation of call registration becomes complicated, and there is a possibility that the user may not be able to perform call registration smoothly.

[0008] The problem to be solved by the present invention is to provide an elevator system that can simply register a call other than a normal landing call in a system that uses a portable terminal for call registration.

[0009] An elevator system according to an embodiment uses a portable terminal installed with an application software for call registration to perform call registration for an elevator. The elevator system includes: a plurality of elevator control devices, each of which is provided in each of a plurality of buildings and controls the operation of an elevator; and a server device that is connected to the plurality of elevator control devices via a communication network. The portable terminal includes: an attribute setting unit, a storage unit, and a call registration unit. The attribute setting unit sets attribute information indicating the attributes of the user. The storage unit stores the attribute information set by the attribute setting unit. In a waiting hall of any one of the plurality of buildings, when the user registers call information, the call registration unit attaches the attribute information stored in the storage unit to the call information and sends it to the server device. The server device includes an operation control unit. When receiving the call information and the attribute information from the portable terminal, the operation control unit replaces the call information with a specific call according to the attribute information and sends it to the elevator control device provided on the any one building, thereby performing an operation considering the attributes of the user.

[0010] In the elevator system configured as described above, in a system using a portable terminal for call registration, it is possible to simply register calls other than normal waiting hall calls. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 FIG. is an example showing the configuration of an elevator system according to a first embodiment.

[0012] Figure 2 FIG. is a block diagram showing the configuration of an elevator control device according to a first embodiment.

[0013] Figure 3 FIG. is a block diagram showing the configuration of a server device according to a first embodiment.

[0014] Figure 4 FIG. is a block diagram showing the configuration of a portable terminal according to a first embodiment.

[0015] Figure 5 FIG. is an example showing an attribute registration screen according to a first embodiment.

[0016] Figure 6 FIG. is an example showing a call registration screen according to a first embodiment.

[0017] Figure 7 FIG. schematically shows the configuration of call information and attribute information when sending information to a server device according to a first embodiment.

[0018] Figure 8A FIG. is a flowchart showing the processing flow of a portable terminal and a server device according to a first embodiment.

[0019] Figure 8B is a flowchart showing the processing flow of the elevator control device of the first embodiment.

[0020] Figure 9 is a diagram showing an example of the attribute registration screen of the first modification of the first embodiment.

[0021] Figure 10 is a diagram showing an example of the attribute registration screen of the second modification of the first embodiment.

[0022] Figure 11 is a diagram showing the functional configuration of the elevator control device of the second embodiment.

[0023] Figure 12 is a diagram showing an example of the installation position of the camera of the second embodiment.

[0024] Figure 13 is a block diagram showing the configuration of the elevator control device of the third embodiment.

[0025] Figure 14 is a block diagram showing the configuration of the server device of the third embodiment.

[0026] Figure 15A is a flowchart showing the processing flow of the portable terminal and the server device of the third embodiment.

[0027] Figure 15B is a flowchart showing the processing flow of the elevator control device of the third embodiment. Detailed Embodiments

[0028] Hereinafter, an elevator system according to an embodiment will be described with reference to the accompanying drawings.

[0029] In addition, the present disclosure is merely an example, and the invention is not limited to the content described in the following embodiments. Modifications that can be easily made by those skilled in the art are of course included in the scope of the present disclosure. For clearer explanation, in the drawings, the dimensions, shapes, etc. of each part may be changed relative to the actual embodiment and shown schematically. In multiple drawings, the same reference numerals are assigned to corresponding elements, and detailed descriptions may sometimes be omitted.

[0030] (First Embodiment)

[0031] Figure 1 is a diagram showing an example of the configuration of an elevator system according to an embodiment.

[0032] In the figure, 10a and 10b represent buildings such as office buildings into which this elevator system is introduced (hereinafter referred to as buildings). Elevator control devices 20a and 20b are respectively provided on buildings 10a and 10b. In addition, in Figure 1 the example, only two buildings 10a and 10b are shown for convenience, but actually there are multiple buildings, and the elevator control devices provided on each of these buildings are connected to the server device 30 via a communication network 1 described later so as to be capable of mutual data communication. The server device 30 is a computer that uniformly manages the elevators of each building.

[0033] The elevator control device 20a controls the operation of passenger cars (elevators) 11-1a to 11-3a provided in building 10a. The passenger cars 11-1a to 11-3a are supported so as to be movable up and down on a pair of guide rails erected in a hoistway, and move between floors in response to a hall call and a car call. A "hall call" refers to a call signal registered in the hall on each floor and includes information on the registered floor and the destination direction. In addition, a "car call" refers to a call signal registered in the car interior and includes information on the destination floor.

[0034] In this system, as described later, it is possible to register a hall call using a portable terminal 40 held by each user. Therefore, it is not necessary to operate a hall call button (not shown) provided on the hall 12a on each floor. In the following description, for convenience, the hall call registered using the portable terminal 40 is referred to as a "smartphone call".

[0035] The elevator control device 20b controls the operation of the passenger car 11b provided in building 10b. The passenger car 11b is supported so as to be movable up and down on a pair of guide rails erected in a hoistway, and move between floors in response to a hall call and a car call.

[0036] The elevator control devices 20a and 20b of the present embodiment are set to be able to register a "wheelchair call" different from a normal hall call. A "wheelchair call" refers to a hall call for calling a wheelchair-corresponding car. Usually, a wheelchair call is registered by a wheelchair call button provided on halls 12a and 12b, but in the present embodiment, as described later, it is possible to register a wheelchair call using the user's portable terminal 40.

[0037] In addition, the "wheelchair - corresponding car" includes, for example, a passenger car with a door opening time set longer than that of a standard - specification passenger car, a passenger car with a door opening / closing speed set slower than that of a standard - specification passenger car, or a passenger car equipped with a call button, a rear - view mirror, etc. for wheelchair users inside the car. When a wheelchair call is registered, the elevator control device 20a that controls the multiple passenger cars 11 - 1a to 11 - 3a causes the passenger car among the passenger cars 11 - 1a to 11 - 3a set as the wheelchair - corresponding car to respond. In addition, when a wheelchair call is registered, the elevator control device 20b that controls one passenger car 11b causes the passenger car 11b to respond as the wheelchair - corresponding car. In this case, for example, the door opening time of this passenger car 11b is set longer than normal.

[0038] The elevator control devices 20a and 20b are connected to the server device 30 via the communication network 1. The server device 30 has a function of cooperating with the elevator control devices 20a and 20b to perform processing related to smartphone calls.

[0039] The portable terminal 40 for smartphone calls is a general portable telephone, a smartphone, etc. An application software 40a for call registration is pre - installed in the portable terminal 40. This application software 40a for call registration is developed by an affiliated company of the elevator and can be freely downloaded from a website dependent on the OS (Operating System) of the portable terminal 40. The user registers a smartphone call via the server device 30 on the Internet by performing a prescribed operation on the call registration screen (refer to Figure 6 ) of this application software 40a.

[0040] Figure 2 is a block diagram showing the configuration of the elevator control device 20a of the present embodiment. In addition, the elevator control device 20b also has the same Figure 2 configuration.

[0041] The elevator control device 20a includes a storage unit 21, a control unit 22, and a communication unit 23.

[0042] The storage unit 21 stores various programs and information required for the processing of the control unit 22. In the present embodiment, the storage unit 21 has a call management table 21a. In the call management table 21a, the hall calls (including smartphone calls) registered in the hall 12a on each floor are stored together with the information of the registration floor, and the information of the passenger car assigned to these calls is stored.

[0043] The control unit 22 is a part that executes various processes required for the operation of the passenger cars 11 - 1a to 11 - 3a by starting a program. The control unit 22 has a car operation unit 22a and a door opening / closing control unit 22b.

[0044] The car operation unit 22a controls the operation of the passenger cars 11-1a to 11-3a. The car operation unit 22a allocates and responds to any one of the passenger cars 11-1a to 11-3a for the hall calls stored in the call management table 21a, and makes the corresponding passenger car go to the destination floor of the user. In addition, the car operation unit 22a makes the passenger car set as the wheelchair-corresponding car respond to the wheelchair call.

[0045] The door opening / closing control unit 22b controls the opening / closing operation of the car doors when the passenger cars 11-1a to 11-3a reach the hall 12a. Specifically, when it is detected by a leveling detection device (not shown) that one of the passenger cars 11-1a to 11-3a has leveled at the hall 12a, the door opening / closing control unit 22b moves the car door of the corresponding passenger car in the opening direction to fully open. And after a specified time, the door opening / closing control unit 22b moves the car door of the corresponding passenger car in the closing direction to fully close. In addition, as the car door moves, the hall door also moves in the same direction. In addition, when the passenger car leveled in the hall 12a is the wheelchair-corresponding car, the specified time from fully open to fully close of the car door is set longer. Or, the opening / closing speed of the door of the wheelchair-corresponding car is set slower. The communication unit 23 performs communication processing between the elevator control device 20a and the server device 30.

[0046] Figure 3 It is a block diagram showing the configuration of the server device 30 of the present embodiment.

[0047] The server device 30 includes a storage unit 31, a control unit 32, and a communication unit 33. The storage unit 31 stores various programs and information required for the processing of the control unit 32. The storage unit 31 has a building management table 31a storing building information. The building information includes the building name (or identification information of the building) of each building 10a, 10b and information of the elevator control device installed on the building, etc.

[0048] The control unit 32 is a part for overall control of the server device 30, and in the present embodiment, it has an operation control unit 32a for executing processing related to smartphone calls.

[0049] When the server device 30 receives a call message and attribute information from the portable terminal 40, the operation control unit 32a replaces the call message with a specific call according to the attribute information, and sends it to the elevator control device installed in the building where the user is located, thereby performing an operation considering the user's attributes. In addition, the so-called "call information" is information including the building where the user is located, the waiting floor, and the destination direction (or destination floor). The communication unit 33 has a function of performing communication processing between the server device 30 and the elevator control devices 20a and 20b, and a function of performing communication processing between the server device 30 and the portable terminal 40.

[0050] Figure 4 It is a block diagram showing the configuration of the portable terminal 40 according to the present embodiment.

[0051] The portable terminal 40 includes an input unit 41, a display unit 42, a control unit 43, a storage unit 44, a communication unit 45, and the like.

[0052] The input unit 41 is composed of various keys, buttons, etc., and performs data input and indication. The display unit 42 is composed of, for example, an LCD, and performs data display. In addition, for example, a transparent touch panel can also be used as the input unit 41 to perform data input and indication on the screen of the display unit 42.

[0053] The control unit 43 is composed of a CPU, and executes various functions by starting a prescribed program. In the present embodiment, the control unit 43 executes the processing of the attribute setting unit 43a and the call registration unit 43b by starting the application software 40a for call registration pre-installed in the portable terminal 40.

[0054] The attribute setting unit 43a performs processing for setting attribute information indicating the user's attributes. Specifically, through a prescribed operation of the user, the attribute setting unit 43a displays an attribute registration screen A11 (refer to Figure 5 ) having a plurality of items (first items) for determining the attributes of a wheelchair user on the display unit 42, and sets attribute information (first attribute information) indicating that the user is a wheelchair user based on the items arbitrarily selected by the user (specifically, stores the attribute information in a readable manner in the storage unit 44).

[0055] The call registration unit 43b performs processing for registering the user's call information. Specifically, through a prescribed operation of the user, the call registration unit 43b displays a call registration screen A12 (refer to Figure 6 ) on the display unit 42, and sends the call information input on the call registration screen A12 to the server device 30. At this time, the call registration unit 43b reads out the user's attribute information from the storage unit 44, and attaches the attribute information to the call information and sends it (refer to Figure 7)。

[0056] The storage unit 44 stores various programs required for the processing of the control unit 43, including various applications including the application software 40a. In addition, the storage unit 44 stores the attribute information of the user set by the attribute setting unit 43a. The communication unit 45 performs communication processing between the portable terminal 40 and the server device 30.

[0057] Next, the configuration of the application software 40a will be described.

[0058] As described above, the application software 40a has a function of causing the control unit 43 to execute the processing of the attribute setting unit 43a and the call registration unit 43b. The application software 40a is downloaded from an application store existing on the network to the user's portable terminal 40.

[0059] Figure 5 FIG. is an example showing an attribute registration screen A11. The attribute registration screen A11 is displayed, for example, by a predetermined operation such as clicking on a menu of "user registration" on a main screen (not shown) after the application software 40a is started. The attribute registration screen A11 is provided with a plurality of items for determining wheelchair use attributes, and selection buttons are provided for each item so that the plurality of items can be selected separately.

[0060] In Figure 5 example, the attribute registration screen A11 includes a selection button B11 and a selection button B12. The selection button B11 is a button for selecting the "using a wheelchair" state (item A). The selection button B12 is a button for selecting the "currently injured" state (item B). The selection buttons B11 and B12 can be displayed by a radio button that can select either item A or item B, or can be displayed by a check box that can select both. In Figure 5 shown by a radio button, it indicates that the user has selected item A. When the user selects at least one of these items, the attribute of "wheelchair user" is set. In contrast, when no button is selected, the attribute of "general user" (fourth attribute information) is set.

[0061] In addition, the items displayed on the attribute registration screen A11 are not limited to Figure 5 example, and items for selecting the status of a user who requires a wheelchair-corresponding car can be further displayed. For example, items indicating that a cane is being used, old age, pregnancy, etc. can be selectively displayed.

[0062] Figure 6 FIG. is an example showing a call registration screen A12. The call registration screen A12 is displayed, for example, by a predetermined operation such as clicking on a menu of "call registration" on a main screen (not shown) after the application software 40a is started.

[0063] The call registration screen A12 is provided with a building selection button B13, a waiting floor input form F11, a destination floor input form F12, a destination direction button B14, and a send button B15.

[0064] The building selection button B13 is a button for selecting the building where the user is located. It is configured such that when the building selection button B13 is clicked, a list of buildings available in this elevator system is displayed, and any building can be selected from this list. In Figure 6 the example, "Building A" is selected.

[0065] The waiting floor input form F11 is an input form for inputting the waiting floor of the user. When the waiting floor input form F11 is clicked, a keyboard (not shown) is displayed on the screen. The waiting floor of the user can be input through the operation of this keyboard. In Figure 6 the example, "2nd floor" is input. In addition, the input method of the user's waiting floor is not limited to Figure 6 the keyboard method as in the example. For example, it can also be configured such that when any building is selected through the building selection button B13, a floor list of that building is displayed, and the user selects the floor as the waiting floor from this floor list.

[0066] The destination direction button B14 is a button for selecting up or down as the destination direction of the user. Figure 6 indicates the case where up is selected. In addition, it can also be configured such that instead of selecting the destination direction of the user through the destination direction button B14, the destination floor of the user is directly input in the destination floor input form F12. In this case, the input destination floor is processed as a car call. Therefore, when the user is already on board in the car, there is no need to register the destination floor through the operation of the in-car operation panel.

[0067] The send button B15 is a button for determining each piece of information (building, waiting floor, destination direction, or destination floor) input on the call registration screen A12 and sending it to the server device 30. When the send button B15 is clicked, this information is sent to the server device 30 in a specified form together with the attribute information as the call information of the user.

[0068] Figure 7 is a diagram schematically showing the composition of the call information and the attribute information sent to the server device 30. As Figure 7As shown, the call information includes the "building name" input by the building selection button B13 on the call registration screen A12, the "waiting floor" input by the waiting floor input form F11, and the "destination direction" selected by the destination direction button B14. In addition, when the destination floor is input in the destination floor input form F12 instead of the destination direction button B14, the destination floor is included in the call information instead of the destination direction.

[0069] Here, when the send button B15 is clicked, the "attribute information" is read from the storage unit 44 of the portable terminal 40, attached to the call information, and sent to the server device 30.

[0070] Next, the operation of the first embodiment will be described.

[0071] Here, it is assumed that the user U holds the portable terminal 40 and comes to the elevator hall 12a on any floor of the building 10a (see Figure 1 ). In addition, in the storage unit 44 of the portable terminal 40, the attribute information of the user U is pre-stored through the Figure 5 shown attribute registration screen A11.

[0072] Figure 8A and Figure 8B are flowcharts showing the processing flow of the elevator system of the first embodiment. Figure 8A Represents the processing of the portable terminal 40 and the server device 30, Figure 8B Represents the processing of the elevator control device 20a.

[0073] First, with reference to Figure 8A , the processing flow of the portable terminal 40 and the server device 30 will be described.

[0074] Through a predetermined operation of the user U, the call registration screen A12 shown in Figure 6 is displayed on the display unit 42 of the portable terminal 40 (step S11). When each information of the building, waiting floor, destination direction, or destination floor is input on the call registration screen A12 and the send button B15 is operated (YES in step S12), the portable terminal 40 (call registration unit 34b) generates call information including this information, attaches attribute information to the call information, and sends it to the server device 30 in the form shown in Figure 7 (step S13).

[0075] When the server device 30 (control unit 32) receives a call message and attribute information from the portable terminal 40, it determines whether the user U is a wheelchair user based on the attribute information (step S14). If the user U is a wheelchair user (Yes in step S14), the server device 30 replaces the call message received from the portable terminal 40 with a wheelchair call.

[0076] In addition, "replacing the call message with a wheelchair call" includes requesting the elevator control device to process the call message as a wheelchair call. More specifically, the code signal indicating the call message registered as a normal hall call (general call) is changed to the code signal indicating the wheelchair call registered by pressing the wheelchair call button.

[0077] The server device 30 sends the above-mentioned wheelchair call to the elevator control device 20a provided in the building 10a where the user U is located (step S15). Specifically, the server device 30 determines the building 10a where the user U is located based on the building information included in the call message, refers to the building management table 31a, and sends the wheelchair call to the elevator control device 20a corresponding to the building 10a.

[0078] On the other hand, if the user U is not a wheelchair user but a general user (No in step S14), the server device 30 sends the call message without replacement to the elevator control device 20a (step S16).

[0079] Next, refer to Figure 8B Describe the processing flow of the elevator control device 20a.

[0080] When the elevator control device 20a receives a wheelchair call from the server device 30 (Yes in step S17), it stores the wheelchair call in the call management table 21a in the same way as the wheelchair call registered by pressing an unillustrated wheelchair call button (step S18). The elevator control device 20a (car operation unit 22a) assigns the wheelchair call to the car set as the wheelchair-corresponding car among the cars 11-1a, 11-2a, and 11-3a to make it go to the waiting floor of the user U (step S19).

[0081] On the other hand, when the elevator control device 20a receives call information from the server device 30 that has not been replaced with a wheelchair call (No in step S17), the elevator control device 20a stores this call information as a normal landing call in the call management table 21a in the same manner as a normal landing call registered by pressing the landing call button (step S20). The elevator control device 20a (car operation unit 22a) assigns this normal landing call to the passenger cars other than the wheelchair-corresponding car among the passenger cars 11-1a, 11-2a, and 11-3a and makes it go to the waiting floor of the user U (step S21).

[0082] In addition, in Figure 8A and Figure 8B it has been described assuming the case where the user U makes a call registration in the building 10a, but the case where the user U makes a call registration in the building 10b is the same. That is, the normal call information registered by the portable terminal 40 is replaced with a wheelchair call according to the attribute information and is sent to the elevator control device 20b of the building 10b where the user U is located. When the elevator control device 20b receives the wheelchair call, it makes the passenger car 11b go to the waiting floor of the user U as the wheelchair-corresponding car.

[0083] In this way, according to the first embodiment, if the attribute information indicating that the user is a wheelchair user is set in the user's portable terminal 40 in advance, the normal call information registered by the normal operation is replaced with a wheelchair call and is sent to the elevator control device of the building where the user is located. Therefore, there is no need to add a wheelchair button or the like to the call registration screen A12, and the user does not need to perform complicated operations, and can simply register a wheelchair call and take the wheelchair-corresponding car.

[0084] In addition, as Figure 5 shown, the attribute registration screen A11 is configured to have a plurality of selection buttons B11 and B12 for selecting the current state of the user, and the attribute information of the wheelchair user is set in the portable terminal 40 through these selection buttons B11 and B12. Therefore, for example, even if the user is not using a wheelchair and is currently injured, by presetting the attribute of the wheelchair user by the selection button B12, when arriving at the landing hall of any building, it is possible to simply register a wheelchair call and take the wheelchair-corresponding car without any special intention.

[0085] In addition, in an elevator that does not have the registration function of a wheelchair call, in order to newly register a wheelchair call, it is necessary to set a wheelchair call button in the landing hall and change the software of the elevator control device. If this system is applied, the wheelchair call can be registered using the user's portable terminal, so it is possible to cope without the improvement of hardware such as setting a wheelchair call button.

[0086] (Modification Example)

[0087] In the above first embodiment, the method of registering "wheelchair call" according to the user's attribute information has been described. However, in the first modification example, the method of registering "reject shared ride call" will be described, and in the second modification example, the method of registering "pet call" will be described. In addition, the detailed description of the components identical to those in the first embodiment will be omitted, and mainly the parts different from the first embodiment will be described here.

[0088] · First Modification Example: Reject Shared Ride Call

[0089] First, the method of registering "reject shared ride call" will be described.

[0090] In the first modification example, the elevator control devices 20a and 20b are provided with a registration function and an operation control function for "reject shared ride call". "Reject shared ride call" means a hall call that can reject sharing with other people on the intermediate floors when the user is on the way to the destination floor.

[0091] For example, in Building 10a, when a reject shared ride call is registered, after the elevator control device 20a makes the passenger car respond to the departure floor of the user, during the period before the passenger car reaches the user's destination floor, the allocation of hall calls registered on other floors is prohibited. That is, it runs directly to the user's destination floor. The same applies to Building 10b. Thus, since other users will not board from the intermediate floors, sharing can be prevented. Such a reject shared ride call is usually registered by operating a reject shared ride call button provided in the hall, but in the first modification example, it can be registered using the user's portable terminal 40.

[0092] In the first modification example, the attribute setting unit 43a performs processing for setting attribute information indicating an attribute of rejecting shared ride. Specifically, the attribute setting unit 43a, through a specified operation of the user, displays an attribute registration screen A13 (refer to Figure 9 ) having a plurality of items (second items) for determining the attribute of rejecting shared ride on the display unit 42, and sets attribute information (second attribute information) indicating that the user is a user who requests to reject shared ride according to the items arbitrarily selected by the user (specifically, stores the attribute information in a readable manner in the storage unit 44).

[0093] Figure 9FIG. is an example showing an attribute registration screen A13. After the application software 40a is started, the attribute registration screen A13 is displayed by a prescribed operation such as clicking on a menu of "user registration" on a main screen (not shown), for example. The attribute registration screen A13 is provided with a plurality of items for determining attributes for rejecting shared rides, and in order to be able to select each of the plurality of items separately, each item has a selection button.

[0094] In Figure 9 the example of, the attribute registration screen A13 includes a selection button B16 and a selection button B17. The selection button B16 is a button for selecting the "concerned about stalking" state (item C). The selection button B17 is a button for selecting the "afraid of sharing an elevator with others" state (item D). The selection buttons B16, B17 can be displayed by a radio button capable of selecting any one of item C and item D, or can be displayed by a checkbox capable of selecting both. In Figure 9 FIG., the case where it is displayed by a radio button and the user has selected item C is shown. In the case where the user has selected at least one of these items, the attribute of "rejecting shared rides" is set. In contrast, in the case where no item is selected, the attribute of "ordinary user" is set. Similarly to the above-described first embodiment, the attribute information is attached to the call information and sent to the server device 30.

[0095] When the server device 30 (operation control unit 32a) receives the call information from the portable terminal 40, it confirms the attribute information attached to the call information. In the case where the attribute information is for rejecting shared rides, the server device 30 replaces the call information registered as a normal hall call (general call) with a reject shared ride call and sends it to the elevator control device of the building where the user is located. For example, if the user is in building 10a, the server device 30 sends a reject shared ride call to the elevator control device 20a.

[0096] Thereby, the elevator control device 20a performs the same processing as in the case where a reject shared ride call button is operated in the hall 12a. That is, the elevator control device 20a selects a passenger car for allocating the reject shared ride call from the passenger cars 11-1a, 11-2a, 11-3a, and after going to the departure floor of the user, prohibits the allocation of hall calls to other floors during the period before the passenger car reaches the destination floor of the user, and performs non-stop operation.

[0097] In addition, if it is considered that the user refuses to share the ride with others, it is preferable that when the passenger car arrives at the floor where the user is waiting for the elevator, there are as few users as possible or no users in the passenger car. Therefore, when selecting the passenger car to which the call for refusing to share the ride is assigned, it is preferable to give priority to selecting the passenger car with the fewest number of passengers or an empty passenger car among the passenger cars 11-1a, 11-2a, and 11-3a.

[0098] In addition, at the floor where the user is waiting for the elevator, when the user takes the passenger car and others enter, in order to refuse to share the ride, a buzzer sound or the like can also be sounded. The entry of others can be detected by, for example, the value of a load sensor provided on the passenger car, the image of a surveillance camera provided in the passenger car or the waiting hall, and the like.

[0099] ·Second modification example: Pet call

[0100] Next, the method of registering a "pet call" will be described.

[0101] In the second modification example, the elevator control devices 20a and 20b have a registration function and a display control function for "pet call". "Pet call" refers to a call from the waiting hall registered by a user with a pet.

[0102] For example, in the building 10a, pet buttons (not shown) are provided in the waiting hall 12a and the passenger cars 11-1a to 11-3a. When a pet call is registered by operating the pet button, the elevator control device 20a displays on the display provided in the waiting hall 12a on each floor that a pet is carried to notify other users in the waiting hall 12a. The same applies to the case where a pet call is registered in the building 10b. Thus, other users who mind sharing the ride with a pet can avoid sharing the ride with the pet. In addition, the display of "pet" may be performed at least in the waiting hall on each floor where it stops during the period when the passenger car responding to the pet call travels to the destination floor of the user carrying the pet. Such a pet call is usually registered by operating a pet call button provided in the waiting hall or the passenger car, but in the second modification example, it can be registered using the user's portable terminal 40.

[0103] In the second modification example, the attribute setting unit 43a performs processing for setting attribute information indicating the attribute of carrying a pet. Specifically, through a prescribed operation of the user, the attribute setting unit 43a displays on the display unit 42 an attribute registration screen A14 (refer to Figure 10 ) having a plurality of items (third items) for determining the attribute of carrying a pet, and based on the items arbitrarily selected by the user, sets attribute information (third attribute information) indicating that the user is a user carrying a pet (specifically, stores the attribute information in a readable manner in the storage unit 44).

[0104] Figure 10 This is a diagram showing an example of the attribute registration screen A14. After the application software 40a is launched, the attribute registration screen A14 is displayed, for example, by performing a prescribed operation such as clicking on the "user registration" menu on the main screen (not shown). The attribute registration screen A14 is provided with a plurality of items for determining the attributes of the pet call. In order to be able to select each of these plurality of items separately, selection buttons are provided for each item.

[0105] In Figure 10 the example of, the attribute registration screen A14 includes a selection button B18 and a selection button B19. The selection button B18 is a button for selecting the "carrying a pet" state (item E). The selection button B19 is a button for selecting the state of "wanting to notify that there is a pet on board the elevator" (item F). The selection buttons B18 and B19 can be displayed by a radio button that can select either item E or item F, or can be displayed by a checkbox that can select both. In Figure 10 it shows the case where it is displayed by a radio button and the user has selected item F. When at least one of these items has been selected by the user, the attribute of "carrying a pet" is set. In contrast, when none of the selection buttons are selected, the attribute of "general user" is set. Similar to the above-described embodiment, the attribute information is attached to the call information and sent to the server device 30.

[0106] If the server device 30 (operation control unit 32a) receives call information from the portable terminal 40, it confirms the attribute information attached to the call information. When the attribute information is that of a user carrying a pet, the server device 30 replaces the call information registered as a normal landing call (general call) with a pet call and sends it to the elevator control device of the building where the user is located. For example, if the user is in building 10a, the server device 30 sends a pet call to the elevator control device 20a.

[0107] Thereby, the elevator control device 20a performs the same processing as in the case of operating the pet call button in the landing hall 12a. That is, the elevator control device 20a selects a passenger car to which the pet call is assigned from the passenger cars 11-1a, 11-1b, and 11-1c, and after going to the departure floor of the user, during the period before the passenger car reaches the destination floor of the user, a display indicating that a pet is being carried is made on a display (not shown) provided in each floor landing hall 12a.

[0108] In addition, in the above-described first and second modified examples, "reject co-riding call" and "pet call" have been described. Other calls such as "voice guidance call" can also be registered in the same way using the user's portable terminal 40.

[0109] The so-called "voice-guided call" refers to the call in the waiting hall registered by the blind user. When registering this voice-guided call, the elevator control device guides by voice, such as the opening and closing of the door, button operations, and the operating status of the passenger car (car position, running direction), etc. Various calls including such voice-guided calls can also be configured to be registered arbitrarily by setting the user's attributes. Hereinafter, calls other than the normal waiting hall call ("wheelchair call", "refusal to share call", "pet call", etc.) will be referred to as specific calls for explanation.

[0110] In addition, it is also possible to register a part or all of multiple specific calls in combination. For example, by displaying the attribute registration screens A11, A13, and A14 on one screen, items that match the user's status can be selected from multiple items (items A to F). In this case, multiple attributes can be included in the attribute information. When multiple attributes are set in the attribute information received from the portable terminal 40, the server device 30 combines and executes operations corresponding to each attribute on the elevator control device in the building where the user is located. For example, when the attribute information includes the attributes of "wheelchair user" and "carrying a pet", the server device 30 causes the elevator control device in the building where the user is located to make the wheelchair-corresponding car respond to the call and display "pet" in the waiting hall.

[0111] In this way, according to the modification example, as the user's attribute information, the user not only sets "wheelchair user" in the portable terminal 40, but also sets other attributes such as "refusal to share" and "carrying a pet", so that calls corresponding to these attributes can be simply registered, and the user can take a passenger car suitable for the user.

[0112] (Second Embodiment)

[0113] In the first embodiment, the method of setting the user's attribute information by the user's portable terminal 40 is described. In the second embodiment, it is different from the first embodiment in that, considering the case where the user forgets to set the attribute information, the user's attribute information is judged by a camera installed in the waiting hall. In addition, the same parts as those in the above first embodiment are denoted by the same reference numerals and the detailed description is omitted. In the following description, the parts different from the first embodiment will be mainly described.

[0114] Regarding the overall configuration of the elevator system, the configuration of the server device 30, and the configuration of the portable terminal 40 in the second embodiment, they are the same as those in the above first embodiment.

[0115] Figure 11This is a diagram showing the functional configuration of the elevator control device 20a according to the second embodiment. In the building 10a, the elevator control device 20a is connected to the camera 24 provided in the landing hall 12a. The control unit 22 has an attribute determination unit 22c, and the processing of the car operation unit 22a is different from that of the first embodiment. In addition, the elevator control device 20b has the same configuration.

[0116] The camera 24 is provided in the landing hall 12a on each floor of the building 10a where the elevator control device 20a is provided, and photographs the users located in the landing hall 12a. As long as it can photograph the users in the landing hall 12a, the camera 24 can be installed anywhere. For example, as Figure 12 shown, the camera 24 is installed facing the landing hall 12a from the side of the landing hall doors 13a to 13c. The images of the users photographed by the camera 24 are sent to the elevator control device 20a in real time and stored in the storage unit 21.

[0117] In addition, the camera 24 does not need to be always on. It can also be configured to turn on the camera 24 only when receiving call information registered as a normal landing hall call (general call) from the server device 30.

[0118] When the attribute determination unit 22c of the control unit 22 receives call information registered as a normal landing hall call (general call) from the server device 30, it analyzes the image of the camera 24 and determines the attributes of the users. In this case, since the attributes of the users are determined by image analysis, attributes related to the mood of the users such as "refusing to ride together" are not within the applicable range, and attributes that can be determined based on the appearance of the users such as "wheelchair user" and "carrying a pet" are applicable.

[0119] Specifically, the attribute determination unit 22c acquires the image of the camera 24 when receiving the call information and analyzes the image. The following methods are used in the above analysis process: a method of extracting the feature amounts of the users in the image and making a determination based on the similarity between the feature amounts and the feature amounts of pre-learned wheelchair users, etc. (wheelchair users, users with crutches, elderly people, pregnant users, etc.) and users carrying pets; a pattern matching method of preparing multiple pattern images of wheelchair users, etc. and users carrying pets in advance and comparing these pattern images with the images of the users obtained from the photographed images.

[0120] When the result of the analysis and processing is that a wheelchair user, a cane user, an elderly person, or a pregnant user is detected in the image, the attribute determination unit 22c determines the attribute of the user as "wheelchair user". In addition, when a user carrying a pet is detected in the image, the attribute determination unit 22c determines the attribute of the user as "carrying a pet".

[0121] The car operation unit 22a receives the determination result of the attribute determination unit 22c, replaces the call information with a specific call, and performs an operation considering the attribute of the user.

[0122] Specifically, when the attribute of the user is "wheelchair user", the call information is replaced with a wheelchair call, and an operation considering the wheelchair user is performed. That is, the car operation unit 22a causes the wheelchair-corresponding car to respond to the wheelchair call.

[0123] In addition, when the attribute of the user is "carrying a pet", the car operation unit 22a replaces the call information with a pet call and performs an operation considering the user carrying a pet. That is, the car operation unit 22a displays "pet" on the landing hall 12a of each floor. When a wheelchair user or a user carrying a pet is not detected in the image, the call information is not replaced, and a passenger car other than the wheelchair-corresponding car is sent to the waiting floor of the user.

[0124] According to the second embodiment like this, in addition to the configuration of the first embodiment described above, by making the elevator control device 20a have a function of judging the attribute of the user using the camera 24, even when the user forgets to set the attribute information in the portable terminal 40, the elevator control device 20a can judge the attribute of the user on its side and perform operation control suitable for the user. In addition, although the building 10a has been described as an example here, the same applies to another building 10b.

[0125] (Third Embodiment)

[0126] Next, the third embodiment will be described.

[0127] In the above first and second embodiments, the portable terminal 40 is provided with an attribute setting function for setting the attribute of the user. When making a call registration using the portable terminal 40, by sending the attribute information of the user to the server device 30, the user can take a passenger car suitable for the user. In contrast, in the third embodiment, it is configured such that the elevator side has a function of judging the attribute of the user, and the attribute information of the user obtained by this function is stored in the server device 30. In addition, the same parts as those in the first and second embodiments described above are denoted by the same reference numerals, and their detailed descriptions are omitted.

[0128] Figure 13FIG. 0 is a block diagram showing the configuration of an elevator control device 20a according to the third embodiment. The elevator control device 20a includes a storage unit 21, a control unit 22, and a communication unit 23. In addition, the elevator control device 20a is connected to a camera 24 provided in the landing 12a on each floor. The photographed image of the user captured by the camera 24 is stored in the storage unit 21 in real time.

[0129] In addition, the camera 24 does not need to be always turned on, and may be configured to turn on the camera 24 only when an attribute request is received from the server device 30. As will be described later, when the attribute of the user is not identified, an attribute request is sent from the server device 30.

[0130] When there is an attribute request from the server device 30 for requesting the attribute of the user, the attribute determination unit 22c analyzes the image of the user captured by the camera 24 to determine the attribute of the user. The image analysis process is the same as that in the second embodiment described above.

[0131] Based on the determination result of the attribute determination unit 22c, the attribute providing unit 22d provides the attribute information of the user to the server device 30. In addition, the configuration of the elevator control device provided in a building where no camera is installed in the landing is the same as Figure 2 the same configuration. In the following description, no camera is installed in the landing 12b of the building 10b, and the elevator control device 20b is the same as Figure 2 the same configuration.

[0132] Figure 14 FIG. 17 is a block diagram showing the configuration of the server device 30 according to the third embodiment.

[0133] The storage unit 31 of the server device 30 includes a building management table 31a and an attribute management table 31b. In the attribute management table 31b, the attribute information of each user is stored in association with the identification information predetermined for each user.

[0134] The control unit 32 includes an operation control unit 32a, an acquisition unit 32b, and an attribute information reading unit 32c.

[0135] When receiving call information from the portable terminal 40, the acquisition unit 32b makes an attribute request to the elevator control device of the building where the user is located, and acquires the attribute information of the user. Specifically, the acquisition unit 32b retrieves the attribute management table 31b based on the identification information of the user sent from the portable terminal 40 together with the call information. When the attribute information of the user is not stored (that is, when the attribute of the user is not determined), an attribute request is made to the elevator control device. The acquisition unit 32b stores the attribute information sent in response to the attribute request in the attribute management table 31b of the storage unit 31 together with the identification information of the user.

[0136] The attribute information reading unit 32c reads the attribute information of the user from the storage unit 31 based on the identification information added to the call information.

[0137] The operation control unit 32a replaces the call information with a specific call (such as a wheelchair call) according to the attribute information read by the attribute information reading unit 32c, and sends it to the elevator control device provided on the building where the user is located, so as to perform an operation considering the attribute of the user.

[0138] In the third embodiment, the portable terminal 40 is configured in the same way as the Figure 4 first embodiment shown, and has an input unit 41, a display unit 42, a control unit 43, a storage unit 44, a communication unit 45, etc. However, in the third embodiment, since the user does not need to use the portable terminal 40 to set attributes, the control unit 43 does not necessarily need the attribute setting unit 43a.

[0139] In addition, when the call registration unit 43b sends call information, the identification information of the user is attached to the call information and sent to the server device 30. The identification information of the user is preset in the portable terminal 40.

[0140] Next, the operation of the third embodiment will be described. Here, it is assumed that the user U holds the portable terminal 40 and comes to the landing 12a on an arbitrary floor of the building 10a (see Figure 1 ). Figure 15A And Figure 15B are flowcharts showing the processing flow of the elevator system of the third embodiment. Figure 15A Shows the processing of the portable terminal 40 and the server device 30, Figure 15B Shows the processing of the elevator control device 20a.

[0141] First, with reference to Figure 15A , the processing flow of the portable terminal 40 and the server device 30 will be described.

[0142] Through a prescribed operation of the user U, it is displayed on the display unit 42 of the portable terminal 40Figure 6 The call registration screen A12 shown (step S31). When each piece of information such as the building, the waiting floor, the destination direction, or the destination floor is input on this call registration screen A12 and the send button B15 is operated (yes in step S32), the portable terminal 40 (call registration unit 43b) generates call information including this information, attaches the identification information of the user U to this call information, and sends it to the server device 30 (step S33).

[0143] When the server device 30 receives the call information and the identification information from the portable terminal 40, it determines whether the attribute information of the user U represented by this identification information is stored in the attribute management table 31b (step S34). When the attribute information of the user U has been stored in the attribute management table 31b, that is, when the attribute of the user U has been determined (yes in step S34), it proceeds to step S38.

[0144] On the other hand, when the attribute information of the user U is not stored in the attribute management table 31b, that is, when the attribute of the user U has not been determined (no in step S34), the server device 30 sends an attribute request to the elevator control device 20a of the building 10a where the user U is located (step S35). As will be described later, the elevator control device 20a accepts this attribute request and determines the attribute of the user U (refer to Figure 15B ).

[0145] When the server device 30 receives the attribute information sent in response to the attribute request from the elevator control device 20a (yes in step S36), it stores (saves) this attribute information in association with the identification information of the user U in the attribute management table 31b (step S37). This is because, when the user U registers a call in the waiting hall by the portable terminal 40 in the building 10a or other buildings, the server device 30 refers to the attribute management table 31b to determine the attribute of the user U.

[0146] Here, the server device 30 determines whether the user U is a wheelchair user based on the attribute information received from the elevator control device 20a (step S38). When the user U is a wheelchair user (yes in step S38), the operation control unit 32a replaces the call information received from the portable terminal 40 with a wheelchair call and sends it to the elevator control device 20a (step S39).

[0147] On the other hand, when the user U is not a wheelchair user, that is, when the user U is a general user (no in step S38), the server device 30 sends it to the elevator control device 20a without replacing the call information (step S40).

[0148] Next, refer to Figure 15BDescribe the processing of the elevator control device 20a.

[0149] When the elevator control device 20a (attribute determination unit 22c) receives an attribute request from the server device 30 (Yes in step S41), it acquires the photographed image of the user U from the storage unit 21 (step S42), and determines (detects) the attribute of the user U by performing analysis processing on this image (step S43). The method of image analysis processing and user U attribute determination performed by the attribute determination unit 22c is the same as that of the second embodiment, so the description is omitted here.

[0150] The elevator control device 20a provides the attribute information of the user U determined (detected) in step S43 to the server device 30 (step S44).

[0151] Hereinafter, it is the same as the Figure 8B processing of the first embodiment shown. That is, when the elevator control device 20a receives a call message (ordinary landing call) or a wheelchair call from the server device 30, it makes the car respond to the floor where the user U is located with an operation corresponding to this call (that is, an operation corresponding to the attribute of the user).

[0152] In addition, although the case where the user U is a "wheelchair user" is described here, for example, when the user U is "carrying a pet", the server device 30 replaces the call message received from the portable terminal 40 with a pet call and sends it to the elevator control device 20a. The elevator control device 20a that receives the pet call is the same as the second modification example of the first embodiment, and performs an operation considering the user carrying a pet.

[0153] In addition, when there are other users in the same landing 12a as the user U, the elevator control device 20a may erroneously detect the attribute information of this user as the attribute information of the user U. Considering such a situation, it is also possible that when the same attribute information is detected a specified number of times, the server device 30 determines this attribute information as the attribute of the user U and stores it in the attribute management table 31b.

[0154] Furthermore, for example, there is a situation where a user U using a wheelchair no longer uses the wheelchair due to injury recovery or the like. Considering such a situation, it is also possible that each time the server device 30 receives a call message of the user U, it stores the attribute information A (wheelchair user) obtained according to the attribute request in a table. Here, it can also be configured that when different attribute information B (general user) is stored in the table due to injury recovery or the like, the server device 30 uses the attribute information B for call message replacement after the attribute information B reaches a specified number of times.

[0155] Thus, according to the third embodiment, by using the camera 24 on the elevator side to determine the user's attributes and sending them to the server device 30, even if the user does not operate the portable terminal 40 to set their own attributes in advance, as long as the user sends a call message to the server device 30 in the waiting hall, the user can ride in the passenger car corresponding to their own attributes.

[0156] In addition, by storing the user's attribute information in association with the user's identification information in the attribute management table 31b on the server device 30 side, when the same user makes a call registration again, even if the elevator control device 20a is not requested for the user's attributes, the server device 30 can refer to the attribute management table 31b to determine the user's attributes. Thus, the replacement from the user's call message to a specific call (such as a wheelchair call) can be performed quickly, and the passenger car suitable for the user can respond.

[0157] Furthermore, once the user's attribute information is stored in the attribute management table 31b, even when the user arrives at the waiting hall of an elevator that does not have the function of determining the user's attributes by the camera 24, the user's attributes can be determined by referring to the attribute management table 31b. Therefore, as described above, the replacement of the user's call message can be performed quickly, and the passenger car suitable for the user can respond.

[0158] According to the elevator system of at least one of the above-described embodiments, in a system that uses a portable terminal for call registration, an elevator system that can simply register calls other than normal waiting hall calls can be provided.

[0159] Although some embodiments of the present invention have been described, these embodiments are given as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other ways, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments, their modifications are included in the scope and gist of the invention, and similarly are included in the invention described in the claims and the scope of equivalents thereof.

Claims

1. An elevator system that uses a user's portable terminal to register a call for an elevator, the elevator system being characterized by comprising: A plurality of elevator control devices, which are provided in each of a plurality of buildings and respectively control the operation of elevators; and a server device that is connected to the plurality of elevator control devices via a communication network, the portable terminal having: an attribute setting unit that sets attribute information indicating the attributes of the user; a storage unit that stores the attribute information set by the attribute setting unit; and a call registration unit that, when the user registers call information in the waiting hall of any of the plurality of buildings, attaches the attribute information stored in the storage unit to the call information and sends it to the server device, the server device having an operation control unit that, when receiving the call information and the attribute information from the portable terminal, replaces the call information with a specific call according to the attribute information and sends it to the elevator control device provided on the any building, thereby performing an operation considering the attributes of the user.

2. The elevator system according to claim 1, characterized in that the attribute setting unit includes an attribute registration screen having a plurality of items for determining the attributes of the user, and sets the attribute information according to the items arbitrarily selected by the user on the attribute registration screen.

3. The elevator system according to claim 2, characterized in that the attribute registration screen is provided with a plurality of first items for determining the attributes of wheelchair users, and when at least one of the plurality of first items is selected, the attribute setting unit sets first attribute information indicating the attributes of the wheelchair user.

4. The elevator system according to claim 3, characterized in that when receiving the first attribute information, the operation control unit sends a wheelchair call as the specific call to the elevator control device, and makes the wheelchair-corresponding car respond to the user.

5. The elevator system according to claim 2, characterized in that the attribute registration screen is provided with a plurality of second items for determining the attributes of those who refuse to share a ride, and when at least one of the plurality of second items is selected, the attribute setting unit sets second attribute information indicating the attributes of those who refuse to share a ride.

6. The elevator system according to claim 5, characterized in that when receiving the second attribute information, the operation control unit sends a call for refusing to share a ride as the specific call to the elevator control device, and prohibits others from sharing the ride in the passenger car in which the user is riding.

7. The elevator system according to claim 2, characterized in that the attribute registration screen is provided with a plurality of third items for determining the attributes of those carrying pets, and when at least one of the plurality of third items is selected, the attribute setting unit sets third attribute information indicating the attributes of those carrying pets.

8. The elevator system according to claim 7, characterized in that When receiving the third attribute information, the operation control unit sends the pet call as the specific call to the elevator control device and notifies the user of the situation of carrying a pet.

9. The elevator system according to claim 1, wherein: When receiving the fourth attribute information indicating the attribute of a general user, the server device sends the call information to the elevator control device. The elevator control device includes: An attribute determination unit that, when receiving the call information, analyzes and processes the image of the camera installed in the landing to determine the attribute of the user. And A car operation unit that receives the determination result of the attribute determination unit, replaces the call information with a specific call, and performs an operation considering the attribute of the user.

10. An elevator system that uses a user's portable terminal to register an elevator call. The elevator system is characterized by having: A plurality of elevator control devices, which are provided in each of a plurality of buildings and respectively control the operation of elevators; And A server device connected to the plurality of elevator control devices via a communication network. The portable terminal has a call registration unit. When the user registers call information in the landing of any of the plurality of buildings, the call registration unit adds the pre-set identification information of the user to the call information and sends it to the server device. The server device has: An acquisition unit that, when receiving the call information from the portable terminal, makes an attribute request to the elevator control device and acquires the attribute information indicating the attribute of the user from the elevator control device. A storage unit that stores the attribute information obtained by the acquisition unit in association with the identification information. An attribute information reading unit that reads the attribute information from the storage unit based on the identification information attached to the call information. And An operation control unit that, according to the attribute information read by the attribute information reading unit, replaces the call information with a specific call and sends it to the elevator control device provided on any of the buildings, thereby performing an operation considering the attribute of the user. The elevator control device has: An attribute determination unit that, when there is an attribute request from the server device, analyzes and processes the image of the camera installed in the landing to determine the attribute of the user. And An attribute providing unit that provides the attribute information to the server device according to the determination result of the attribute determination unit.

11. The elevator system according to claim 10, wherein: When the attribute information is not stored in the storage unit, the acquisition unit makes the attribute request to the elevator control device and acquires the attribute information from the elevator control device.

Images