JP2022142918A - Elevator system and information output method - Google Patents

Abstract

To provide an elevator system enabling a user to know exit congestion information before the adjustment of a parking fee.SOLUTION: An elevator system 100 includes a communication unit 112C receiving a call request from a user terminal 160 and a processing unit 112B outputting exit congestion information showing the congestion in a zone until a vehicle of a user goes out of a predetermined area from a parking lot to the user terminal 160 having output the call request when a parking lot floor continuing to the parking lot is included as a destination floor in the call request.SELECTED DRAWING: Figure 1

Description

The present invention relates to an elevator system and an information output method.

The parking lot is provided with an entrance/exit for regulating the entry and exit of vehicles, and an adjustment office for adjusting the parking fee. A user of the parking lot starts using the parking lot by entering the vehicle from the entrance and parking the vehicle in a parking space in the parking lot. When finishing using the parking lot, the user drives the vehicle from the parking space to the exit, settles the parking fee at the adjustment office, and then exits the vehicle from the exit.

The parking lot has a multi-storey parking lot and a flat parking lot. In a multilevel parking garage, a plurality of parking spaces are provided on the parking floor of a building. Also, parking floors may be installed on multiple floors of a building. Also, in the flat parking lot, a large number of parking spaces are provided on the flat land adjacent to the building. In this specification, exiting a building with a parking lot is called "exiting". In addition, even if a vehicle exits the parking space, the toll payment for the first vehicle is delayed at the adjustment office. When a vehicle cannot join the road immediately after leaving the parking lot, it is called "departure congestion."

If the number of vehicles exiting the parking space at a specific time increases, the vehicles tend to be congested in front of the exit, increasing the time required for settlement processing at the settlement office. Therefore, techniques for improving convenience for parking lot users have been studied. For example, in Patent Document 1, "The acquisition unit acquires congestion information regarding the congestion status of vehicles exiting from the parking lot. It controls the grace time from the start to the start of the vehicle.”

JP 2019-23832 A

By the way, in the technique disclosed in Patent Document 1, congestion information of the exit gate is displayed on the portable terminal of the person who pays the parking fee when the parking fee is paid. For this reason, the user was unable to temporarily stop leaving the parking lot in consideration of the congestion information before paying the parking fee. In addition, if it is not possible to review leaving the parking lot, the user who has paid the parking fee will always try to leave the parking lot, and congestion information will not be alleviated. As described above, the conventional technology cannot be said to have sufficiently considered the convenience of the user.

SUMMARY OF THE INVENTION The present invention has been made in view of such a situation, and an object of the present invention is to inform the user of parking congestion information before the payment of the parking fee.

An elevator system according to the present invention dispatches a car to a boarding floor in accordance with a call request from a user terminal of a user.
This elevator system includes a communication unit that receives a call request from a user terminal, and a parking lot floor following a parking lot that is included in the call request as a destination floor. and a processing unit for outputting, through the communication unit, delivery congestion information representing congestion until the user leaves the area, to the user terminal that has made the call request.

According to the present invention, the elevator system outputs congestion information to the user terminal when the user terminal receives a call request with the destination floor as the parking floor, for example, before the parking fee is settled. can be confirmed by the user, the convenience of using the parking lot for the user is improved.
Problems, configurations, and effects other than those described above will be clarified by the following description of the embodiments.

It is a block diagram showing an example of whole elevator system composition concerning one embodiment of the present invention. 1 is a block diagram showing a hardware configuration example of a computer according to an embodiment of the present invention; FIG. It is a flow chart which shows an example of elevator processing in an elevator system concerning one embodiment of the present invention. It is a display example of a congestion information message notifying that the waiting time is 30 minutes or longer according to one embodiment of the present invention. It is a display example of a message including information provided to the user terminal according to the waiting time displayed on the user terminal according to the embodiment of the present invention. It is a display example of a congestion information message notifying that the waiting time is 45 minutes or more according to one embodiment of the present invention. It is a display example of a congestion information message notifying that the waiting time is 60 minutes or more according to one embodiment of the present invention. It is an example of a display of the traffic information necessity message which concerns on one embodiment of this invention. It is a display example of a traffic information necessity message including a hyperlink according to an embodiment of the present invention. It is a display example of a surrounding map according to an embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments for carrying out the present invention will be described with reference to the accompanying drawings. The present specification and drawings are given as examples to explain the present invention, and are appropriately omitted and simplified for clarity of explanation. The present invention can also be implemented in various other forms. Unless otherwise specified, each component may be singular or plural. Further, in the present specification and drawings, constituent elements having substantially the same function or configuration are denoted by the same reference numerals, thereby omitting redundant description.

[One embodiment]
FIG. 1 is a block diagram showing an overall configuration example of an elevator system 100 according to one embodiment. Elevator system 100 according to the present embodiment enables registration of a call to elevator 140 from user terminal 160 operated by a user. The elevator system 100 is characterized by communication when call registration is performed using a message exchange application installed in the user terminal 160 . In this specification, the application is also abbreviated as "app". Also, in this specification, a section in which a vehicle can be parked is called a "parking space", and a place where a plurality of parking spaces are provided is called a "parking lot".

The elevator system 100 shown in FIG. 1 is a system that dispatches cars to boarding floors and destination floors in accordance with a call request from a user terminal 160 capable of requesting a call to an elevator 140 . This elevator system 100 comprises a remote monitoring server 111 , a preprocessing device 112 and a DMZ (DeMilitarized Zone) 113 . Remote monitoring server 111 , preprocessing device 112 and DMZ 113 are provided in control center 110 . The control center 110 is a facility capable of remotely controlling the operational status of the elevators 140 installed in each building.
Also, the remote monitoring server 111 and the preprocessing device 112 are connected via the DMZ 113 .

In the elevator system 100, the elevator 140 is called in response to a call registration request generated by a message exchange type SNS (Social Networking Service) application (hereinafter abbreviated as “SNS application”) installed in the user terminal 160. information is set. This call information includes the boarding floor and destination floor of the call request. The SNS application is an example of a message exchange application that allows the user terminal 160 to exchange messages with other user terminals 160 .

Here, the request for call registration by the SNS application is, for example, input of boarding floor information and destination floor information by the user of the parking lot using the user terminal 160, and is hereinafter referred to as a "call request". called. The call request is transmitted to the preprocessing device 112 through the SNS application activated by the user terminal 160, and if the user terminal 160 does not change the call request (for example, cancel the call request), the elevator 140 is moved to the boarding floor and Destination floor is set. The boarding floor and destination floor for the elevator 140 are set through the elevator system 100 . Also, the elevator system 100 acquires the congestion state in front of the exit gate from the parking lot management device 170 and acquires the congestion information around the building where the parking lot is installed from the congestion information device 180 .

<Configuration example of user terminal>
The user terminal 160 is, for example, an information processing device such as a smart phone or a tablet terminal carried by the user, and the user of the parking lot can input a call request. If the user is a user of a building with a parking lot and is registered with the SNS application, even a person other than the user of the parking lot can use the functions of the user terminal 160. . The user terminal 160 has a message exchange section 161, for example.

The message exchange unit 161 has, for example, a message exchange function provided by an SNS application. The message exchange unit 161 communicates with the preprocessing device 112 and other user terminals 160 (not shown) via the public network 102 and the application device 150 . This communication may include sending and receiving text messages or electronic files.

<Configuration example of application device>
The application device 150 is, for example, an information processing device. Application device 150 includes authentication unit 151 and application data processing unit 152 .

The authentication unit 151 allows the user of the user terminal 160 to exchange messages with the SNS application of the user terminal 160 based on the activation information (login information, etc.) of the SNS application executed on the user terminal 160. It determines (authenticates) whether the person is a person. If the authentication result is valid, the application data processing unit 152 performs subsequent processing.

The application data processing unit 152 transfers a message received from the message exchange unit 161 to another user terminal 160 , or transfers a message transmitted from another user terminal 160 to the message exchange unit 161 of the user terminal 160 . transfer to

Further, when the message received from message exchange unit 161 is to set a call request to elevator 140, application data processing unit 152 sets a call request to elevator 140 generated based on this call request. message to the preprocessor 112 . A call request is different from normal call registration in that the user can cancel the call even after the user has registered on the user terminal 160 . The application data processing unit 152 generates a congestion information message based on the delivery congestion information received from the preprocessing device 112 and transmits this congestion information message to the user terminal 160 .

<Configuration example of pretreatment device>
Next, a configuration example of the pretreatment device 112 will be described.
The preprocessing device 112 is, for example, an information processing device such as a server, and is connected to the application device 150 via the public network 102 . The preprocessing device 112 includes, for example, an authentication unit 112A, a processing unit 112B, a communication unit 112C, and a user DB 112D.

112 A of authentication parts authenticate the user who uses the user terminal 160 based on the call request|requirement which 112 C of communication parts received. For example, the authentication unit 112A refers to the user DB 112D and determines whether the user whose call request is registered by the user terminal 160 from the SNS application is a user permitted to register the call request (authentication )do.

For example, if the user application ID added to the message received from application device 150 is stored in user DB 112D, authentication unit 112A can determine that the user is permitted to register a call request. . Therefore, if the user application ID added to the message received from the application device 150 is not stored in the user DB 112D, the authentication unit 112A returns an authentication error to the application device 150. Do not connect to processing.

The processing unit 112B performs processing corresponding to the message received by the communication unit 112C from the SNS application of the user terminal 160 via the application device 150 . Then, when the parking lot floor following the parking lot is included in the call request as the destination floor, the processing unit 112B outputs the parking congestion information to the user terminal 160 that has made the call request through the communication unit 112C. The exit congestion information is information representing congestion until the vehicle of the user authenticated by the authentication unit 112A leaves the parking lot and exits the predetermined area. Outside a predetermined area is, for example, outside a building provided with a multistory parking lot or outside a site provided with a plane parking lot. The exit congestion information includes the waiting time required for the user of the user terminal 160 to get out of the parking space of the parking lot and out of the area. The delivery congestion information output to the user terminal 160 changes according to the waiting time.

Here, for example, when the processing unit 112B receives an elevator call request, the processing unit 112B determines the number of waiting vehicles lined up at the exit of the parking lot, the number of call requests set for the elevator 140, and the parking lot. The waiting time is obtained based on congestion information around the building. For example, if it takes 30 seconds for each vehicle to pay the bill at the exit, the waiting time is obtained by multiplying the number of vehicles by 30 seconds. Also, if the road around the parking lot is congested, for example, it is assumed that it takes 20 seconds for each vehicle to join the road. Therefore, the value obtained by multiplying the number of vehicles waiting for delivery by 20 seconds is added to the waiting time. Then, the processing unit 112B transmits to the application device 150 a message for prompting the user to check the congestion information (hereinafter referred to as a “congestion information message”).

112 C of communication parts receive the call request from the user terminal 160 via the application apparatus 150, and transmit the message processed by the process part 112B to the user terminal 160 via the application apparatus 150. . Here, when the congestion state in front of the exit gate is received from the parking management device 170, the communication unit 112C transfers the congestion state in front of the exit gate to the processing unit 112B. Further, when receiving the congestion information around the building from the congestion information device 180, the communication unit 112C transfers the congestion information around the building to the processing unit 112B. When the communication unit 112C receives a call request as an SNS application message from the application device 150, the communication unit 112C transfers the message including the call request to the processing unit 112B. In addition, the communication unit 112C transmits a congestion information message including the delivery congestion information generated by the processing unit 112B to the user terminal 160 via the application device 150. FIG.

The user DB 112D is an example of a storage unit and stores user information. The user DB 112D stores user application IDs used by users of the application device 150, and the like. The user DB 112D is referred to when the authentication unit 112A performs authentication.

<Example of configuration of DMZ>
DMZ 113 is a network area for safely performing communication between remote monitoring server 111 connected to network 101 and preprocessing device 112 connected to public network 102 . The DMZ 113 ensures security of information transmitted and received by the communication device 120 , the remote monitoring device 130 and the elevator 140 connected to the remote monitoring server 111 .

<Configuration example of remote monitoring server>
Next, a configuration example of the remote monitoring server 111 will be described.
The remote monitoring server 111 is, for example, an information processing device, connected to the communication device 120 via the network 101 and connected to the preprocessing device 112 via the DMZ 113 . The remote monitoring server 111 is a device that receives a call request for the elevator 140 transmitted from the user terminal 160 from the preprocessing device 112 (processing unit 112B) and sets this call request to the elevator 140 . This remote monitoring server 111 is capable of collecting operational statuses of elevators 140 monitored by a plurality of remote monitoring devices 130 and remotely monitoring elevators 140 in various locations. This remote monitoring server 111 links the call request sent from the preprocessing device 112 to the elevator 140 . The remote monitoring server 111 includes a setting section 111A, an elevator information acquisition section 111B and an elevator DB 111C.

The setting unit 111A receives the call request transmitted by the user terminal 160 via the application device 150 and the preprocessing device 112 . Then, the setting unit 111A refers to the elevator DB 111C to identify the elevator 140 for which the call request has been made, and generates call information for the elevator 140 based on the call request. The setting unit 111A also transmits call information to the elevator 140 via the network 101, the communication device 120 and the remote monitoring device 130, and sets the boarding floor and destination floor for the elevator 140. FIG.

Elevator information acquisition unit 111B acquires elevator information of elevator 140 via remote monitoring device 130 and communication device 120 . The elevator information acquisition unit 111B then stores the elevator information in the elevator DB 111C and transmits the elevator information to the preprocessing device 112 . The elevator information includes the position of the car for each elevator 140, the time when the car arrived at the boarding floor, the time when the car departed from the boarding floor, the time when the car arrived at the destination floor, the time when the car departed from the destination floor, and the like. Contains information.

Elevator DB 111C stores elevator information of each elevator 140 . The elevator information includes, for example, information such as the model name of the elevator 140, the number of elevators, floors on which the car can travel, parking floors, and the like.

<Elevator side configuration example>
Next, a configuration example on the elevator 140 side from the network 101 will be described.
The network 101 is a secure communication line, and the remote monitoring server 111 and the communication device 120 can safely transmit and receive various information via the network 101 . Information is also safely transmitted and received between the communication device 120 and the remote monitoring device 130 and between the remote monitoring device 130 and the elevator 140 .

Communication device 120 is connected to remote monitoring server 111 via network 101 . Communication device 120 is also connected to remote monitoring device 130 . The communication device 120 is, for example, a device for connecting the remote monitoring device 130 to an external device (eg, the remote monitoring server 111).

Remote monitoring device 130 is a device capable of remotely monitoring the operation of elevator 140 . Remote monitoring device 130 is connected to communication device 120 and elevator 140 . Remote monitoring device 130 communicates with remote monitoring server 111 via communication device 120 and network 101 . Further, the remote monitoring device 130 transfers the call information of the elevator 140 transmitted by the remote monitoring server 111 to the elevator 140 .

Elevator 140 is installed in a building with a parking lot. The parking lot according to the present embodiment may be either a plane parking lot or a multilevel parking lot. In the case of a flat parking lot, for example, a large number of parking spaces are provided on ground ground adjacent to a building in which an elevator 140 is provided. In the case of a multi-storey car park, for example, parking spaces are provided on the parking floors of other buildings that are installed within a building or that are connected by connecting passages. In addition, multi-storey parking lots can be self-propelled or mechanical.

One or more elevators 140 are installed in one building. A user can register a call request to the elevator 140 by operating the user terminal 160 . When the call request is registered, a car is dispatched to the boarding floor specified by the user terminal 160, ie, the floor where the user is present, and the user can board the car. Then, the user can register, for example, the floor of the parking lot next to the parking lot as the destination floor and move to the destination floor. In this embodiment, for example, when a parking lot is provided on the roof of a building, if the user moves from the floor one floor below the roof to the rooftop by an escalator, the floor one floor below the roof is used. It may be a parking floor that follows the parking lot. Also, a floor with a connecting passageway to the parking lot may be used as the parking lot floor leading to the parking lot.

<Configuration example of parking lot management device>
Next, a configuration example of the parking lot management device 170 will be described.
The parking lot management device 170 is, for example, a device that manages the parking lot of the building where the elevator 140 is installed, and is provided for each building where the parking lot is installed. The parking lot management device 170 can inform the preprocessing device 112 of the congestion state of the parking lot via the public network 102 and the application device 150 .

The parking lot management device 170 includes a processing unit 171 .
The processing unit 171 extracts the outline of the vehicle using the camera image taken by the camera installed in front of the exit gate of the parking lot, and calculates the number of vehicles lined up in front of the exit gate. The information on the number of vehicles is called "congestion state in front of the exit gate". Then, the processing unit 171 transmits the congestion state in front of the exit gate to the user terminal 160 .

<Configuration example of congestion information device>
Next, a configuration example of the congestion information device 180 will be described.
The congestion information device 180 acquires congestion information around the building where the elevator 140 is provided. The congestion information device 180 can exchange messages with the user terminal 160 via the public network 102 and the application device 150 .

The congestion information device 180 has a congestion information DB 181 .
The congestion information DB 181 stores the congestion information around the building acquired by the congestion information device 180 . The congestion information acquired by the processing unit 112B from the congestion information DB 181 is transmitted to the user terminal 160. FIG.

<Computer hardware configuration>
Next, the hardware configuration of the computer 10 constituting each device of the elevator system 100 will be described.
FIG. 2 is a block diagram showing a hardware configuration example of the computer 10. As shown in FIG. Computer 10 is an example of hardware used as a computer operable as elevator system 100 according to the present embodiment. Elevator system 100 according to the present embodiment realizes an information output method performed by cooperation of the functional blocks shown in FIG. 1 by executing a program by computer 10 (computer).

The computer 10 includes a CPU (Central Processing Unit) 11 , a ROM (Read Only Memory) 12 , and a RAM (Random Access Memory) 13 which are connected to a bus 14 . Further, computer 10 includes display device 15 , input device 16 , non-volatile storage 17 and network interface 18 .

The CPU 11 reads the program code of the software that implements each function according to the present embodiment from the ROM 12, loads it into the RAM 13, and executes it. Variables, parameters, etc. generated during the arithmetic processing of the CPU 11 are temporarily written in the RAM 13, and these variables, parameters, etc. are read by the CPU 11 as appropriate. However, an MPU (Micro Processing Unit) may be used instead of the CPU 11 .

The display device 15 is, for example, a liquid crystal display monitor, and displays the results of processing performed by the computer 10 to the user. For example, a keyboard, a mouse, or the like is used as the input device 16, and the user can perform predetermined operation inputs and requests. For example, the computer 10 constituting the user terminal 160 is used as a touch panel display device in which the display device 15 and the input device 16 are integrated.

As the nonvolatile storage 17, for example, HDD (Hard Disk Drive), SSD (Solid State Drive), flexible disk, optical disk, magneto-optical disk, CD-ROM, CD-R, magnetic tape, nonvolatile memory, or the like is used. be done. The nonvolatile storage 17 stores an OS (Operating System), various parameters, and programs for making the computer 10 function. The ROM 12 and the non-volatile storage 17 record programs and data necessary for the operation of the CPU 11, and are examples of computer-readable non-transitory storage media storing programs executed by the computer 10. Used. The user DB 112</b>D of the preprocessing device 112 is constructed in the nonvolatile storage 17 provided in the preprocessing device 112 . Further, the elevator DB 111C of the remote monitoring server 111 is constructed in the non-volatile storage 17 provided in the remote monitoring server 111 .

For example, a NIC (Network Interface Card) or the like is used as the network interface 18, and various data can be transmitted and received between devices via a LAN (Local Area Network), a dedicated line, or the like connected to the terminal of the NIC. It is possible. Each device in elevator system 100 sends and receives messages through network interface 18 . For example, the function of the communication unit 112C of the preprocessing device 112 is implemented by the network interface 18. FIG.

<Example of elevator processing>
FIG. 3 is a flowchart showing an example of elevator processing in the elevator system 100. As shown in FIG. Note that the elevator processing illustrated in FIG. 3 is performed periodically. This elevator process shows an example of an information output method for the elevator system 100 to output congestion information to the user terminal 160 . Here, it is assumed that the application device 150 has already authenticated the user of the user terminal 160 . At this time, the user is on the second floor of the building, for example, and is operating an SNS application installed in the user terminal 160 .

The user terminal 160 transmits a request (call request) for call registration of the elevator 140 to the application device 150 based on the operation of the call registration screen by the user (S1). The call request is sent to preprocessing device 112 via app device 150 . The process of transmitting the call request in step S1 is performed at any timing when the call request is registered by the user terminal 160 . The call request includes information such as the user application ID of the application of the user terminal 160, the elevator ID of the elevator 140 for which call registration has been performed, and the boarding floor and destination floor input via the call registration screen. there is

112 C of communication parts of the preprocessing apparatus 112 determine whether the call request was received from the user terminal 160 (S2). When determining that the call request has been received (YES in S2), the communication unit 112C shifts the process to step S3. On the other hand, when determining that the call request has not been received (NO in S2), the communication unit 112C ends the elevator processing.

If it is determined in step S2 that the call request has been received, the authentication unit 112A of the preprocessing device 112 authenticates the user who performed the call registration (S3). For example, the authentication unit 112A confirms that the call request received by the communication unit 112C is a request to register a call to the elevator 140. FIG. Authentication unit 112A also confirms whether the user application ID included in the call request received by communication unit 112C is registered as a user.

Authentication unit 112A determines whether or not user authentication has succeeded (S4). If the user authentication is successful, the authentication unit 112A shifts the process to step S5 (YES in S4), and ends the elevator process if the user authentication fails (NO in S4).

After the authentication succeeds in step S4, the processing unit 112B determines whether or not the destination floor whose call is registered is the parking floor (S5). When the processing unit 112B determines that the destination floor is not the parking lot floor (NO in S5), the process proceeds to step S12.

On the other hand, when the processing unit 112B determines that the destination floor is the parking floor (YES in S5), the process proceeds to step S6.

The processing unit 112B acquires the number of vehicles waiting to be delivered (S6). At this time, the processing unit 112B receives the number of vehicles in front of the exit gate from the parking lot management device 170 . Processing unit 112B also receives the number of call registrations from remote monitoring server 111 . Then, the processing unit 112B combines the number of vehicles in front of the exit gate received from the parking lot management device 170 and the number of call requests registered in the elevator 140 to determine the number of vehicles waiting to be exited.

Next, the processing unit 112B acquires surrounding congestion information (S7). At this time, the processing unit 112B acquires from the remote monitoring server 111 the elevator ID of the elevator 140 and the location information corresponding to the elevator ID. Then, the processing unit 112B acquires congestion information around the location of the elevator 140 corresponding to the location information from the congestion information device 180 .

Next, the processing unit 112B uses the number of vehicles waiting to be delivered acquired in step S6, the number of call requests set for the elevator 140, and the congestion information around the location of the elevator 140 calculated in step S8 to calculates the waiting time until the vehicle can leave the parking lot (S8). The number of call requests set for the elevator 140 can be obtained from the number of call requests transmitted to the remote monitoring server 111 by the processing unit 112B. Note that the processing unit 112B may obtain the waiting time only from the number of vehicles waiting to be delivered.

Next, the processing unit 112B confirms the waiting time (S9). Here, when the waiting time required for the vehicle to leave the area is equal to or longer than a predetermined time, the processing unit 112B transmits to the user terminal 160 a message for accepting confirmation of whether or not to change the call request. When processing unit 112B receives a call request change from user terminal 160, processing unit 112B ignores the call request received from communication unit 112C in step S2. On the other hand, if the call request from the user terminal 160 is not changed, the call request is transmitted to the remote monitoring server 111 that can set the call request to the elevator 140 . In addition, the processing unit 112B can set a call request to the elevator 140 when the waiting time is less than the predetermined time in step S9, or when the registered destination floor is other than the parking floor (NO in S5). A call request is sent to the remote monitoring server 111 . For example, 30 minutes is set as the predetermined time. Then, if the waiting time is 30 minutes or more, the processing unit 112B shifts the processing to step S10. On the other hand, if the waiting time is less than 30 minutes, the processing unit 112B shifts the process to step S12.

If the waiting time is 30 minutes or more, the processing unit 112B causes the user terminal 160 to display a congestion information message shown in FIGS. 4 to 7, which will be described later, according to the waiting time (S10). The processing unit 112B then transmits a response to the user's reservation change to the preprocessing device 112 .

Display examples of the congestion information message will now be described with reference to FIGS. 4 to 7. FIG.
FIG. 4 is a display example of a congestion information message notifying that the waiting time is 30 minutes or longer.

The congestion information message transmitted from the preprocessing device 112 to the user terminal 160 via the application device 150 is displayed in the SNS application as described by the robot icon. Since the destination floor registered by the user in the call request is the parking floor, this congestion information message indicates that the destination desired by the user is the parking lot, that the parking lot is somewhat crowded, and that the waiting time is long. 30 minutes or longer, and includes information prompting the user to confirm whether or not to call the elevator. The user can confirm that the waiting time is 30 minutes or more.

After that, when the user inputs "yes" (an example of a positive response) to the user terminal 160, the processing unit 112B outputs a call request to the remote monitoring server 111 through the DMZ 113, and the setting unit 111A sends the elevator 140 set call request to Then, the processing unit 112B outputs a message to the user terminal 160 that registered the call request, notifying that the car is heading to the second floor where the user is. After confirming the message displayed on the user terminal 160, the user waits for the arrival of the car on the second floor, which is the boarding floor.

In step S10, the processing unit 112B can also provide the user terminal 160 with information corresponding to the waiting time.
FIG. 5 is a display example of a message including information provided to the user terminal 160 according to the waiting time displayed on the user terminal 160. FIG.

In the SNS application, in addition to the congestion information message shown in FIG. 4, a message including information on facilities that can be used immediately by the user is displayed. At this time, the processing unit 112B can output to the user terminal 160 a message indicating availability of stores and event spaces in the building where the elevator 140 is installed, which the remote monitoring server 111 has collected from the remote monitoring device 130. It is possible. In FIG. 5, a message indicates that the first-floor cafe is available in addition to the second-floor food court where the user is currently located, and can be used immediately. If the waiting time is long, additional information used for the user to relax in the building is displayed on the user terminal 160 according to the waiting time. You don't have to wait for

For example, if the user confirms that the waiting time is 30 minutes or longer and inputs "yes" (an example of a positive response) to the user terminal 160, the call request will be sent to the elevator without the call being cancelled. It is set to 140. On the other hand, the user can read the congestion information message displayed on the user terminal 160 and cancel the call request sent in step S1 if the waiting time seems too long. In the present embodiment, the process of canceling a call request is also called "change of call request". The call is canceled by the user inputting "no" (an example of a negative response) into the user terminal 160. FIG. In this case, the processing unit 112B ignores the call request first registered by the user. Therefore, the process of setting the call request initially registered by the user to the elevator 140 is not performed. Then, the processing unit 112B outputs a message to the user terminal 160 indicating that the call has been cancelled.

The additional information displayed on the user terminal 160 may include various information according to the waiting time. For example, as the additional information, in addition to the shop information shown in FIG. 5, event information in the building is assumed. For example, if the waiting time is short (30 minutes to less than 1 hour), the additional information may include food court introduction information. Introductory information may be included in the additional information.

The affirmative response that the user can enter shown in FIG. 4 and the negative response that the user can enter shown in FIG. 5 may be entered by key input. For example, if the congestion information message includes the content of "to continue the call, enter '1' and to cancel the call, enter '2'", the user will It is also possible to respond by entering one character on the numeric key through the software keyboard displayed on the . If it is a one-character input, the time required for the user to input can be shortened.

FIG. 6 is a display example of a congestion information message notifying that the waiting time is 45 minutes or more.
The congestion information message shown in FIG. 6 differs from the congestion information message explained in FIG. 4 in that the parking lot is crowded and the waiting time is 45 minutes or more.

FIG. 7 is a display example of a congestion information message notifying that the waiting time is 60 minutes or longer.
The congestion information message shown in FIG. 7 is different from the congestion information message explained in FIG. 4 in that it indicates that the parking lot is quite congested and that the waiting time is 60 minutes or longer.

Returning to FIG. 3 again, the description of the elevator processing continues.
After step S10, the processing unit 112B determines whether or not to continue the reservation from the user terminal 160 (S11). "Reservation change" in this flow chart represents the operation of canceling the call request by the user. A change in the call request can be input from the user terminal 160 to which the delivery congestion information is output in this way.

If the reservation is not changed (NO in S11), the processing unit 112B proceeds to step S12. On the other hand, if the reservation is changed (YES in S11), the processing unit 112B ignores the call request that the processing unit 112B received from the communication unit 112C in step S2 (S17), and terminates the elevator processing.

If the destination floor is not the parking lot floor in step S5, if the waiting time is less than 30 minutes in step S9, or if a response to change the reservation has not been received in step S11, the processing unit 112B sends a remote message via the DMZ 113. A call request is transmitted to the monitoring server 111 (S12).

Based on the call request received from the preprocessing device 112, the elevator information acquisition unit 111B of the remote monitoring server 111 searches the elevator DB 111C for the elevator 140 to be registered as a call. Then, the setting unit 111A of the remote monitoring server 111 sets the call information extracted from the call request received from the processing unit 112B to the elevator 140 matching the elevator ID specified by the elevator information acquisition unit 111B (S13). ).

The call information set by the setting unit 111A is set for the specified elevator 140 via the network 101, the communication device 120, and the remote monitoring device . However, upon receiving the reservation change response transmitted in step S11, the setting unit 111A ends the elevator processing because the call request is not registered.

After step S13, the processing unit 112B of the preprocessing device 112 displays a traffic information necessity message shown in FIG. 8 on the user terminal 160 (S14). Here, a traffic information necessity message is displayed on the user terminal 160 via the application device 150 from the processing unit 112B.
FIG. 8 is a display example of a traffic information necessity message.

Here, information is displayed on the user terminal 160 indicating that the car will move from the floor where the user is currently located (eg, the first floor) to the destination floor (eg, the parking lot floor on the sixth floor). In addition, as a traffic information necessity message, a message asking the user whether or not to additionally check the traffic information of the surrounding area is displayed. In this case, when the user inputs "yes" or "no", the input contents are sent to the preprocessing device 112 through the application device 150 as a response to the user's display request.

Returning to FIG. 3 again, the description of the elevator processing continues.
After step S14, the processing unit 112B of the preprocessing device 112 receives a response to the traffic information display request from the user terminal 160, and determines whether or not a display request has been made (S15). Since the user has entered "no", if no display request has been made (NO in S15), the elevator process is terminated. On the other hand, if the display is requested by the user inputting "yes" (YES in S15), the process proceeds to step S16.

When the display request is made in step S15, the processing unit 112B of the preprocessing device 112 displays the traffic information message on the user terminal 160 (S16), and ends this processing. Here, the processing unit 112B receives the elevator ID of the elevator 140 from the remote monitoring server 111 and acquires location information corresponding to the elevator ID. Then, the processing unit 112B generates a traffic information necessary/unnecessary message including a hyperlink of a map around the location provided by the congestion information device 180, and displays it on the user terminal 160. FIG.

FIG. 9 is a display example of a traffic information necessity message including a hyperlink.
The traffic information required/unnecessary message includes a hyperlink to open a map showing traffic information around the location. When the user selects the hyperlink displayed on the user terminal 160, the surrounding map shown in FIG. 10 is displayed.

FIG. 10 is a display example of a peripheral map.
On the surrounding map displayed on the user terminal 160, an entrance/exit 20, a current location icon 21, and congestion display sections 22 and 23 are displayed.
The entrance/exit 20 is an icon representing an entrance/exit from an area provided with a parking lot. The entrance/exit has a function of dividing the area where the parking lot is provided from the road around the parking lot. In this embodiment, an icon representing the entrance/exit is shown, but only an icon representing the position of the exit may be displayed in the surrounding map.

The current location icon 21 is an icon representing the current location of the user (user terminal 160).
The congestion display sections 22 and 23 are displayed in different colors according to road congestion information. For example, congested roads are displayed in red, and moderately congested roads are displayed in orange.
By looking at the surrounding map, the user can check road congestion information and make decisions such as avoiding congested roads.

In the elevator system 100 according to the embodiment described above, the preprocessing device 112 accepts registration of a call request to the elevator 140 using the SNS application. Then, when congestion of vehicles occurs in the building where the elevator 140 for which the call request has been received by the user terminal 160 occurs, the preprocessing device 112 confirms the registration of the congestion congestion information and the call request. to the user terminal 160. Therefore, when the user decides to go to the parking lot floor and registers a call request in the user terminal 160, the user terminal 160 accepts the call request with the destination floor as the parking lot floor. A congestion information message is displayed on the user terminal 160 before payment. The user can check the waiting time included in the delivery congestion information through the congestion information message displayed on the user terminal 160 . Such a configuration of the elevator system 100 allows the user to check the waiting time and determine whether or not to actually register the call request to the elevator 140 .

For example, if the waiting time displayed on the user terminal 160 is longer than expected, the user can operate the user terminal 160 to cancel the once registered call request. In this way, the user can review the delivery, thereby improving convenience for the user.

Also, the user can confirm whether or not the roads around the building are congested based on the congestion information around the building. Therefore, the user can exit the vehicle from the exit leading to a road that is not congested.

Also, if the waiting time is less than 30 minutes, the user often wants to move to the destination floor as the parking lot floor without even checking the congestion information message. Therefore, if the waiting time is less than 30 minutes, by omitting the display of the congestion information message, it is possible to save the user the trouble of confirming the congestion information message. Note that the waiting time used to determine whether to display the congestion information message may be changed for each user. For example, it is possible to change the waiting time to 20 minutes or 40 minutes.

In addition, when the user cancels the call request, the processing unit 112B can correct the delivery congestion information again. Therefore, when another user registers a call request through the other user terminal 160 and the boarding floor and destination floor are set for the elevator 140, the exit congestion information is updated at the time of setting. Therefore, a congestion information message reflecting accurate delivery congestion information is output to other user terminals 160 .

In addition, a call request is registered and delivery congestion information is output only to a user terminal 160 used by an authenticated user, and delivery congestion information is not output to other unauthenticated user terminals 160.例文帳に追加Users of other user terminals 160 do not need to confirm unnecessary information because the congestion information is not output unless they themselves register a call request with the destination floor as the parking floor.

[Modification]
In the above-described embodiment, current congestion information is displayed, but the tendency of past congestion information may be displayed on the user terminal 160, for example. For example, based on the past situation, if the congestion information message indicates that it will be even more crowded after waiting for 30 minutes, the user may allow the 30-minute wait to wait for the vehicle. is decided to issue the

Moreover, the user who confirmed the leaving congestion information may change the destination floor once registered. For example, the user can move to another floor by changing the destination floor to a floor other than the parking lot floor. If the change in the call request is to change the destination floor to a floor other than the parking floor, the processing unit 112B transmits a call request including the changed destination floor to the remote monitoring server 111 in the process of step S12. . In this case, the car travels to the changed destination floor, so the processing unit 112B does not add the changed call request to the number of vehicles waiting to be dispatched.

In addition, a driver who drives a vehicle and a fellow passenger may have separate user terminals 160 . Therefore, when the elevator system 100 receives a call request from the user terminal 160 held by the driver, the process shown in FIG. 3 is performed. When a call request is received from the user terminal 160 held by the driver, the subsequent processing is performed after a YES determination is made in step S5 of FIG. Therefore, when a call request is registered in the elevator 140, the number of this call request is added to the number of vehicles waiting to be delivered.

On the other hand, when a call request is received from the user terminal 160 possessed by the fellow passenger, the process of steps S12 and S13 may be performed after the determination of NO in step S5 of FIG. In order for the elevator system 100 to identify the owner of the user terminal 160 in this way, for example, the user inputs user information indicating whether or not he or she is a driver to an SNS application in advance, User information is sent to the preprocessing device 112 via the device 150 . The processing unit 112B may determine whether the user of the user terminal 160 is a driver or a fellow passenger based on the user information. Note that regardless of whether the user who registered the call request from the user terminal 160 is a driver or a fellow passenger, the parking congestion information may be displayed on any of the user terminals 160 .

The present invention is not limited to the above-described embodiments, and it goes without saying that various other application examples and modifications can be made without departing from the gist of the present invention described in the claims.
For example, the above-described embodiments are detailed and specific descriptions of the system configuration for easy understanding of the present invention, and are not necessarily limited to those having all the described configurations. Moreover, it is possible to add, delete, or replace a part of the configuration of this embodiment with another configuration.
Further, the control lines and information lines indicate those considered necessary for explanation, and not all control lines and information lines are necessarily indicated on the product. In practice, it may be considered that almost all configurations are interconnected.

DESCRIPTION OF SYMBOLS 100... Elevator system, 110... Control center, 111... Remote monitoring server, 111A... Setting part, 111B... Elevator information acquisition part, 111C... Elevator DB, 112... Preprocessing apparatus, 112A... Authentication part, 112B... Processing part, 112C User DB 113 DMZ 120 Communication device 130 Remote monitoring device 140 Elevator 150 Application device 160 User terminal 170 Parking management device 180 Congestion information device

Claims (6)

In an elevator system that dispatches a car to a boarding floor according to a call request from a user's user terminal,
a communication unit that receives the call request from the user terminal;
When the parking floor following the parking lot is included in the call request as the destination floor, leaving congestion information representing congestion until the user's vehicle leaves the parking lot and exits a predetermined area, and a processing unit that outputs to the user terminal having the call request. Elevator system. When the waiting time is equal to or longer than a predetermined time, the processing unit transmits to the user terminal a message for accepting confirmation of necessity of changing the call request, and when the change of the call request is received from the user terminal. and disregarding the call request received from the communication unit, and if the call request is not changed from the user terminal, transmitting the call request to a remote monitoring server capable of setting the call request to the elevator. ,
The elevator system according to claim 1, wherein the remote monitoring server sets the call request received from the processing unit to the elevator. The elevator system according to claim 2, wherein the processing unit provides the user terminal with information corresponding to the waiting time. 4. The elevator system according to claim 3, wherein the exit congestion information includes the waiting time required for the user of the user terminal to leave the parking space of the parking lot and exit the area. Based on the number of vehicles waiting to exit the parking lot, the number of call requests set for the elevator, and congestion information around the building where the parking lot is provided, the processing unit 5. The elevator system of claim 4, wherein waiting time is determined. In an information output method performed in an elevator system that dispatches a car to a boarding floor according to a call request from a user terminal of a user,
a process of receiving the call request from the user terminal;
When the parking floor following the parking lot is included in the call request as the destination floor, leaving congestion information representing congestion until the user's vehicle leaves the parking lot and exits a predetermined area, and a process of outputting to the user terminal having the call request.

Images