CN114436073A

CN114436073A - Elevator call registration method and elevator system

Info

Publication number: CN114436073A
Application number: CN202111194677.XA
Authority: CN
Inventors: 金子晶夫; 井元凉大郎
Original assignee: Hitachi Building Systems Co Ltd
Current assignee: Hitachi Building Systems Co Ltd
Priority date: 2020-10-30
Filing date: 2021-10-13
Publication date: 2022-05-06
Also published as: JP2022072615A; JP7412316B2

Abstract

The present invention provides an elevator call registration method and an elevator system, so that a car call from a user can be advanced, and the elevator control system side can reliably grasp the situation. A car call command generated by a portable terminal (1) held by an elevator user is transmitted from the portable terminal (1) to a car call registration device (3) via a predetermined communication line. When the car call registration device (3) receives the car call command, it authenticates the transmission source of the received car call command, and when the authentication is completed, it sends the received message to the remote monitoring device (4) that remotely monitors the elevator. The car call command of the elevator is registered, and the car call of the elevator is registered. Then, the control part (602) of the scheduled elevator remotely managed by the remote monitoring device (4) is instructed to stop the car at the floor designated by the car call command.

Description

Elevator call registration method and elevator system

Technical Field

The invention relates to an elevator call registration method and an elevator system.

Background

Conventionally, an elevator can be ridden by a user pressing a car call button provided at a landing on each floor to stop a car at the corresponding floor and open a door.

In response to this, various techniques have been developed, in which a car call is made from a portable terminal such as a smartphone held by a user, thereby achieving user convenience and shortening of waiting time at a hall.

For example, patent document 1 describes the following technique: a receiving section for performing wireless communication with a portable terminal of an elevator user is provided at an elevator landing on each floor in a building, and the elevator user performs wireless communication with a management device of an elevator in the building via the receiving section by means of the portable terminal, thereby allocating a car to the floor where the user is located.

As described in patent document 1, it is known that an operation corresponding to a car call of an elevator is performed using a portable terminal held by a user. However, in the currently proposed technology, the elevator management device in the building that receives the instruction from the portable terminal assigns only the stop floor of the car.

In other words, the portable terminal can be operated instead of pressing a car call button provided in a hall, and thus, advanced control is not always performed.

For example, in managing elevator operation, sometimes some problems occur in traveling of the car, and a failure in which passengers are enclosed in the car may occur. In such a case, in order to enable passengers to leave from the elevator car, an operator or a controller needs to support.

Some support is preferably performed on the elevator control system side for trouble in the car of a passenger who makes a car call using a portable terminal, but no specific support is currently performed.

Patent document 1: japanese laid-open patent publication No. 2002-120976

Disclosure of Invention

The invention aims to provide an elevator call registration method and an elevator system, which can improve the car call from a user and ensure the situation of an elevator control system.

In order to solve the above problem, for example, the structure described in the claims is adopted.

The present application includes a plurality of solutions to the above-described problem, and includes, for example: a car call receiving process of confirming a transmission source of a received car call command and accepting the transmission source when receiving the car call command generated by a portable terminal held by an elevator user; a car call registration process of transmitting a received car call command from the car call registration device to a remote monitoring device for remotely monitoring the elevator and registering a car call of a predetermined elevator when the car call reception process is performed; and a car call execution process for instructing a control device of a predetermined elevator remotely managed by the remote monitoring device to stop the car at the floor indicated by the car call instruction when the car call instruction is registered by the remote monitoring device.

According to the present invention, the remote monitoring apparatus can determine the number of users, the type of users, and the like based on the history of the car call registration. Therefore, when some trouble occurs in the elevator, it is possible to quickly and reliably perform a response such as rescue using the history of the car call registration.

Problems, structures, and effects other than those described above will become apparent from the following description of the embodiments.

Drawings

Fig. 1 is a block diagram showing an example of a system according to an embodiment of the present invention.

Fig. 2 is a block diagram showing an example of a hardware configuration of a call registration unit according to an embodiment of the present invention.

Fig. 3 is a data configuration diagram showing an example of a table stored in the storage unit of the call registration apparatus according to the embodiment of the present invention.

Fig. 4 is a data configuration diagram showing an example of a table stored in the storage unit of the remote monitoring apparatus according to the embodiment of the present invention.

Fig. 5 is a flowchart showing an example of the flow of the car call processing and the elevator rescue processing according to the embodiment of the present invention.

Fig. 6 is a diagram showing an example of a process for receiving a sealing report according to an embodiment of the present invention.

Fig. 7 is a diagram showing an example of the processing for determining the possibility of occlusion according to the embodiment of the present invention.

Fig. 8 is a diagram showing an example of passenger information acquisition processing according to an embodiment of the present invention.

Fig. 9 is a diagram showing an example of a display screen of a control center according to an embodiment of the present invention.

Fig. 10 is a diagram showing an example of a display screen of a mobile terminal according to an embodiment of the present invention.

Description of reference numerals

1 … portable terminal, 2 … general line network, 3 … call registration device, 3a … CPU (central control unit), 3b … ROM, 3c … RAM, 3d … nonvolatile storage device, 3e … network interface, 3f … input/output section, 4 … remote monitoring device, 5 … closed-area line network, 6 … elevator, 101 … operating section, 102 … communication section, 103 … positioning section, 110 … display section, 301 … processing section, 302 … storage section, 303 … communication section, 401 … control section, 402 … storage section, 403 … communication section, 601 … communication section, 602 … control section, 603 … elevator driving section, 7 … control center, 701 … processing section, 710 … display section.

Detailed Description

An elevator system according to an embodiment of the present invention (hereinafter referred to as "present example") will be described below with reference to the drawings.

[ System Structure ]

Fig. 1 shows a structure of an elevator system of this example.

The elevator system of this example includes a call registration device 3, a remote monitoring device 4, an elevator 6, and a control center 7.

The call registration device 3, the remote monitoring device 4, and the control center 7 are operated by a management company of the elevators 6, and collectively perform processing (registration processing, management processing, and the like) for the elevators 6 of a plurality of buildings. However, in fig. 1, only the elevators 6 of 1 building are shown for simplicity of explanation.

The call registration apparatus 3 includes a processing unit 301, a storage unit 302, and a communication unit 303.

The communication unit 303 is connected to the mobile terminal 1 via the general network 2, and receives an elevator call command from the mobile terminal 1. As the general network 2, a public line such as a wireless telephone line is used.

The portable terminal 1 is a portable terminal held by a user of the elevator 6, and is configured as a smartphone having a connection function to the internet and a call function, for example.

The mobile terminal 1 includes: an operation unit 101 operated by a user; a communication unit 102 that transmits a signal based on an operation performed by the operation unit 101; a positioning section 103 that positions a current position of the terminal; and a display section 110. When the mobile terminal 1 is a smartphone, the operation unit 101 is formed of a touch panel integrated with the display unit 110. The Positioning unit 103 positions the current position of the mobile terminal 1 using a GPS (Global Positioning System) or the like.

The portable terminal 1 is provided with an application program for performing call registration of an elevator by operating the operation unit 101 by a user. That is, the mobile terminal 1 specifies a building, a car, a call time, and a destination floor where an elevator to be called is installed based on the operation of the operation unit 101, and generates a car call command having the specified contents. The boarding floor is a floor registered in advance such as the 1 st floor, but may be changed by the operation of the operation unit 101.

The mobile terminal 1 also has a function of transmitting the generated car call command from the communication unit 102 to the call registration device 3 via the general network 2. At this time, the mobile terminal 1 simultaneously transmits the unique identification number or the user account information which the mobile terminal 1 has to the call registration apparatus 3. Further, the mobile terminal 1 can also receive the success or failure of the elevator call and other interface information as a result of transmission. The mobile terminal 1 can also transmit the positional information located by the positioning unit 103 from the communication unit 102.

The portable terminal 1 held by the user of the elevator 6 is a terminal registered in advance in the call registration device 3, and a unique identification number or user account information of the registered portable terminal 1 is stored as customer information in the storage unit 302 of the call registration device 3. Further, a history of the car call command and the like are stored in the storage unit 302. The information stored in the storage section 302 will be described in detail later.

When the communication unit 303 receives an elevator call command from the mobile terminal 1, the processing unit 301 of the call registration device 3 performs authentication processing for determining whether or not the terminal is a registered terminal based on the information stored in the storage unit 302. The processing unit 301 performs a process of receiving a received car call command (car call receiving process) when the elevator call command is from the registered portable terminal 1 by the authentication process. Then, the processing unit 301 transfers the car call command from the mobile terminal 1 to the remote monitoring apparatus 4.

In addition, the car call command of the elevator transmitted from the portable terminal 1 to the call registration device 3 includes information on the floor where the user takes the elevator and the floor where the user takes the elevator, in addition to the identification code of the portable terminal 1. In addition, the car call command may include information on the current position of the mobile terminal 1.

In addition, when the information on the current position of the portable terminal 1 is included in the elevator call command, the processing unit 301 performs processing for receiving a car call command only when the information on the current position is in the vicinity of the building in which the elevator 6 is installed.

The remote monitoring apparatus 4 includes a control unit 401, a storage unit 402, and a communication unit 403.

The control unit 401 performs processing for remotely monitoring the operation state of the elevator 6. When the car call command is transmitted (forwarded) from the call registration device 3, the control unit 401 transmits registration information of the stop floor of the elevator 6 based on the car call command to the communication unit 601 on the elevator 6 side via the communication unit 403.

When a failure of the elevator 6 under monitoring is detected, the control unit 401 determines whether or not the closure of the passenger has occurred in the car in which the failure has occurred, and takes measures based on the determination. The determination as to whether or not the occlusion has occurred and the details of the handling thereof will be described later.

The storage unit 402 stores information about the elevator 6 monitored by the remote monitoring device 4, and histories of the operation state, failure, and the like of the elevator 6. The information stored in the storage section 402 will be described in detail later.

The communication unit 403 communicates with the communication unit 601 of the elevator 6 via the closed-circuit network 5.

The elevator 6 includes a communication unit 601, a control unit 602, and a hoist drive unit 603. The communication unit 601 communicates with the communication unit 403 on the remote monitoring apparatus 4 side via the closed network 5, which is a dedicated network for elevators.

The control unit 602 controls the elevator driving unit 603 to travel (raise and lower) the car (not shown) of the elevator 6, open and close the doors, and the like. Further, by giving a unique identification number to the communication unit 601 of the elevator 6 and communicating with the remote monitoring apparatus 4, when information from the communication unit 601 is received on the side of the remote monitoring apparatus 4, the article information and address relating to the transmission source of the received information can be uniquely identified.

The running control of the car by the control section 602 is performed based on the operation of a stop floor registration button in the car and the operation of a car call registration button at a landing at each floor. When the communication unit 601 receives the registration information of the stop floor from the remote monitoring apparatus 4, the control unit 602 performs the travel control based on the registration information of the stop floor.

The control unit 602 monitors the operating state of the elevator 6 and the occurrence of a failure, and when the occurrence of a failure is detected, transmits failure information to the remote monitoring apparatus 4 via the communication unit 601.

The control center 7 includes a processing unit 701 and a display unit 710.

The processing unit 701 acquires information stored in the storage unit 302 of the call registration device 3 and information stored in the storage unit 402 of the remote monitoring device 4 in real time, and integrates these information to display the operating state of the elevator 6 and the handling at the time of failure on the display unit 710.

At this time, the processing unit 701 acquires information on whether or not the user (passenger) is closed when the elevator 6 has a failure based on the information stored in the

storage units

302 and 402, and displays details of the failure on the display unit 710. Further, when a closure failure occurs, the processing unit 701 automatically transmits the passenger information in the car to the controller.

[ hardware configuration of each device ]

The call registration device 3 and the remote monitoring device 4 can be constituted by computers, for example.

Fig. 2 shows an example of a hardware configuration in the case where the call registration apparatus 3 is a computer.

The call registration apparatus (computer) 3 shown in fig. 2 includes a CPU (Central Processing Unit) 3a, a ROM (Read Only Memory) 3b, a RAM (Random Access Memory) 3c, a nonvolatile Memory device 3d, a network interface 3e, and an input/output Unit 3f, which are connected to a bus, respectively.

The nonvolatile memory device 3d corresponds to the storage unit 302 of the call registration apparatus 3. The network interface 3e corresponds to the communication unit 303 of the call registration apparatus 3.

The CPU3a is an arithmetic processing unit that reads out and executes program codes of software that realizes functions performed by the call registration apparatus 3 from the ROM3 b.

Variables, parameters, and the like generated during the arithmetic processing are temporarily written in the RAM3 c.

The nonvolatile storage device 3d stores customer information, call history, and the like using a large-capacity information storage medium such as an hdd (hard Disk drive) or an ssd (solid State drive).

The Network Interface 3e performs data transmission to the general line Network 2 and data reception from the general line Network 2, for example, using an NIC (Network Interface Card) or the like.

The input/output unit 3f exchanges data among the call registration device 3, the remote monitoring device 4, and the control center 7.

Fig. 2 shows an example in which the call registration device 3 is configured by a computer, but the remote monitoring device 4 may be configured by a computer as well. Further, the control center 7 may be configured by the same computer. However, in the case of the control center 7, in addition to the configuration shown in fig. 2, an input unit such as a display unit 710 and a keyboard for controlling the operation of the operator is added.

Note that the call registration device 3 and the remote monitoring device 4 are configured by computers shown in fig. 2 as an example, and may be configured by other arithmetic processing devices than computers. For example, a part or all of the functions performed by the call registration apparatus 3 may be realized by hardware such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). The call registration apparatus 3 and the remote monitoring apparatus 4 may be configured by 1 computer, and execute the function as the call registration apparatus 3 and the function as the remote monitoring apparatus 4.

[ Structure of stored information ]

Fig. 3 shows an example of information stored in the storage unit 302 of the call registration apparatus 3.

The storage unit 302 is provided with a customer information table T11, a call registration log table T12, and an elevator remote operation detailed record table T13.

The details of tables T11 to T13 will be described, and information on a user who uses the elevator remote call service provided by the system of the present example is stored in the customer information table T11.

That is, as shown in fig. 3, the customer information table T11 has registered therein a unique number assigned to each user, i.e., a user number, customer information, sex, age, memo information, and date of registration. Information that needs to be considered for using an elevator, such as wheelchair use and claustrophobia, is registered in the remark information. Information such as sex, age, wheelchair use, claustrophobia, and the like of the registered user is used as category information of the customer. Specific examples of using the category information of the customer will be described later. Note that, as the remark information, information such as a use history, a use frequency, a calling time zone, and a destination floor that is normally used by the corresponding user may be registered.

In the call registration log table T12, a history of calls from the mobile terminal 1 is stored for each 1 elevator.

That is, as shown in fig. 3, information of a number assigned in the call order, a call source number (user number), a call destination code (manufacturing number of the subject elevator), a call floor (boarding floor), a destination floor (alighting floor), and a call date and time is registered in the call registration log table T12.

In the elevator remote operation detailed history table T13, events associated with remote call registration are stored in time series order by each elevator manufacturing number. That is, as shown in fig. 3, an event ID, a code (elevator manufacturing number), details of the event, a call number, and an occurrence date and time are registered in the elevator remote operation detailed history table T13.

Fig. 4 shows an example of information stored in the storage unit 402 of the remote monitoring apparatus 4.

The storage unit 402 stores an elevator information table T21, a report history table T22, and an operation state table T23.

The details of each table T21 to T33 will be described, and the elevator manufacturing numbers and the specification information of the associated elevators are registered in the elevator information table T21. That is, as shown in fig. 4, a code corresponding to an elevator manufacturing number, a customer number, a machine type number, a car number, information on the uppermost floor, and information on the monitoring start date of the elevator installation building are registered in the elevator information table T21.

In the report history table T22, the report code received from the monitoring start date is stored with the elevator manufacturing number as a key. That is, as shown in fig. 4, a code corresponding to an elevator manufacturing number, a report code, and a reception date and time are registered.

The operating state table T23 stores the error message and the operating state of the elevator 6 acquired by the remote monitoring device 4 using the elevator manufacturing number as a key. That is, as shown in fig. 4, a code corresponding to the elevator manufacturing number, a trouble code indicating the content of trouble, data indicating the details of the content of trouble, and the occurrence date and time are registered in the operation state table T23.

[ procedure of Car Call processing and Elevator rescue processing ]

Fig. 5 is a flowchart showing an example of the flow of the car call processing and the elevator rescue processing executed in the elevator system of this example.

First, the user inputs an elevator to be called, a car, a call floor, and a destination floor via the mobile terminal 1, and then sends a car call command for remotely calling the elevator to the call registration device 3 (step S1).

Upon receiving the car call command, the call registration device 3 authenticates that the car call command is from the portable terminal 1 registered in advance, and then transmits the car call command to the elevator 6 via the remote monitoring device 4 to stop the car of the elevator 6 at the instructed floor.

Thereby, the user having the mobile terminal 1 that instructed the car call can get on the elevator 6 (step S2). At this time, in the call registration apparatus 3, the storage unit 302 associates the identification number of the elevator 6 with the identification number of the mobile terminal 1, and stores the call history and the information of the user of the call in the call registration log table T12 (fig. 3).

Then, it is assumed that a closing failure has occurred in the car of the elevator 6 due to some reason stopping before reaching the preset destination floor (step S3). At this time, the control unit 602 of the elevator 6 transmits a closing report to the remote monitoring apparatus 4 (step S4).

When the remote monitoring apparatus 4 receives the closing report, the items including the defective elevator 6, the failure condition, and the cause of occurrence are collected from the report information and the information stored in the storage unit 402, and are deployed to the control center 7 (step S5).

Simultaneously with the receipt of the information, the processing unit 702 of the control center 7 inquires the storage unit 302 of the call registration device 3 and confirms whether or not the corresponding elevator 6 is called by the remote call registration function from the portable terminal 1 (step S6). If the call is not being called by the remote call registration function in step S6 (no in step S6), a step of performing closed rescue is performed in accordance with the normal procedure (step S14).

When a call is received by the remote call registration function in step S6 (yes in step S6), the number of mobile terminals 1 that are called is counted (step S7). Then, the following processing of steps S9 to S11 is performed in accordance with the number of mobile terminals 1 called, that is, the number of users of the elevator 6 (step S8).

Step S9: the survey user calls the floor and destination floor of the elevator.

Step S10: by referring to the information of step S9 and the position where the sealing is generated, it is determined whether or not the sealing is generated at a position beyond the target floor. In step S10, if the position is a position exceeding the destination floor (yes in step S10), it is determined that the user has left before the closure occurs, and therefore the user is excluded from candidates for closing passengers. In step S10, if the destination floor is not exceeded (no in step S10), the destination floor is added to the closed passenger candidate.

Step S11: in step S10, if the user does not exceed the target floor, it is determined that the user is confined in the car, and therefore detailed information of the user is collected. The collected information is information on the user (customer) registered in the customer information table T11 (fig. 3), and includes at least the age of the user and category information of the user who contributes to rescue, such as using a wheelchair.

The processing of steps S9 to S11 is repeated for each number of mobile terminals 1 called, and the list of passengers confined in the car is generated (step S12). The passenger list is integrated with the item information and the elevator model information stored in the storage unit 402 of the remote monitoring apparatus 4, transmitted to the control center 7, and provided to the controller by display or the like on the display unit 710 (step S13).

The controller provides the on-site operator with advance information necessary for passenger rescue using the information displayed on the display unit 710 (step S14).

Fig. 6 shows an example of the determination process performed in step S6.

In the example of fig. 6, in the elevator remote operation detailed history table T13 in the storage unit 302 of the call registration device 3, as an event ID: b0008, recording the event of the acceptance of the closed report.

At this time, the event ID: event ID before B0008, remote call without stop of destination floor is judged. Specifically, regarding the event ID: remote call reception of B0001, since at event ID: b0001, excluding destination floor stop, judging as event ID: the remote call reception of B0003 has not yet landed to the destination floor.

Fig. 7 shows an example of the processing performed when it is determined whether or not the closed position exceeds the target floor in step S10.

In the example of fig. 7, in the call registration log table T12 of the storage unit 302 of the call registration device 3, information that the call floor is 10 floors and the destination floor is 20 floors is registered for the call number 2.

In addition, information on the occurrence state position of the failure and the date and time is registered in the information of the operation state table T23 of the storage unit 402 of the remote monitoring device 4, and the current position of the car (the position at which the car stops in the closed failure) is determined. For example, in the example of fig. 7, when the current position of the car is lower than the 20 th floor, the processing unit 701 of the control center 7 determines that there is a possibility of blocking.

Fig. 8 shows a process of integrating elevator installation items, failure information, and passenger information of the elevator car in step S13.

Specifically, the processing unit 701 of the control center 7 acquires information on the call floor and the destination floor from the call registration log table T12, and acquires detailed information on the age, sex, and the like of the closed customer (user) from the customer information table T11. Further, the processing unit 701 of the control center 7 acquires details of the failure state, the failure date and time, and the like from the operation state table T23, and acquires the model information of the elevator in which the failure has occurred and the information of the highest floor from the elevator information table T21.

As shown in fig. 8, the control center 7 can reliably instruct the site operator because the information of the highest floor exists as the elevator information. That is, the hoisting machine of the elevator and the control device thereof are usually installed near the uppermost floor, and when instructed from the control center 7, it is possible to reliably instruct the operator to which floor to go.

[ display example in control center ]

Fig. 9 shows an example of a screen of the display unit 710 of the control center 7 when a closed fault occurs in the elevator.

A screen 711 of the display unit 710 shown in fig. 9 (a) is an application screen for confirming the closure report state. On the upper right of this screen 711, a display 712 of the total number of closed report production items produced nationwide or under the jurisdiction of the control center is displayed. Further, adjacent to the display 712, an area selection field is provided to enable efficient understanding of a closed state in a case where a disaster such as a wind and water disaster or an earthquake occurs in an area where large-scale disasters or the like are concentrated.

Under the display 712 of the total number of generated pieces of the closure report, displays 713, 714 of the closure-failed article are displayed in 1 row for every 1 article. The item displays 713 and 714 have display areas for indicating the item number set for each item, the number of floors and stop floors of the elevator, the date and time of occurrence and the elapsed time, and whether or not the remote call is made.

For example, in the example of display 713, an example of a situation is shown where a closure failure has occurred in an elevator that is remotely called. Since the remote call is performed, the estimated number of persons present in the car is displayed at the right end of the row of the display 713. The number of people represents the number of people who remotely called.

In the example of the display 714, an example of the case where a closure failure has occurred in an elevator which is not remotely called is shown. Since there is no record of the remote call, there is an x button displayed at the right end of the row of display 714.

The controller can display more detailed information by selecting and clicking on display 713 or display 714.

A screen 721 in fig. 9 (b) shows an example in which the display 713 is clicked. In the detailed information display column 722 of the display 712, the type of elevator and the estimated number of passengers are displayed based on the failure information transmitted when the closed failure occurs and the information stored in the remote monitoring apparatus 4.

The details of the remotely called passenger are displayed in the details display

columns

723 and 724 of the closed passenger. The display of the detailed information of the passenger uses the category information of the customer registered in the customer information table T11 (fig. 3). The passenger detailed information display fields 723 and 724 in the example of fig. 9 show examples in which the name and age of the user are described as the category of the customer. In addition, the more detailed category information of the customer registered in the memo information of the customer information table T11 is displayed in the column of the special record items. For example, "claustrophobia" is displayed on the screen 721 in fig. 9 (b). The controller who has confirmed the display of "claustrophobia" can make a judgment such as a higher priority for rescuing the relevant customer than other customers.

In this way, the passenger detailed

information display columns

723 and 724 are provided with the characteristics of the passengers, and therefore can be used as a material for determining the rescue priority. Further, when the controller makes a call with the car, the controller can be used as information for preventing a driver from being scared.

In the passenger detailed information display field 724 of the example of fig. 9, an example of a case where "wheelchair use" is described as a special record item is shown. By performing such display, it is possible to quickly instruct the field worker of the tool and equipment necessary for performing the rescue work when the wheelchair is used.

Then, the controller issues an instruction to start the work to the field worker by pressing the button 725 in the screen 721, and transmits the information displayed in the screen 721 to the terminal held by the work to be started.

[ display example in user terminal ]

When the processing unit 702 of the control center 7 determines that the user who made the remote car call is closed, it may check whether or not the portable terminal 1 of the corresponding user is closed using the general network 2.

Fig. 10 shows an example of a screen of the display unit 110 of the mobile terminal 1 when it is determined that the user is closed.

For example, when the processing unit 702 of the control center 7 determines that there is a possibility of occurrence of a block of the user who makes a remote car call, the processing unit 702 displays the guide screen 111 on which the block has occurred on the mobile terminal 1 as shown on the left side of fig. 10.

On the guidance screen 111, a closed trouble occurrence notification display 112 and a confirmation display 113 for confirming whether or not the corresponding elevator is mounted are provided.

As the confirmation display 113, a column 113a of "yes" for replying to a boarding of the corresponding elevator and a column 113b of "no" for replying to a non-boarding are provided.

Here, when the column 113b of "no" is touched, the "thank you answer is added to the guide screen 111 as shown in the center of fig. 10. And a display section 114 for "" display. Based on the answer, the processing unit 702 of the control center 7 excludes the corresponding user from the closed passenger list.

When the yes column 113a is touched, a display column 115 of "… … can communicate with the technician at the control center" is added to the guidance screen 111 as shown on the right side of fig. 10.

A button (a mark of a handset) for making a call is displayed in the display section 115, and a call with the control center 7 is made by a user touching the corresponding button.

< modification example >

The present invention is not limited to the above-described embodiment examples, and includes various modifications. For example, the above-described embodiment is an example explained in detail for easily understanding the present invention, and is not limited to the case where all the structures described are necessarily provided.

For example, the display screens shown in fig. 9 and 10 show an example of a screen for notifying a controller or a user, and may be display screens of other forms.

In addition, in the block diagrams of fig. 1 and 2, the control lines and the information lines only indicate control lines and information lines necessary for the description, and do not necessarily indicate all control lines and information lines on the product. In practice, it is also possible to consider almost all structures connected to one another. In the flowchart shown in fig. 5, a plurality of processes may be executed simultaneously or the order of the processes may be changed within a range that does not affect the processing result.

Claims

1. An elevator call registration method, characterized in that,

the elevator call registration method comprises the following steps:

a car call reception process of authenticating and accepting a transmission source of a received car call command when receiving the car call command generated by a portable terminal held by an elevator user;

a car call registration process of transmitting a received car call command from the car call registration device to a remote monitoring device that remotely monitors an elevator and registering a car call of the elevator when the car call reception process is performed; and

and a car call execution process of, when the remote monitoring device registers the car call command, instructing a control device of an elevator remotely managed by the remote monitoring device to stop the car at the floor indicated by the car call command.

2. The elevator call registration method of claim 1,

the remote monitoring device performs a blocking detection process for detecting a possibility of blocking of a user in the car based on a history of performing the car call registration process when receiving failure report information from the elevator instructed by the car call execution process.

3. The elevator call registration method according to claim 2,

the remote monitoring device determines the type of a user in a car that is likely to be closed based on information of a transmission source acquired by the car call reception processing, and determines the priority of rescue.

4. The elevator call registration method according to claim 2,

the remote monitoring device transmits guidance information inquiring whether or not the mobile terminal of the user in the car is closed to the car via a predetermined communication line based on the information of the transmission source acquired by the car call reception processing.

5. The elevator call registration method according to claim 2,

the detection process detects the possibility of a closure of a user in the car based on whether the current car position reaches the destination floor.

6. An elevator system, characterized in that,

the elevator system comprises:

a car call registration device that receives a car call command generated based on an operation of instructing a car call of a predetermined elevator in a portable terminal held by an elevator user, and authenticates a transmission source of the received car call command;

a remote monitoring device which receives the transfer of the received car call command and registers the car call of the predetermined elevator when the authentication is completed by the car call registration device; and

and a control device that, when the car call command is registered by the remote monitoring device, instructs the car to stop at the floor instructed by the car call command.