Elevator system

Abstract

To easily register calls other than normal landing calls in a system that uses a mobile terminal to register calls.SOLUTION: An elevator system according to one embodiment uses a mobile terminal to register calls and comprises a plurality of elevator control devices and a server device. The mobile terminal is equipped with attribute setting means for setting attribute information indicating the attributes of the user, storage means for storing the attribute information, and call registration means for adding the attribute information to call information and sending the same to the server device when the user registers the call information at a landing of any property among a plurality of properties. The server device is equipped with operation control means which, when the server device receives the call information and the attribute information from the mobile terminal, replaces the call information with a specific call, on the basis of the attribute information, and transmits the same to the elevator control device installed in any property, thereby causing the operation to be executed in consideration of the user's attributes.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] Embodiments of the present invention relate to an elevator system.

Background Art

[0002] Generally, a landing call button for registering a landing call is installed at an elevator landing. When the landing call button is operated by an elevator user, the car responds to the landing.

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

[0004] Here, an elevator may be provided with a wheelchair call button for wheelchair users. When a wheelchair call is registered by the wheelchair call button, for example, a car with a long door opening time set responds. As a result, wheelchair users can board the car without haste.

[0005] In the above-described system, the call information transmitted from the portable terminal is treated as a normal landing call. In order to be able to register a wheelchair call separate from a normal landing call, an interface (button, etc.) for wheelchair call registration must be added to the call registration screen.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0007] However, if the number of buttons on the call registration screen is increased, the call registration operation becomes complicated, and there is a possibility that the user cannot register calls smoothly.

[0008] Therefore, the problem to be solved by the present invention is to provide an elevator system that can easily register calls other than normal landing calls in a system that performs call registration using a mobile terminal.

Means for Solving the Problems

[0009] An elevator system according to an embodiment performs call registration of an elevator using a mobile terminal in which call registration application software is installed. The elevator system includes a plurality of elevator control devices installed for each of a plurality of properties and controlling the operation of the elevator respectively, and a server device connected to the plurality of elevator control devices via a communication network. The mobile terminal includes an attribute setting means, a storage means, and a call registration means. The attribute setting means sets attribute information indicating the attributes of the user. The storage means stores the attribute information set by the attribute setting means. When the user registers call information at the landing of any of the plurality of properties, the call registration means adds the attribute information stored in the storage means to the call information and transmits it to the server device. The server device includes an operation control means. When receiving the call information and the attribute information from the mobile terminal, the operation control means replaces the call information with a specific call based on the attribute information and transmits it to the elevator control device installed in the arbitrary property, thereby executing an operation considering the attributes of the user.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8A

Figure 8B

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15A

Figure 15B

Embodiments for Carrying Out the Invention

[0011] Hereinafter, each embodiment will be described with reference to the drawings. Note that the disclosure is merely an example, and the invention is not limited by the contents described in the following embodiments. Modifications that can be easily conceived by those skilled in the art are naturally included in the scope of the disclosure. For the sake of clarity, in the drawings, the sizes, shapes, etc. of each part may be changed and schematically represented with respect to the actual embodiments. In a plurality of drawings, the same reference numerals may be assigned to corresponding elements, and detailed descriptions may be omitted.

[0012] (First Embodiment) FIG. 1 is a diagram showing an example of the configuration of an elevator system according to an embodiment. In the figure, 10a and 10b represent buildings such as office buildings (hereinafter referred to as properties) in which this elevator system is introduced. In each of the properties 10a and 10b, elevator control devices 20a and 20b are installed. In the example of FIG. 1, only two properties 10a and 10b are shown for convenience, but actually there are a large number of properties, and the elevator control devices provided for each of these properties are connected to the server device 30 via a communication network 1 described later so as to be able to communicate with each other. The server device 30 is a computer that centrally manages the elevators in each property.

[0013] The elevator control device 20a controls the operation of the cars (elevators) 11-1a to 11-3a provided in the property 10a. The cars 11-1a to 11-3a are supported so as to be movable up and down on a pair of guide rails erected in the hoistway, and move to each floor in response to landing calls and car calls. A "landing call" is a call signal registered at the landing on each floor and includes information on the registered floor and the destination direction. Also, a "car call" is a call signal registered in the car interior and includes information on the destination floor.

[0014] In this system, as will be described later, each user can register a landing call using the mobile terminal 40 they each possess. Therefore, it is not necessary to operate the landing call buttons (not shown) installed at each landing 12a. In the following description, for the sake of convenience, the landing call registered using the mobile terminal 40 will be referred to as a "smartphone call".

[0015] The elevator control device 20b controls the operation of the car 11b provided in the building 10b. The car 11b is supported so as to be movable up and down on a pair of guide rails erected in the hoistway, and moves to each floor in response to a landing call and a car call.

[0016] The elevator control devices 20a and 20b according to this embodiment are set to be able to register a "wheelchair call" which is different from a normal landing call. A "wheelchair call" is a landing call for calling a wheelchair-compatible car. A wheelchair call is usually registered by a wheelchair call button installed at the landings 12a and 12b, but in this embodiment, as will be described later, a user can register a wheelchair call using the mobile terminal 40.

[0017] Also, the "wheelchair-compatible car" includes, for example, a car with a longer door opening time set than that of a standard-specification car, a car with a slower door opening / closing speed set than that of a standard-specification car, or a car in which a call button and a rearview mirror for wheelchair users are installed in the car interior. When a wheelchair call is registered, the elevator control device 20a that controls the plurality of cars 11-1a to 11-3a causes the car set as the wheelchair-compatible car among the cars 11-1a to 11-3a to respond. Also, when a wheelchair call is registered, the elevator control device 20b that controls one car 11b causes the car 11b to respond as a wheelchair-compatible car. In this case, for example, the door opening time of the car 11b is set longer than normal.

[0018] 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 executing processes related to smartphone calls in cooperation with the elevator control devices 20a and 20b.

[0019] The mobile terminal 40 used for smartphone calls is a general mobile phone, smartphone, etc. An application software 40a for call registration is installed in advance in the mobile terminal 40. This application software 40a for call registration is developed by an elevator-related company and can be freely downloaded from a website dependent on the OS (Operating System) of the mobile terminal 40. The user registers a smartphone call via the server device 30 on the Internet by performing a predetermined operation on the call registration screen (see FIG. 6) of this application software 40a.

[0020] FIG. 2 is a block diagram showing the configuration of the elevator control device 20a according to the present embodiment. Note that the elevator control device 20b also has the same configuration as that in FIG. 2.

[0021] The elevator control device 20a includes a storage unit 21, a control unit 22, and a communication unit 23. The storage unit 21 stores various programs and information necessary for the processing of the control unit 22. In the present embodiment, the storage unit 21 has a call management table 21a. The call management table 21a stores the landing calls (including smartphone calls) registered at the landings 12a on each floor together with the information of the registered floors, and stores the information of the car to which these calls are assigned.

[0022] The control unit 22 is a part that executes various processes necessary for the operation of the cars 11-1a to 11-3a when the program is started. The control unit 22 has a car operation unit 22a and a door opening / closing control unit 22b.

[0023] The car operation unit 22a controls the operation of the cars 11-1a to 11-3a. Specifically, the car operation unit 22a assigns and responds to any one of the cars 11-1a to 11-3a to the landing calls stored in the call management table 21a, and directs the car to the destination floor of the user. Note that the car operation unit 22a responds to wheelchair calls with the car set as a wheelchair-compatible car.

[0024] The door opening / closing control unit 22b controls the opening and closing operation of the car door when the cars 11-1a to 11-3a arrive at the landing 12a. Specifically, when the door opening / closing control unit 22b detects that any one of the cars 11-1a to 11-3a has landed on the landing 12a by a landing detection device (not shown), the car door of the car is moved in the door-opening direction to fully open. Then, after a predetermined time has elapsed, the door opening / closing control unit 22b moves the car door of the car in the door-closing direction to fully close. Also, the landing door moves in the same direction as the movement of the car door. Note that when the car that has landed on the landing 12a is a wheelchair-compatible car, the predetermined time from when the car door fully opens to when it fully closes is set longer. Alternatively, the door opening / closing speed of the wheelchair-compatible car is set slower. The communication unit 23 performs communication processing between the elevator control device 20a and the server device 30.

[0025] Figure 3 is a block diagram showing the configuration of the server device 30 according to the present embodiment. 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 necessary for the processing of the control unit 32. The storage unit 31 has a property management table 31a that stores property information. The property information includes, for each of the properties 10a and 10b, the property name (or identification information of the property) and information on the elevator control device installed in the property.

[0026] The control unit 32 is a part that controls the entire server device 30, and in the present embodiment, has an operation control unit 32a for executing processing related to smartphone calls.

[0027] When the server device 30 receives call information and attribute information from the mobile terminal 40, the operation control unit 32a replaces the call information with specific call information based on the attribute information and transmits it to the elevator control device installed in the property where the user is located, thereby causing the elevator to perform an operation considering the user's attributes. Note that the "call information" is information including the property where the user is located, the boarding floor, and the destination direction (or the 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 mobile terminal 40.

[0028] FIG. 4 is a block diagram showing the configuration of the mobile terminal 40 according to the present embodiment. The mobile terminal 40 is provided with an input unit 41, a display unit 42, a control unit 43, a storage unit 44, a communication unit 45, and the like.

[0029] The input unit 41 includes various keys and buttons, and inputs data and gives instructions. The display unit 42 is composed of, for example, an LCD and displays data. Note that, as the input unit 41, for example, a transparent touch panel may be used, and data input and instructions may be given on the screen of the display unit 42.

[0030] The control unit 43 is composed of a CPU and executes various functions by starting a predetermined program. In the present embodiment, when the call registration application software 40a installed in the mobile terminal 40 in advance is started, the control unit 43 executes the processes of the attribute setting unit 43a and the call registration unit 43b.

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

[0032] The call registration unit 43b performs a process for registering the call information of the user. Specifically, the call registration unit 43b displays a call registration screen A12 (see FIG. 6) on the display unit 42 by a predetermined operation of the user, and transmits the call information input on this call registration screen A12 to the server device 30. At this time, the call registration unit 43b reads out the attribute information of the user from the storage unit 44, and adds the attribute information to the call information and transmits it (see FIG. 7).

[0033] The storage unit 44 stores various programs necessary for the processing of the control unit 43 and various applications including the application software 40a. The storage unit 44 also stores the attribute information of the user set by the attribute setting unit 43a. The communication unit 45 performs communication processing between the mobile terminal 40 and the server device 30.

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

[0035] FIG. 5 is a diagram showing an example of the attribute registration screen A11. The attribute registration screen A11 is displayed by a predetermined operation such as tapping the "user registration" menu 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 the attributes of wheelchair use, and each item is provided with a selection button so that each of the plurality of items can be selected.

[0036] In the example of FIG. 5, the attribute registration screen A11 is provided with a selection button B11 and a selection button B12. The selection button B11 is a button for selecting the state of "using a wheelchair" (item A). The selection button B12 is a button for selecting the state of "being injured" (item B). The selection buttons B11 and B12 may be displayed as radio buttons that can select any one of item A and item B, or may be displayed as check boxes that can select both. FIG. 5 shows a case where it is displayed as a radio button and item A is selected by the user. When at least one of these items is selected by the user, the attribute of "wheelchair user" is set. On the other hand, when none of the selection buttons is selected, the attribute of "general user" (fourth attribute information) is set.

[0037] Note that the items displayed on the attribute registration screen A11 are not limited to the example of FIG. 5, and items for selecting the state of a user who requires a wheelchair-compatible basket may be further displayed. For example, items indicating that a walking stick is being used, being elderly, being pregnant, etc. may be displayed so as to be selectable.

[0038] FIG. 6 is a diagram showing an example of a call registration screen A12. The call registration screen A12 is displayed by a predetermined operation such as tapping the "call registration" menu on a main screen (not shown) after the application software 40a is launched.

[0039] The call registration screen A12 includes a property selection button B13, a boarding floor input form F11, a destination floor input form F12, a destination direction button B14, and a transmission button B15.

[0040] The property selection button B13 is a button for selecting the property where the user is located. When the property selection button B13 is tapped, a list of each property available for use in this elevator system is displayed, and it is configured to select an arbitrary property from the list. In the example of FIG. 6, "Building A" is selected.

[0041] The boarding floor input form F11 is an input form for users to enter the boarding floor. When the boarding floor input form F11 is tapped, a keypad (not shown in the figure) is displayed on the screen. The user can enter the boarding floor by operating this keypad. In the example of FIG. 6, "2nd floor" is entered. Note that the input method for the user's boarding floor is not limited to the keypad method as shown in the example of FIG. 6. For example, when an arbitrary property is selected by the property selection button B13, a floor list of the property may be displayed, and the user may select the floor as the boarding floor from the floor list.

[0042] The destination direction button B14 is a button for the user to select the upward or downward direction as the destination direction. FIG. 6 shows the case where the upward direction is selected. Note that instead of selecting the user's destination direction by the destination direction button B14, the user may directly enter the destination floor in the destination floor input form F12. In this case, the entered destination floor is treated as a car call. Therefore, when the user gets on the elevator car, there is no need to register the destination floor by operating the operation panel in the car.

[0043] The send button B15 is a button for confirming each piece of information (property, boarding floor, destination direction, or destination floor) entered on the call registration screen A12 and sending it to the server device 30. When the send button B15 is tapped, this information is sent to the server device 30 in a predetermined format together with the attribute information as the user's call information.

[0044] FIG. 7 is a diagram schematically showing the configuration of the call information and the attribute information sent to the server device 30. As shown in FIG. 7, the call information includes the "property name" entered by the property selection button B13 on the call registration screen A12, the "boarding floor" entered by the boarding floor input form F11, and the "destination direction" selected by the destination direction button B14. Note that when the destination floor is entered 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.

[0045] Here, the "attribute information" is read from the storage unit 44 of the mobile terminal 40 when the transmission button B15 is tapped, added to the call information, and transmitted to the server device 30.

[0046] Next, the operation of the first embodiment will be described. Here, it is assumed that the user U has come to the landing 12a on an arbitrary floor of the property 10a with the mobile terminal 40 (see FIG. 1). It is assumed that the attribute information of the user U is stored in advance in the storage unit 44 of the mobile terminal 40 through the attribute registration screen A11 shown in FIG. 5.

[0047] FIGS. 8A and 8B are flowcharts showing the processing flow of the elevator system according to the first embodiment. FIG. 8A shows the processing of the mobile terminal 40 and the server device 30, and FIG. 8B shows the processing of the elevator control device 20a.

[0048] First, with reference to FIG. 8A, the processing flow of the mobile terminal 40 and the server device 30 will be described. By a predetermined operation of the user U, the call registration screen A12 shown in FIG. 6 is displayed on the display unit 42 of the mobile terminal 40 (step S11). When each piece of information such as the property, boarding floor, destination direction, or destination floor is input on this call registration screen A12 and the transmission button B15 is operated (YES in step S12), the mobile terminal 40 (call registration unit 34b) generates call information including these pieces of information, adds attribute information to the call information, and transmits it to the server device 30 in the format shown in FIG. 7 (step S13).

[0049] When the server device 30 (control unit 32) receives the call information and the attribute information from the mobile 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 information received from the mobile terminal 40 with a wheelchair call.

[0050] Note that "replacing the call information with a wheelchair call" includes requesting the elevator control device to handle the call information as a wheelchair call. More specifically, it is to change the code signal indicating the call information registered as a normal landing call (general call) to the code signal indicating the wheelchair call registered by pressing the wheelchair call button.

[0051] The server device 30 transmits the wheelchair call to the elevator control device 20a installed in the building 10a where the user U is located (step S15). Specifically, the server device 30 identifies the building 10a where the user U is located from the building information included in the call information, refers to the building management table 31a, and transmits the wheelchair call to the elevator control device 20a corresponding to the building 10a.

[0052] On the other hand, when the user U is not a wheelchair user but a general user (NO in step S14), the server device 30 transmits the call information to the elevator control device 20a without replacement (step S16).

[0053] Next, with reference to FIG. 8B, the processing flow of the elevator control device 20a will be described. 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 manner as the wheelchair call registered by pressing a wheelchair call button (not shown) (step S18). The elevator control device 20a (the car operation unit 22a) assigns the wheelchair call to the car set as the wheelchair-compatible car among the cars 11-1a, 11-2a, and 11-3a, and makes it go to the floor where the user U is waiting (step S19).

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

[0055] In addition, in FIGS. 8A and 8B, the case where the user U makes a call registration at the property 10a has been described by way of assumption. However, the same applies to the case where the user U makes a call registration at the property 10b. That is, the normal call information registered by the mobile terminal 40 is replaced with a wheelchair call according to the attribute information and sent to the elevator control device 20b of the property 10b where the user U is located. When the elevator control device 20b receives the wheelchair call, it directs the car 11b as a wheelchair-compatible car to the floor where the user U is waiting.

[0056] Thus, according to the first embodiment, if the attribute information indicating that the user is a wheelchair user is set in advance in the user's mobile terminal 40, the normal call information registered by a normal operation is replaced with a wheelchair call and sent to the elevator control device of the property where the user is located. Therefore, improvements such as adding a wheelchair button to the call registration screen A12 are unnecessary, and the user can easily register a wheelchair call and board a wheelchair-compatible car without requiring complicated operations.

[0057] Also, as shown in Fig. 5, the attribute registration screen A11 has a plurality of selection buttons B11 and B12 for selecting the current state of the user. Through these selection buttons B11 and B12, the attribute information of the wheelchair user is configured to be set in the mobile terminal 40. Therefore, for example, even if the user is not using a wheelchair but is currently injured, by setting the attribute of the wheelchair user through the selection button B12, when the user comes to the boarding area of any property, the wheelchair call can be easily registered without special awareness, and the user can board the wheelchair-compatible basket.

[0058] In an elevator that does not have a wheelchair call registration function, in order to newly register a wheelchair call, it is necessary to install a wheelchair call button at the boarding area and change the software of the elevator control device. By applying this system, since the wheelchair call can be registered using the user's mobile terminal, it can be dealt with without the need for hardware improvements such as installing a wheelchair call button.

[0059] (Modification example) In the first embodiment described above, the form of registering a "wheelchair call" according to the user's attribute information has been described. In the first modification example, the form of registering a "ride refusal call" and in the second modification example, the form of registering a "pet call" will be described. Regarding the components similar to those in the first embodiment, the detailed description thereof will be omitted, and here mainly the parts different from the first embodiment will be described.

[0060] ·First modification example: Ride refusal call First, the form of registering a "ride refusal call" will be described. In the first modification example, it is assumed that the elevator control devices 20a and 20b are equipped with a registration function and an operation control function for a "ride refusal call". A "ride refusal call" is a boarding call that allows the user to refuse sharing a ride with others on the intermediate floors until reaching the destination floor.

[0061] For example, in the building 10a, when a ride-sharing rejection call is registered, the elevator control device 20a makes the car respond to the user's departure floor, and then prohibits the assignment of landing calls registered on other floors until the car arrives at the user's destination floor. That is, it makes a direct operation to the user's destination floor. The same applies to the building 10b. This can prevent ride-sharing because other users cannot board from intermediate floors. Such a ride-sharing rejection call is usually registered by operating a ride-sharing rejection call button installed at the landing. However, in the first modification example, it can be registered using the user's mobile terminal 40.

[0062] In the first modification example, the attribute setting unit 43a performs a process for setting attribute information indicating the attribute of ride-sharing rejection. Specifically, the attribute setting unit 43a displays an attribute registration screen A13 (see FIG. 9) having a plurality of items (second items) for determining the attribute of ride-sharing rejection on the display unit 42 by a predetermined operation of the user, and based on the items arbitrarily selected by the user, sets attribute information (second attribute information) indicating that the user is a user who requests ride-sharing rejection (specifically, stores this attribute information in the storage unit 44 so that it can be read).

[0063] FIG. 9 is a diagram showing an example of the attribute registration screen A13. The attribute registration screen A13 is displayed on the display unit 42 by a predetermined operation such as tapping the "user registration" menu on a main screen (not shown) after the application software 40a is started. The attribute registration screen A13 is provided with a plurality of items for determining the attribute of ride-sharing rejection, and each item is provided with a selection button so that each of the plurality of items can be selected.

[0064] In the example of FIG. 9, the attribute registration screen A13 is provided with a selection button B16 and a selection button B17. The selection button B16 is a button for selecting the state of "being troubled by a stalker" (item C). The selection button B17 is a button for selecting the state of "being afraid of sharing an elevator with others" (item D). The selection buttons B16 and B17 may be displayed as radio buttons that can select any one of item C and item D, or may be displayed as check boxes that can select both. FIG. 9 shows the case where they are displayed as radio buttons and item C is selected by the user. When at least one of these items is selected by the user, the attribute of "ride rejection" is set. On the contrary, when none of the items is selected, the attribute of "general user" is set. The attribute information is added to the call information and transmitted to the server device 30 in the same manner as in the first embodiment described above.

[0065] When the server device 30 (operation control unit 32a) receives call information from the mobile terminal 40, it checks the attribute information added to the call information. When the attribute information is ride rejection, the server device 30 replaces the call information registered as a normal landing call (general call) with a ride rejection call and transmits 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 ride rejection call to the elevator control device 20a.

[0066] Thereby, the elevator control device 20a executes the same processing as when the ride rejection call button is operated at the landing 12a. That is, the elevator control device 20a selects a car to which the ride rejection call is assigned from among the cars 11-1a, 11-2a, and 11-3a, directs it toward the departure floor of the user, and then prohibits the assignment of landing calls to other floors until the car arrives at the destination floor of the user, and performs a direct operation.

[0067] In consideration of the user rejecting co-riding with others, when the car reaches the floor where the user is located, it is preferably ensured that the user is not in the car as much as possible. Therefore, when selecting a car to which a co-riding rejection call is assigned, it is preferable to preferentially select the car with the fewest number of passengers among cars 11-1a, 11-2a, and 11-3a, or an empty car.

[0068] Also, when the user boards the car on the floor where the user is located and another person gets in, in order to reject co-riding, a buzzer sound or the like may be emitted. The entry of another person can be detected, for example, by the value of a load sensor installed in the car or the image of a surveillance camera installed inside the car or at the landing.

[0069] ·Second Modification Example: Pet Call Next, the form of registering a "pet call" will be described. In the second modification example, it is assumed that the elevator control devices 20a and 20b are provided with a registration function and a display control function for a "pet call". A "pet call" is a landing call registered by a user accompanied by a pet.

[0070] For example, in building 10a, pet buttons (not shown) are provided in landing 12a and cars 11-1a to 11-3a. When a pet call is registered by operating this pet button, the elevator control device 20a displays that the user is accompanied by a pet on the display installed at each floor landing 12a to notify other users at that landing 12a. The same applies when a pet call is registered in building 10b. This allows other users who are concerned about co-riding with a pet to avoid sharing a ride with the pet. Note that the display of "pet" may be performed at least at each floor landing where the car that responds to the pet call stops while heading to the floor where the user accompanied by the pet is going. Such a pet call is usually registered by operating a pet call button installed at the landing or in the car, but in the second modification example, it can be registered using the user's mobile terminal 40.

[0071] In the second modification example, the attribute setting unit 43a performs a process for setting attribute information indicating the attribute of a person with a pet. Specifically, the attribute setting unit 43a displays, on the display unit 42, an attribute registration screen A14 (see FIG. 10) having a plurality of items (third items) for determining the attribute of a person with a pet by a predetermined operation of the user, and based on the items arbitrarily selected by the user, sets attribute information (third attribute information) indicating that the user is a user with a pet (specifically, stores this attribute information in a readable manner in the storage unit 44).

[0072] FIG. 10 is a diagram showing an example of the attribute registration screen A14. The attribute registration screen A14 is displayed on the display unit 42 by a predetermined operation such as tapping a "user registration" menu on a main screen (not shown) after the application software 40a is started. The attribute registration screen A14 is provided with a plurality of items for determining the attribute of a pet call, and is provided with selection buttons for each item so that each of the plurality of items can be selected.

[0073] In the example of FIG. 10, the attribute registration screen A14 is provided with a selection button B18 and a selection button B19. The selection button B18 is a button for selecting the state of "carrying a pet" (item E). The selection button B19 is a button for selecting the state of "wanting to notify that a pet is riding in the elevator" (item F). The selection buttons B18 and B19 may be displayed as radio buttons that can select either one of item E and item F, or may be displayed as check boxes that can select both. FIG. 10 shows a case where it is displayed as a radio button and item F is selected by the user. When at least one of these items is selected by the user, the attribute of "person with a pet" is set. On the other hand, when none of the selection buttons is selected, the attribute of "general user" is set. The attribute information is added to the call information and transmitted to the server device 30 in the same manner as in the above-described embodiment.

[0074] When the server device 30 (operation control unit 32a) receives call information from the mobile terminal 40, it checks the attribute information added to the call information. If the attribute information indicates a user with a pet, the server device 30 replaces the call information registered as a normal landing call (general call) with a pet call and transmits 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.

[0075] Thereby, the elevator control device 20a executes the same processing as when the pet call button is operated at landing 12a. That is, the elevator control device 20a selects a car to which the pet call is assigned from cars 11-1a, 11-1b, and 11-1c, directs it toward the departure floor of the user, and then displays a sign for users with pets on a display (not shown) installed at each floor landing 12a until the car arrives at the destination floor of the user.

[0076] In the first and second modified examples described above, "ride-sharing rejection call" and "pet call" have been described. However, other calls such as "voice guidance call" can also be registered in the same way using the user's mobile terminal 40.

[0077] A "voice guidance call" is a landing call registered by a visually impaired user. When this voice guidance call is registered, the elevator control device provides voice guidance on, for example, door opening and closing, button operations, and the operating state of the car (car position and operating direction). It may be configured such that various calls, including such voice guidance calls, can be arbitrarily registered by setting the attributes of the user. Hereinafter, calls other than normal landing calls ("wheelchair call", "ride-sharing rejection call", "pet call", etc.) will be described as specific calls.

[0078] Further, some or all of a plurality of specific calls may be combinable for registration. For example, by displaying the attribute registration screens A11, A13, and A14 on one screen, it may be possible to select items (items A to F) suitable for the user's state from a plurality of items. In this case, the attribute information may include a plurality of attributes. When a plurality of attributes are set in the attribute information received from the mobile terminal 40, the server device 30 causes the elevator control device of the building where the user is located to execute a combined operation according to each attribute. For example, when the attributes of "wheelchair user" and "accompanied by a pet" are included as attribute information, the server device 30 causes the elevator control device of the building where the user is located to respond to the call with a wheelchair-compatible car and display "pet" at the landing.

[0079] As described above, according to the modification example, the user can easily register calls according to these attributes by setting not only "wheelchair user" but also other attributes such as "ride refusal" and "accompanied by a pet" in the mobile terminal 40 as the user's attribute information, and can board a car suitable for the user.

[0080] (Second Embodiment) In the first embodiment, the form in which the user's attribute information is set by the user's mobile terminal 40 has been described. In the second embodiment, it is different from the first embodiment in that the user's attribute information is also determined by a camera installed at the landing in consideration of the case where the user forgets to set the attribute information. Note that the same reference numerals are given to the same parts as those in the first embodiment described above, and detailed description thereof is omitted. In the following description, the parts different from the first embodiment will be mainly described.

[0081] The overall configuration of the elevator system according to the second embodiment, the configuration of the server device 30, and the configuration of the mobile terminal 40 are the same as those in the first embodiment described above. FIG. 11 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 different from that of the first embodiment in that it is connected to the camera 24 installed in the landing 12a, the control unit 22 has an attribute determination unit 22c, and the processing of the car operation unit 22a. Note that the elevator control device 20b has the same configuration.

[0082] The camera 24 is installed at the landing 12a on each floor of the building 10a where the elevator control device 20a is installed, and photographs the users in the landing 12a. The installation position of the camera 24 may be anywhere as long as it can photograph the users in the landing 12a. For example, as shown in FIG. 12, the camera 24 is installed toward the landing 12a from the side of the landing doors 13a to 13c. The image of the user photographed by the camera 24 is transmitted to the elevator control device 20a in real time and stored in the storage unit 21.

[0083] Note that the camera 24 does not need to be always ON, and may be configured to be turned ON only when the elevator control device 20a receives call information registered as a normal landing call (general call) from the server device 30.

[0084] When the attribute determination unit 22c of the control unit 22 receives call information registered as a normal landing call (general call) from the server device 30, it analyzes the image of the camera 24 to determine the attribute of the user. In this case, since the attribute of the user is determined by image analysis, attributes related to the feelings of the user such as "companion refusal" are not subject to determination, and attributes that can be determined from the appearance of the user such as "wheelchair user" and "pet owner" are subject to determination.

[0085] Specifically, when the call information is received, the attribute determination unit 22c acquires the image of the camera 24 and analyzes the image. The above analysis process includes extracting the feature amount of the user on the image and determining from the similarity between the feature amount and the feature amounts of wheelchair users, cane users, elderly people, pregnant users, etc. (wheelchair users, cane users, elderly people, pregnant users, etc.) and users with pets in advance, or preparing several types of pattern images of wheelchair users, etc. and users with pets, and using a pattern matching method to compare these pattern images with the user image obtained from the captured image.

[0086] As a result of the analysis process, when the attribute determination unit 22c detects a wheelchair user, a cane user, an elderly person, or a pregnant user on the image, it determines that the user's attribute is "wheelchair user". In addition, when the attribute determination unit 22c detects a user with a pet on the image, it determines that the user's attribute is "with pet".

[0087] Receiving the determination result of the attribute determination unit 22c, the car operation unit 22a replaces the call information with a specific call and executes an operation considering the user's attribute. Specifically, when the user's attribute 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 responds to the wheelchair call with a wheelchair-compatible car.

[0088] In addition, when the user's attribute is "with pet", the car operation unit 22a replaces the call information with a pet call and performs an operation considering the user with a pet. That is, the car operation unit 22a displays "pet" on the landing 12a of each floor. When a wheelchair user or a user with a pet is not detected on the image, without replacing the call information, a car other than the wheelchair-compatible car is directed to the floor where the user is waiting.

[0089] According to the second embodiment as described above, in addition to the configuration of the first embodiment, by providing the elevator control device 20a with a function of determining the user's attributes using the camera 24, even when the user forgets to set the attribute information in the mobile terminal 40, the elevator control device 20a can determine the user's attributes and perform driving control suitable for the user. Here, the property 10a has been described as an example, but the same applies to other properties 10b.

[0090] (Third Embodiment) Next, the third embodiment will be described. In the first and second embodiments described above, the mobile terminal 40 is provided with an attribute setting function for setting the user's attributes, and when performing call registration using the mobile terminal 40, the user's attribute information is sent to the server device 30 so that the user can board a car suitable for the user. On the other hand, in the third embodiment, the elevator side is provided with a function of determining the user's attributes, and the user's attribute information obtained by this function is held in the server device 30. Note that the same parts as those in the first and second embodiments described above are denoted by the same reference numerals, and detailed descriptions thereof are omitted.

[0091] FIG. 13 is a block diagram showing the configuration of the 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. The elevator control device 20a is also connected to a camera 24 installed at the landing 12a on each floor. The photographed image of the user by the camera 24 is stored in the storage unit 21 in real time.

[0092] Note that the camera 24 does not need to be always ON, and may be configured to be turned ON only when an attribute request is received from the server device 30. As will be described later, the attribute request is sent from the server device 30 when the user's attributes are not known.

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

[0094] The attribute providing unit 22d provides the server device 30 with the attribute information of the user according to the determination result by the attribute determination unit 22c. Note that the configuration of the elevator control device installed in a property where no camera is installed at the landing is the same as the configuration shown in FIG. 2. In the following description, it is assumed that no camera is installed at the landing 12b of the property 10b, and the elevator control device 20b has the same configuration as that shown in FIG. 2.

[0095] FIG. 14 is a block diagram showing the configuration of the server device 30 according to the third embodiment. The storage unit 31 of the server device 30 has a property management table 31a and an attribute management table 31b. In the attribute management table 31b, the attribute information for each user is stored in association with the identification information determined in advance for each user.

[0096] The control unit 32 includes an operation control unit 32a, an acquisition unit 32b, and an attribute information reading unit 32c. When the acquisition unit 32b receives call information from the mobile terminal 40, it makes an attribute request to the elevator control device of the property where the user is located, and acquires the attribute information of the user. Specifically, the acquisition unit 32b searches the attribute management table 31b based on the identification information of the user sent together with the call information from the mobile terminal 40, and makes an attribute request to the elevator control device when the attribute information of the user is not stored (that is, when the attributes of the user are not known). The acquisition unit 32b stores the attribute information sent in response to the attribute request together with the identification information of the user in the attribute management table 31b of the storage unit 31.

[0097] 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. Based on the attribute information read by the attribute information reading unit 32c, the operation control unit 32a replaces the call information with a specific call (such as a wheelchair call), and transmits it to the elevator control device installed in the property where the user is located, so as to execute an operation considering the user's attributes.

[0098] In the third embodiment, the mobile terminal 40 includes an input unit 41, a display unit 42, a control unit 43, a storage unit 44, a communication unit 45, etc., in the same configuration as that of the first embodiment shown in FIG. 4. However, in the third embodiment, since it is not necessary for the user to set attributes using the mobile terminal 40, the control unit 43 does not necessarily require an attribute setting unit 43a.

[0099] Also, when transmitting the call information, the call registration unit 43b adds the user's identification information to this call information and transmits it to the server device 30. The user's identification information is set in the mobile terminal 40 in advance.

[0100] Next, the operation of the third embodiment will be described. Here, it is assumed that the user U comes to the landing 12a on an arbitrary floor of the property 10a with the mobile terminal 40 (see FIG. 1). FIGS. 15A and 15B are flowcharts showing the processing flow of the elevator system according to the third embodiment. FIG. 15A shows the processing of the mobile terminal 40 and the server device 30, and FIG. 15B shows the processing of the elevator control device 20a.

[0101] First, referring to FIG. 15A, the processing flow of the mobile terminal 40 and the server device 30 will be described. By a predetermined operation of the user U, the call registration screen A12 shown in FIG. 6 is displayed on the display unit 42 of the mobile terminal 40 (step S31). When the information on the property, boarding floor, destination direction, or destination floor is input on this call registration screen A12 and the send button B15 is operated (YES in step S32), the mobile terminal 40 (call registration unit 43b) generates call information including these information, adds the identification information of the user U to the call information, and transmits it to the server device 30 (step S33).

[0102] When the server device 30 receives call information and identification information from the mobile terminal 40, it determines whether the attribute information of the user U indicated by the identification information is stored in the attribute management table 31b (step S34). If the attribute information of the user U is already stored in the attribute management table 31b, that is, if the attribute of the user U is known (YES in step S34), the process proceeds to step S38.

[0103] On the other hand, if the attribute information of the user U is not stored in the attribute management table 31b, that is, if the attribute of the user U is unknown (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, upon receiving this attribute request, the elevator control device 20a determines the attribute of the user U (see FIG. 15B).

[0104] 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 associates the attribute information with the identification information of the user U and holds (stores) it in the attribute management table 31b (step S37). This is to enable the server device 30 to refer to the attribute management table 31b to determine the attribute of the user U when the user U registers a landing call from the mobile terminal 40 in the building 10a or another building.

[0105] 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). If the user U is a wheelchair user (YES in step S38), the driving control unit 32a replaces the call information received from the mobile terminal 40 with a wheelchair call and sends it to the elevator control device 20a (step S39).

[0106] On the other hand, if the user U is not a wheelchair user, that is, if the user U is a general user (NO in step S38), the server device 30 sends the call information to the elevator control device 20a without replacement (step S40).

[0107] Next, with reference to FIG. 15B, the processing of the elevator control device 20a will be described. 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 captured image of the user U from the storage unit 21 (step S42), and determines (detects) the attribute of the user U by analyzing the image (step S43). Since the method of image analysis processing and user U attribute determination by the attribute determination unit 22c is the same as that of the second embodiment, the description thereof is omitted here. 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).

[0108] Thereafter, it is the same as the processing of the first embodiment shown in FIG. 8B. That is, when the elevator control device 20a receives call information (ordinary landing call) or a wheelchair call from the server device 30, it responds the car to the floor where the user U is located by driving according to the call (that is, driving according to the attribute of the user).

[0109] Here, the case where the user U is a "wheelchair user" is assumed for explanation. However, for example, when the user U is a "pet owner", the server device 30 replaces the call information received from the mobile terminal 40 with a pet call and transmits it to the elevator control device 20a. The elevator control device 20a that has received the pet call performs driving considering the user with a pet in the same manner as the second modification example of the first embodiment.

[0110] Also, when there is another user in the same landing 12a as the user U, the elevator control device 20a may erroneously detect the attribute information of that user as the attribute information of the user U. Considering such a case, the server device 30 may determine the attribute information as the attribute of the user U and store it in the attribute management table 31b when the same attribute information is detected a predetermined number of times.

[0111] Furthermore, for example, a user U who was using a wheelchair may no longer need to use the wheelchair due to recovery from an injury or the like. Considering such a case, each time the server device 30 receives the call information of the user U, it may store the attribute information A (wheelchair user) obtained by the attribute request in a table. Here, when attribute information B (general user), which is different from the attribute information A, is stored in the table due to recovery from an injury or the like, the server device 30 may be configured to replace the call information using the attribute information B after the attribute information B reaches a predetermined number of times.

[0112] As described above, according to the third embodiment, by determining the attribute of the user using the camera 24 on the elevator side and sending it to the server device 30, the user can board the car according to their attribute only by sending the call information to the server device 30 at the landing without having to set their attribute in advance by operating the mobile terminal 40.

[0113] In addition, by storing the attribute information of the user in the attribute management table 31b on the server device 30 side in association with the identification information of the user, when the same user registers a call again, the server device 30 can determine the attribute of the user by referring to the attribute management table 31b without asking the elevator control device 20a for the attribute of the user. As a result, the call information of the user can be quickly replaced with a specific call (such as a wheelchair call), and a car suitable for the user can be responded to.

[0114] Furthermore, once the attribute information of the user is stored in the attribute management table 31b, even if the user comes to the landing of an elevator that does not have a function of determining the attribute of the user with the camera 24, the attribute of the user can be determined by referring to the attribute management table 31b. Therefore, similar to the above, the call information of the user can be quickly replaced, and a car suitable for the user can be responded to.

[0115] According to at least one of the above-described embodiments, in a system for performing call registration using a mobile terminal, an elevator system that can easily register calls other than normal landing calls can be provided.

[0116] Although some embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalent scope thereof.

Explanation of Reference Numerals

[0117] 1... Communication network, 10a, 10b... Premises, 12a, 12b... Landing, 20a, 12b... Elevator control device, 21... Storage unit, 21a... Call management table, 22... Control unit, 22a... Car operation unit, 22b... Door opening / closing control unit, 22c... Attribute determination unit, 22d... Attribute providing unit, 23... Communication unit, 24... Camera, 30... Server device, 31... Storage unit, 31a... Premises management table, 31b... Attribute management table, 32... Control unit, 32a... Operation control unit, 32b... Acquisition unit, 32c... Attribute information reading unit, 33... Communication unit, 40... Mobile terminal, 40a... Application software, 41... Input unit, 42... Display unit, 43... Control unit, 43a... Attribute setting unit, 43b... Call registration unit, 44... Storage unit, 45... Communication unit, A11, A13, A14... Attribute registration screen, A12... Call registration screen.

Claims

1. In an elevator system that performs call registration for an elevator using a user's mobile terminal, a plurality of elevator control devices installed for each of a plurality of properties, each controlling the operation of an elevator; a server device connected to the plurality of elevator control devices via a communication network, wherein the mobile terminal has attribute setting means for setting attribute information indicating the attributes of the user; storage means for storing the attribute information set by the attribute setting means; call registration means for, when the user registers call information at a landing of any one of the plurality of properties, adding the attribute information stored in the storage means to the call information and transmitting it to the server device; wherein the server device when receiving the call information and the attribute information from the mobile terminal, based on the attribute information, replaces the call information with a specific call and transmits it to the elevator control device installed in the arbitrary property, thereby executing an operation considering the attributes of the user. An elevator system comprising the above.

2. The attribute setting means has an attribute registration screen having a plurality of items for defining the attributes of the user, and sets the attribute information based on the items arbitrarily selected by the user on the attribute registration screen. The elevator system according to claim 1.

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

4. When receiving the first attribute information, the operation control means transmits a wheelchair call as the specific call to the elevator control device and causes a wheelchair-compatible car to respond to the user. The elevator system according to claim 3.

5. The attribute registration screen is provided with a plurality of second items for defining the attribute of refusal to share a ride, and the attribute setting means sets second attribute information indicating the attribute of refusal to share a ride when at least one of the plurality of second items is selected. The elevator system according to claim 2.

6. When the operation control means receives the second attribute information, it transmits a ride rejection call as the specific call to the elevator control device, and prohibits others from boarding the car in which the user rides. The elevator system according to claim 5.

7. The attribute registration screen is provided with a plurality of third items for defining the attribute of a person with a pet. When at least one of the plurality of third items is selected, the attribute setting means sets third attribute information indicating the attribute of a person with a pet. The elevator system according to claim 2.

8. When the operation control means receives the third attribute information, it transmits a pet call as the specific call to the elevator control device, and notifies that the user is a person with a pet. The elevator system according to claim 7.

9. When the server device receives fourth attribute information indicating the attribute of a general user, it transmits the call information to the elevator control device. The elevator control device When receiving the call information, an attribute determination means for analyzing an image of a camera installed in the landing to determine the attribute of the user, and Car operation means for replacing the call information with specific call information and performing an operation considering the attribute of the user in response to the determination result of the attribute determination means The elevator system according to claim 1, comprising:

10. In an elevator system that performs call registration for an elevator using a user's mobile terminal, A plurality of elevator control devices installed for each of a plurality of properties and controlling the operation of the elevators respectively, and A server device connected to the plurality of elevator control devices via a communication network, The mobile terminal When the user registers call information at the landing of any one of the plurality of properties, it is provided with call registration means for adding the user's identification information preset in the call information and transmitting it to the server device. The server device When receiving the call information from the mobile terminal, an acquisition means for making an attribute request to the elevator control device and acquiring attribute information indicating the attribute of the user from the elevator control device, and Storage means for storing the attribute information obtained by the acquisition means in association with the identification information, and Attribute information reading means for reading the attribute information from the storage means based on the identification information added to the call information Based on the attribute information read by the attribute information reading means, the calling information is replaced with a specific call and transmitted to the elevator control device installed in the arbitrary property, so as to include driving control means for causing the elevator to perform driving considering the attributes of the user. The elevator control device When there is the attribute request from the server device, it includes attribute determination means for analyzing an image of a camera installed at the landing to determine the attributes of the user. Attribute providing means for providing the attribute information to the server device according to the determination result by the attribute determination means An elevator system comprising the same.

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

Images