JP7106566B2 - Automatic call registration system and automatic call registration method - Google Patents

Description

The present invention relates to an automatic call registration system and an automatic call registration method for an elevator device, and more particularly, to an automatic call registration system and an automatic call registration method for an elevator device having a hall processing function for automatically inputting and displaying the direction of movement in an elevator hall. It relates to a call registration method.

Conventionally, many proposals have been made for operation management of elevator devices. Among these, there is a proposal for a hall display processing function for users of the elevator apparatus to indicate the direction of movement at the hall of each floor or to confirm the direction of movement of the car on the display.

For example, US Pat. a video processor (16) connected to receive the video input of the video processor (16) for tracking objects within the field of view of the video camera and generating occupant data associated with each of the tracked objects; Calculate parameters for elevator controller (24), elevator dispatcher (26), door controller (28), security system (30) based in part on passenger data sent from video processor (16). The security system also operates based in part on data from the access control system (14).'

Japanese Patent Publication No. 2009-523678

According to the device described in Patent Literature 1, elevator dispatch and door control can be performed by using video input from a video camera. However, even in this case, it is necessary to wait for an instruction from the user regarding the destination direction.

Accordingly, it is an object of the present invention to provide an automatic call registration system and an automatic call registration method that can reduce the burden on the user, including the instruction of the destination direction.

From the above, in the present invention, "an automatic call registration system for controlling and managing a hall elevator service request device provided at a hall in a facility, and receiving information for obtaining the number of users of the elevator device and the destination information of the car" a learning unit that stores and learns the number of users and car destination information obtained from the receiving unit as past experience data; It has a prediction unit that predicts and a hall call registration determination unit that automatically displays the destination direction of the car on the hall elevator service request device based on the prediction result of the prediction unit when a person is detected at the hall in the facility. An automatic call registration system characterized by

Further, in the present invention, there is provided an "automatic call registration method for controlling and managing a hall elevator service request device provided at a hall in a facility, in which the number of users of the elevator system and the destination information of the car are obtained and past experience is obtained. Stored as data, using past experience data to predict the destination information of the user for each floor of the hall, and when detecting a person in the hall in the facility, based on the predicted destination direction, the hall elevator service request device An automatic call registration method characterized by automatically displaying the predicted destination direction of the car.

According to the present invention, it is possible to reduce the burden on the user, including the instruction of the destination direction.

BRIEF DESCRIPTION OF THE DRAWINGS The figure which shows schematic structure of the elevator operation management system which concerns on this invention. The figure which showed the suitable platform environment example for this invention. 4 is a diagram showing an example of a storage format of past experience data learned by a learning unit 31; FIG. The figure which shows an example of prediction passenger|occupant number table TB1 predicted by the number-of-persons prediction part 32 by floor. The figure which shows an example of prediction alighting number-of-people table TB2 predicted by the number-of-people-by-floor prediction part 32. FIG. FIG. 2 is a flowchart specifically exemplifying the processing contents of the number-of-persons prediction unit 32 for each floor of FIG. 1 ; The figure which shows an example of estimated passenger number table TB1 containing the actual data added by accuracy verification. FIG. 10 is a diagram showing an example of a predicted number of people getting off the train table TB2 including actual data added in accuracy verification; FIG. 10 is a diagram showing an output example (every one minute) of the predicted number of people getting off the train in chronological order; FIG. 10 is a diagram showing an output example (every 5 minutes) of the predicted number of people getting off the train in time series; The figure which shows the output example which displayed and output the predicted value of the number of boarding/alighting people about each floor. FIG. 10 is a diagram showing an output example of displaying and outputting predicted values and actual values of the number of boarding and alighting passengers for each floor; The figure which shows the example which arrange|positioned the boarding/alighting number of people vertically and horizontally, and displayed and output so that the present elevator usage situation can be grasped. FIG. 10 is a diagram showing a flow example specifically illustrating the processing contents of a hall call registration determination unit 39; FIG. 12 is a diagram showing changes in display contents of the platform elevator service request device 4 at the time of the flow of FIG. 11;

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 shows a schematic configuration of an elevator operation management system that implements an automatic call registration system and registration method according to the present invention. In FIG. 1, facilities and systems in a facility such as a building 1 and an external system 2 are described.

Among these, facilities and systems in facilities such as the building 1 generally include an elevator operation management system 3, a platform elevator service request device 4 on each floor, a monitoring camera 5 on each floor, a building management system 6, and the like. Data communication is performed between them via the communication means 8 . A plurality of elevator control systems 7 a . . . 7 n are installed and controlled by an elevator operation management system 3 . In implementing the present invention, the elevator operation management system 3 and the building management system 6 do not need to be facilities and systems in facilities such as the building 1 . As long as mutual data communication is performed via the communication means 8, similar control and monitoring are possible even if some or all of the functions are installed outside the facility such as the building 1. FIG.

Furthermore, FIG. 1 illustrates a public institution management system as an example of the external system 2, but it may be a taxi dispatch system or the like.

The elevator operation management system 3 according to the present invention obtains many inputs and settings and gives outputs. Among these inputs and outputs, between the elevator control systems 7a . . . 7n and the elevator operation management system 3, the elevator control systems 7a . 7a . . . 7n select the allocated car after the landing button of each car elevator is pressed by the control command signal S72 from the elevator operation management system 3 . What is characteristic here is that the elevator operation management system 3 operates and manages all the elevators in the building 1, and other matters are the same as in normal elevator control, so explanation here will be made. omitted.

In the present invention, further inputs include a service request signal S4 from the hall elevator service request device 4 on each floor, a video signal S5 from the surveillance camera 5 on each floor, building management information S6 from the building management system 6, and a public institution management system 2. Public institution management information S2 and the like are obtained.

Further, as a service guidance signal SS4, guidance information such as whether the registration has been correctly executed or which elevator is to be dispatched is transmitted to the elevator side in response to the service request signal S4.

FIG. 2 is a diagram showing an example of a hall environment suitable for the present invention. At the elevator hall on each floor, surveillance cameras 5 (5-1, 5-2, 5-3, 5-4) for monitoring and photographing the space including the elevator door and up/down buttons 4 as the hall elevator service request device 4 are installed. (4-1, 4-2, 4-3, 4-4) are installed. Further, in FIG. 2, 20 (20-1, 20-2, 20-3) are lanterns for forecasting the arrival of elevator cars and for informing reservation status. In FIG. 2, a car interior camera 21 and a load sensor 22 are further provided in the car 24 of the elevator.

As will be explained below, the positioning of the service request signal S4 in the present invention is to confirm the ascending or descending direction of the elevator. may be a destination floor registration device or the like.

Also, the positioning of the video signal S5 in the present invention is for measuring the number of users, and it can be substituted by any other means that can directly or indirectly confirm the number of users. In the example of FIG. 2, it is possible to obtain information on the number of passengers from a car camera 21 provided inside the elevator car 24 and a load sensor 22 provided at the bottom of the elevator car 24 .

Thus, from the service request signal S4, it is possible to confirm the ascending and descending direction of the elevator, from the video signal S5, it is possible to confirm the number of users, and from the building management information S6, it is possible to confirm the meeting in the facility. , events, etc., can be confirmed, and from the public institution management information S2, it is possible to grasp the operation information of the public institutions on the day (for example, train delays). It should be noted that some of this information includes information that is also input in existing systems and used for some purpose, but in the present invention, it is new in that it is used for estimating the predicted number of people getting off.

1 receives the service request signal S4, the video signal S5, the building management information S6, etc. via the communication means 8, and also receives the operating conditions from the elevator control systems 7a . . . 7n. Input information S71. The driving state information S71 includes information on the position of the car.

The input signal from the receiving section 36 is given to and used by the platform call registration determination section 39 and the learning section 31. Since these are essential parts of the present invention, they will be described later, and generally First, the general evaluation section 37 and the assignment command section 38, which are the main functions, will be explained.

The comprehensive evaluation unit 37 determines the user's request and movement direction from these input signals, and the assignment command unit 38 gives a control command signal S72 to the elevator control system 7a . . . 7n of each car. to control. Since this part is the same as the conventional elevator control, further explanation is omitted.

The service request signal S4, the video signal S5, the building management information S6, etc. obtained via the communication means 8 are recorded in the learning section 31 and used. Furthermore, the number of users is also detected from a car camera 21 provided in the elevator car 24 and a load sensor 22 provided in the lower part of the elevator car 24, which are transmitted from the elevator control system 7a...7n. Based on the information and the position of the elevator car, it is possible to grasp the number of passengers and the number of passengers getting off for each floor. Here, the service request signal S4 and the video signal S5 are stored together with information on the time when these signals were generated, and are used as experience information in the past. As a result, the user's behavior and mode at a certain past scene (day of the week, season, etc.) at a certain time can be statistically grasped. For example, it is possible to grasp the outline of the movement of people at the time of going to work, at lunch time, at the time of leaving work, and the like. Therefore, in a similar future scene, although individuals do not behave in the same way, the macroscopic traffic flow of the entire building can be presumed to show the same traffic flow as the past experience.

While the service request signal S4 and the video signal S5 are used as experience information in the past, the building management information S6 from the building management system 6 is used as a schedule of activities such as meetings and events in the facility in the near future. (Holding place, attendees and their place of attendance), etc. are information registered in the building management system 6. According to this, for example, at the time of the meeting from 3 o'clock today, the movement of people from each floor is Predictable.

If, for example, train delays and their degree can be grasped from the public institution management information S2 as the operation information of the public institutions on the day, the travel trends of users especially when going to work will differ from the travel trends during normal times when there is no delay. , is predictable to change. As is clear from this, the public institution management information S2 can be used as correction information for predictions determined from experience information in the past or plans in the near future.

In this way, the learning unit 31 learns the number of people who normally use the elevator on a daily basis. Here, it is possible to output macro number-of-people information. Further, the learning section 31 has a boarding rate setting section 40, which compares the number of people in the elevator car with the daily number of people in the boarding hall, and learns the boarding rate for each floor.

Here, the floor-by-floor occupancy rate is the ratio of the number of passengers to the capacity of the elevator for each floor, each floor and each vertical direction of the stop floor or destination floor. This may be not the number of people, but the ratio of the area occupied in the car. These changes depending on the time period and the situation, and the setting of the boarding rate may be a system that changes for each time period, a system that changes according to an arbitrary mode, or a system that has a fixed value. Specifically, when the maximum number of passengers per day is 16, this passenger ratio is 70% when the capacity is 24 passengers. By correctly learning this occupancy rate, it is possible to optimize the operation pattern of more accurate number of passengers.

The past experience data learned by the learning unit 31 is organized and stored as shown in FIG. 3, for example. FIG. 3 exemplifies a storage format for the number of passengers in the past, for example, in which the number of passengers on each floor and the information on the boarding rate for each floor and up and down are stored in association with each past date and time. there is A storage format for the number of people who have landed in the past is created in the same format. It should be noted that the above-mentioned storage format should preferably include information that is stored after grasping the number of people every day, for example, every five minutes, and that has been accumulated over a long period of time. The past experience data should preferably include event information such as conferences and various events as incidental information. The past experience data learned by the learning unit 31 is used as past experience for prediction processing in the following processes.

This 5 minutes is a time span used for the scale used when planning the installation of elevators, and is not limited to this. For example, it may be determined for each case for each cycle time of the elevator, or a fixed width other than 5 minutes may be specified. Further, the resolution may be calculated in increments of 1 minute, and may be appropriately processed to 5 minutes or 10 minutes.

The number-of-personnel prediction unit 32 for each floor predicts the movement of people in an arbitrary time span from the current time, or the movement of people in the traffic flow of the building recognized by the learning unit 31, based on past experience, meeting schedules for the day, etc. to predict the number of people by floor. FIG. 4a shows an example of a predicted passenger number table TB1 predicted by the floor-specific passenger number prediction unit 32, and FIG.

The predicted number of passengers table TB1 and the predicted number of alighting passengers table TB2 are arranged sequentially from the top, including time data D1, D6, floor data D2, D7, predicted number of people data D3, D8, actual number of people data D4, D9, prediction accuracy data D5, D10, It is composed of boarding ratios D11 and D12. The number-of-personnel-predicting unit 32 for each floor forms data from the top to the third level in these tables using the past experience data shown in FIG.

For example, in the predicted number of passengers table TB1, at 8 o'clock (which will be described later, for example, represents five minutes from 8 o'clock), the number of passengers on each floor (here, from the first floor to the eighth floor) is 20 and 9, respectively. , 7, 14, 13, 7, 8, and 5. Further, for example, with regard to the predicted number of people getting off the table TB2, at 8:00 (which will be described later, for example, represents five minutes from 8:00), the number of people getting off at each floor (here, from the 1st floor to the 8th floor) is 20, 20, and 20 respectively. 5, 9, 15, 11, 15, 18, 11 people are predicted.

As for the method of creating the predicted number of passengers table TB1 and the predicted number of alighting passengers table TB2, as described above, it is possible to prepare the tables in consideration of past experiences and today's schedule, and furthermore, in consideration of today's train delays and the like. It can be obtained by correction.

FIG. 5 is a flowchart specifically exemplifying the processing contents of the number-of-persons prediction unit 32 for each floor in FIG. As a premise for this, the number of passengers measured in chronological order on a daily basis is grasped together with information on the boarding rate for each floor and in the ascending and descending direction by the processing in the learning unit 31, and the past experience data shown in FIG. 3 is formed. shall be In other words, it is assumed that the past experience data corresponding to the actual number of people data D4 and D9 are secured and stored in chronological order for a corresponding number of days in the predicted number of passengers table TB1 and the predicted number of alighters table TB2. In addition, it is assumed that past days are stored including information on events and meetings that took place on that day.

The processing in FIG. 5 may be started at an appropriate timing. For example, if information for the next day is provided on the previous day, it will be processed at an appropriate time on the previous day. Alternatively, if it is provided upon request from the outside, it may be started at the time of request.

In the first processing step S100 of the number-of-persons prediction unit 32 for each floor, past experience data and the like are fetched. This data includes past actual number data D4, D9, time data D1, D6, boarding rate, building management information S6, and the like. In processing step S101, setting information such as time width and designated time is taken in.

In processing step S102, the output date (for example, tomorrow) is determined. It is determined whether the output day is a weekday, a holiday, or a partial holiday, and only those corresponding to the relevant conditions are extracted from the past experience data of FIG. In processing step S103, for example, if the output day is a weekday, only weekday past experience data is extracted, and if the output day is a holiday, only holiday past experience data is extracted. Note that when seasonal fluctuations and day-of-week fluctuations are conspicuous in terms of users, it is preferable to take these points into consideration when extracting.

In processing step S104, hourly hourly usage averages are obtained for the extracted time-series usage records for a plurality of days, and these are used as forecasted number of passengers data D3 and D8 in forecasted number of passengers table TB1 and forecasted number of alighters table TB2. Since the above process is performed on the number of users for each floor, the floor data D2 and D7 are also obtained.

In processing step S105, the presence or absence of building management information S6 is confirmed. For example, if a meeting is scheduled to be held from 15:00 today, in processing step S106, the movement of users and the operation of the elevator are determined according to the scale of the meeting. The predicted number of passengers D3 and D8 in the predicted number of passengers table TB1 and the predicted number of alighters table TB2 obtained in processing step S104 are corrected by reflecting the manner of use. In addition, in the past experience data, if there is an experience that a conference with the same purpose as this conference was held in the past, the predicted number of passengers table TB1 and the predicted number of people getting off will be calculated by referring to the user information at that time. It is preferable to correct the predicted number of people data D3 and D8 in the table TB2.

In processing step S108, the presence or absence of public institution management information S2 is confirmed. , depending on the extent of the delay, reflecting the movements of the users and how to use the elevator, the predicted number of people data D3 and D8 of the predicted number of passengers table TB1 obtained in processing steps S104 and S106 and the predicted number of people getting off the table TB2 are updated. fix it.

As described above, the past results are corrected based on the action schedule and information of public institutions, and the predicted number of people data D3 and D8 of the predicted number of passengers table TB1 and the predicted number of people getting off the train TB2 are obtained. Although not specified in the flow of FIG. 5, the occupancy rate data in the past empirical data of FIG. be done.

The number-of-personnel-prediction unit 32 for each floor further has an accuracy verification function. to add data. FIG. 6a shows an example of a predicted number of passengers table TB1 including actual data added by accuracy verification, and FIG. 6b shows an example of a predicted alighting number table TB2 including actual data added by accuracy verification.

In this example, for example, for the predicted number of passengers table TB1, at 8 o'clock (which will be described later, for example, represents five minutes from 8 o'clock), the number of passengers on each floor (here, from the 1st floor to the 8th floor) is Although it was predicted to be 20, 9, 7, 14, 13, 7, 8, and 5, respectively, it is actually 18, 13, 10, 19, 14, 14, 10, and 9, and the accuracy of each is It turns out that it was 82, 38, 60, 75, 92, 88, 95, 90%.

Also, in this case, for example, for the predicted number of people getting off the table TB2, at 8:00 (which will be described later, for example, represents five minutes from 8:00), the number of people getting off at each floor (here, from the 1st floor to the 8th floor) is , were predicted to be 20, 5, 9, 15, 11, 15, 18, and 11, respectively, but the actual numbers were 17, 13, 15, 12, 12, 17, 19, and 10, respectively, and the respective accuracies was 89, 69, 70, 74, 93, 50, 80 and 56%.

The addition of the data D4 and D9 to the tables of FIGS. 6a and 6b means that they have been added to the learning unit 31 as new past experience data.

According to the automatic call registration system according to the present invention described above, the automatic call registration system acquires the number of users of the elevator device and the destination information of the car, and based on these past experience data, It predicts the destination information of the user. The destination information includes destination direction information, destination floor information, or car position information, and in actual operation, the predicted destination direction of the car is automatically displayed. Information on the position of the car becomes destination information of the car by grasping this in chronological order.

The result of the processing in the number-of-personnel prediction unit 32 for each floor can be displayed and output in an appropriate format on a monitor (not shown in FIG. 1) or the like. In this case, the information on the predicted number of passengers and the predicted number of people getting off obtained by the floor-by-floor number prediction unit 32 is appropriately processed and output to the inside and outside of the elevator operation management system 3 . The internal output destination is a monitor within the system or the like, and the external output destination is a building management system 6 or an external system 2 such as a public institution management system. At the time of display output, for example, a time width, a designated time, and the like are referred to as appropriately set contents.

In many cases, the output format (display format) of the information on the predicted number of passengers and the predicted number of alighters output here does not matter. In extreme cases, the raw information may be unprocessed, and the building management system 6 or the external system 2 on the user side may appropriately interpret, process, and use it according to the purpose of use. . Output examples and usage examples are explained below.

7a and 7b are diagrams showing output examples of predicted number of people getting off the train in time series. The accuracy data D10 are summarized as time-series data in increments of 1 minute in FIG. 7a and 5 minutes in FIG. 7b. It should be noted that the distinction between 1-minute increments and 5-minute increments, or the time in the 8 o'clock range is appropriately given as time width setting and time setting.

FIG. 8 displays and outputs predicted values of the number of boarding and alighting passengers for each floor, and FIG. 9 displays and outputs actual values (dotted lines) superimposed thereon.

This information is intended to facilitate understanding of FIGS. 7a and 7b. For example, it requests hourly information for the past day from the elevator operation management system 3 via the network 8, and outputs the above-described predicted values and measured values. Output this information to a monitoring panel installed in the building management room, a PC, or a Web content management screen for building management so that the information can be used to indicate the daily usage status of the building for the building manager, By visualizing the usage status in the building, administrators can flexibly respond to building security and air conditioning equipment schedules. In addition, the output method may include only the measured values without including the predicted values.

FIG. 10 shows an example in which the number of passengers getting on and off is arranged vertically and horizontally, and displayed and output so that the current elevator usage status can be grasped. Normal use, lunch, uphill, downhill peaks, etc. can be identified according to the area determined by the number of people boarding and alighting vertically and horizontally.

Returning to FIG. 1, in the hall call registration determination unit 39 of the elevator operation management system according to the present invention, the display control in the hall elevator service request device 4 of each floor is performed as follows.

FIG. 11 is a flow diagram specifically illustrating the processing contents of the hall call registration determination unit 39. As shown in FIG. The process of FIG. 11 is activated at a constant control cycle of the computer in the elevator operation management system.

In S200, which is the first processing step in FIG. 11, it is determined from the information of the surveillance camera 5 on each floor that a new user has been detected at the boarding point of each floor. If detected, in processing step S201, it is determined that the probability that the person will use the elevator is equal to or greater than a certain value. For this determination, the estimated number of passengers D3 and D8 in FIGS. 4a and 4b (when the number of users is estimated to be large, it can be determined that the probability of using the elevator is greater than a certain value), or the monitoring camera It is possible to take into consideration the behavior obtained from (approaching the elevator, waiting).

Furthermore, when it can be determined that the probability of using the elevator is high, in processing step S202, it is determined in which direction the user wishes to move in the upper or lower direction. This determination can be made using the occupancy rates D11 and D12 in FIGS. 4a and 4b. If it can be estimated that the probability of upward movement is high, an upward call button is automatically registered in processing step S203, and if it can be estimated that the probability of downward movement is high, the downward direction is processed in processing step S204. automatically register the call button. Further, by this registration, the vertical direction is displayed on the call button (platform elevator service request device 4) of the relevant floor.

After the automatic registration of the call button, a timer starting process is performed in processing step S205.

In processing step S206, it is determined whether "no new person is detected" in processing step S200, "elevator usage probability is low" in processing step S201, or "after timer activation" in processing step S205. In the state, it is further confirmed that the button in the other direction has been registered before the timer expires. It should be noted that the registration of the button for the other direction here is made by direct operation of the call button (platform elevator service request device 4) of the floor by the user of the floor concerned.

If the button for the other direction is not registered, the series of processes is terminated and the next control period is awaited. The automatic registration in the movement direction set in step S204 is canceled, and the control of the elevator is changed toward the movement direction of the call whose registration has been confirmed in processing step S206.

FIG. 12 shows changes in display contents of the platform elevator service request device 4 at the time of the flow of FIG. In (a), there is no one in the hall below it, and therefore the display contents of the hall elevator service request device 4 are not displayed either above or below. In (b), the monitor camera 5 detects a person who seems to be a user, and the elevator operation management system 3 predicts that the elevator will go down, for example, and automatically displays the downward direction. (c) is a case in which the prediction was wrong, and the user himself operated the platform elevator service request device 4 to instruct the upward direction again. In the state (e) after the instruction correction, the display of the downward direction disappears and the upward direction is displayed again. (d) is a case where the prediction is correct, and the downward display continues.

If a new person appears from (e) and it is determined that the person is likely to go down, the downward direction is displayed again.

The display of the present invention described above is characterized in that the state changes from (b) to (e). If the prediction is wrong, accept it and correct the display. By the way, in the case of the conventional device, if the upward direction is indicated during the downward lighting, the upward and downward lighting is performed.

Since the movement direction is uniquely determined on the top floor and the bottom floor, the present invention is preferably applied to intermediate floors. By adopting the present invention, the user can omit unnecessary operations of the platform elevator service request device 4 .

1: Facilities such as buildings, 2: External system (public institution management system), 3: Elevator operation management system, 4: Platform elevator service request device on each floor, 5: Surveillance camera on each floor, 6: Building management system, 7a ... 7n elevator control system, 8: communication means, 31: learning unit, 32: number of people prediction unit for each floor, 36: receiving unit, 37: comprehensive evaluation unit, 38: allocation command unit, 39: hall call registration determination S2: public institution management information, S4: service request signal, S5: video signal, S6: building management information, S72: control command signal

Claims (12)

An automatic call registration system for controlling and managing a hall elevator service request device provided at a hall in a facility,
A receiving unit for obtaining information on the number of users of an elevator device and destination information on cars, a learning unit for storing and learning the number of users and destination information on cars obtained from the receiving unit as past experience data, and the learning unit. a prediction unit for predicting destination information of users for each floor of the hall using information stored in the unit; Equipped with a hall call registration determination unit that automatically displays the destination direction of the car on the service request device,
The prediction unit predicts the predicted number of users, actual number of users, and prediction accuracy information for each time, floor, and vertical direction as the destination information,
The hall call registration determination unit detects a person at the hall in the facility, and when determining that the probability of using the elevator is high, uses the destination information for each vertical direction to move to the side where the probability of movement is high. automatically displays the first direction as the destination direction on the platform elevator service request device, and when the person instructs the second direction as the destination direction by the platform elevator service request device , the second direction input is before the timer has elapsed, the automatic display of the first direction displayed on the platform elevator service request device is canceled, and if the input of the second direction is after the timer has elapsed, the first direction is indicated. An automatic call registration system characterized by continuing automatic display as a destination direction . The automatic call registration system of claim 1, wherein
The automatic call registration system, wherein the prediction unit obtains event schedule information in the facility, and predicts the destination direction of the user for each floor of the hall from the event schedule information and the past experience data. An automatic call registration system according to claim 1 or claim 2 ,
The automatic call registration system, wherein the prediction unit obtains operation information of a public institution, and predicts the destination direction of the user for each floor of the boarding hall from the operation information and the past experience data. An automatic call registration system according to any one of claims 1 to 3 ,
The automatic call registration system, wherein the prediction unit obtains the information on the destination direction to be automatically displayed as information for each preset time zone. An automatic call registration system according to any one of claims 1 to 4 ,
The automatic call registration system, wherein the destination information of the car is information of the destination direction of the car, information of the destination floor, or information of the position of the car. An automatic call registration system according to any one of claims 1 to 5 ,
The automatic call registration system, wherein the destination information of the user is information of the destination direction or the destination floor of the user. An automatic call registration method for controlling and managing a hall elevator service request device provided at a hall in a facility, comprising:
The number of users of the elevator device and the destination information of the car are obtained and stored as past experience data, the past experience data is used to predict the destination information of the users for each floor of the hall, and the number of people at the hall in the facility is detected, based on the predicted destination direction, automatically display the predicted destination direction of the car on the platform elevator service request device,
predicting the predicted number of users, actual number of users, and prediction accuracy information as the destination information for each time, floor, and vertical direction;
When it is determined that a person is detected at the platform in the facility and the probability of using the elevator is high, the destination information for each vertical direction is used to select the first direction with the high probability of movement as the destination direction. is automatically displayed on the hall elevator service request device, and when the person designates the second direction as the destination direction by the hall elevator service request device , if the input of the second direction is before the timer elapses, Canceling the automatic display of the first direction displayed on the platform elevator service request device, and continuing automatic display of the first direction as the destination direction if the input of the second direction is after the timer has elapsed . An automatic call registration method characterized by: The automatic call registration method of claim 7 , wherein
An automatic call registration method comprising the steps of obtaining event schedule information within the facility, and predicting the destination direction of users for each floor of the hall from the event schedule information and the past experience data. An automatic call registration method according to claim 7 or claim 8 ,
1. An automatic call registration method, comprising the steps of: obtaining operation information of a public institution; and predicting the destination direction of a user for each floor of a hall from the operation information and past experience data. The automatic call registration method according to any one of claims 7 to 9 ,
1. An automatic call registration method, wherein the information of the destination direction to be automatically displayed is obtained as information for each preset time zone. The automatic call registration method according to any one of claims 7 to 10 ,
The automatic call registration method, wherein the destination information of the car is information of the destination direction of the car, information of the destination floor or information of the position of the car. The automatic call registration method according to any one of claims 7 to 10 ,
An automatic call registration method, wherein the information is the user's destination information, the user's destination direction information, or the destination floor information.

Images