Elevator control system and elevator control method

The elevator control system analyzes historical data to predict call locations and strategically positions the elevator, addressing the inefficiency caused by long waiting times due to distance from the call floor, thereby enhancing operational efficiency.

WO2024232658A1PCT designated stage expired Publication Date: 2024-11-14HYUNDAI ELEVATOR CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/006183
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-08
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Elevator operation efficiency decreases due to increased waiting times as the distance between the elevator's current location and the floor where a call is made increases, as the elevator typically returns to its last stop or the lobby before responding to calls.

Method used

An elevator control system that processes and analyzes operation information to predict the target floor based on historical call data, using a call count matrix and weight matrix to determine the most likely floor for calls, and prioritizes moving the elevator to this predicted location to reduce waiting times.

Benefits of technology

This approach enhances elevator operation efficiency by strategically positioning the elevator at anticipated call locations, thereby reducing user waiting times and improving overall system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006183_14112024_PF_FP_ABST
    Figure KR2024006183_14112024_PF_FP_ABST
Patent Text Reader

Abstract

This elevator control system comprises: a data processing unit configured to process elevator operation information; a data storage unit configured to store the elevator operation information, wherein the elevator operation information includes call unit data including a date and time when a call is generated in a call unit and a floor where the call is generated; an analysis unit configured to predict a target floor of an elevator on the basis of the elevator operation information; and an elevator control unit configured to operate the elevator to the target floor of the elevator.
Need to check novelty before this filing date? Find Prior Art

Description

Elevator control system and elevator control method

[0001] The present disclosure relates to an elevator control system and an elevator control method.

[0002] In buildings equipped with elevators, the floors where elevator calls are most frequently generated vary depending on the building's characteristics, users, and time of day. Typically, elevators are located on the last floor they arrive at or automatically move to the lobby floor to await the next call. In response to a call, the elevator moves to the requested floor. The farther the elevator is from the floor where the call originated, the longer the user's wait time will be. Consequently, elevator operation efficiency can be reduced.

[0003] Prior patent literature

[0004] Korean Patent Publication No. 10-1999-012986

[0005] Korean Patent Publication No. 10-2000-0076382

[0006] Move the elevator to the floor where a call is expected to occur, thereby improving elevator operation efficiency.

[0007] According to one aspect of the present disclosure, an elevator control system includes a data processing unit configured to process elevator operation information; a data storage unit configured to store the elevator operation information, wherein the elevator operation information includes call unit data including a date and time when a call occurred and a floor on which the call occurred for each call; an analysis unit configured to predict a target floor of an elevator based on the elevator operation information; and an elevator control unit configured to operate an elevator to the target floor of the elevator.

[0008] In one embodiment, the analysis unit may be configured to organize the call unit data by day of the week to create a call count matrix in which the horizontal axis represents time and the vertical axis represents the floor in which the call occurred.

[0009] In one embodiment, the analysis unit may be configured to generate a weight matrix having the same dimension as the call count matrix based on the time at which the elevator operation information was aggregated, and to generate a score matrix by multiplying the call count matrix and the weight matrix.

[0010] In one embodiment, the elevator control unit may be configured to determine whether the elevator is in operation, and in response to determining that the elevator is not in operation, to operate the elevator to the target floor.

[0011] In one embodiment, the elevator control unit may be configured to receive an elevator call from a user and to operate the elevator with priority given to the elevator call, regardless of whether the elevator is operated to the target floor in response to receiving the elevator call.

[0012] In one embodiment, the data storage unit may be configured to store the call unit data by grouping it by day of the week, time, and destination floor.

[0013] According to one aspect of the present disclosure, a method for controlling an elevator by an elevator control system includes: receiving and storing elevator operation information; analyzing the elevator operation information to generate call unit data including a floor and time at which an elevator call occurred; generating a call count matrix based on the call unit data, in which a horizontal axis is time and a vertical axis is the floor at which the call occurred; predicting a target floor of an elevator based on the call count matrix; and operating an elevator to the target floor.

[0014] In one embodiment, the step of predicting the target floor of the elevator based on the call count matrix may include the steps of generating a weight matrix having the same dimension as the call count matrix based on the time at which the elevator operation information was aggregated, generating a score matrix by multiplying the call count matrix and the weight matrix, and predicting the target floor of the elevator based on the score matrix.

[0015] In one embodiment, the method may further include: receiving an elevator call from a user; and operating the elevator with priority given to the elevator call, regardless of whether the elevator is operated to the target floor in response to receiving the elevator call.

[0016] In one embodiment, the step of generating a call count matrix based on the call unit data, in which the horizontal axis is time and the vertical axis is the floor where the call occurred, may include the step of grouping and storing the call unit data by day of the week, time, and target floor.

[0017] Elevator operation efficiency can be improved by moving the elevator to a location where an elevator call is expected to occur at a preset time (e.g., in seconds or minutes).

[0018] FIG. 1 is a block diagram of an elevator control system according to one embodiment of the present disclosure.

[0019] FIG. 2 is a block diagram of an elevator control system according to one embodiment of the present disclosure.

[0020] FIG. 3 is a block diagram of an elevator control system according to one embodiment of the present disclosure.

[0021] FIG. 4 is a flowchart illustrating a method for storing elevator operation information according to one embodiment of the present disclosure.

[0022] FIG. 5 is a drawing illustrating an elevator control method according to one embodiment of the present disclosure.

[0023] FIGS. 6 to 8 are matrices for predicting the expected position of an elevator according to one embodiment of the present disclosure.

[0024] Below, with reference to the attached drawings, embodiments of the present disclosure are described in detail so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein.

[0025] And in order to clearly explain the present disclosure in the drawings, parts unrelated to the explanation are omitted, and similar parts are given similar drawing reference numerals throughout the specification.

[0026] Throughout the specification, whenever a part is said to "include" a component, this does not mean that it excludes other components, but rather that it may include other components, unless otherwise stated.

[0027] It should be understood that the technology described in this disclosure is not intended to be limited to a particular embodiment, but rather encompasses various modifications, equivalents, and / or alternatives of the embodiments of this disclosure.

[0028] The expression "configured to" as used herein may be used interchangeably with, for example, "suitable for", "having the capacity to", "designed to", "adapted to", "made to", or "capable of", depending on the context. The term "configured to" may not necessarily mean only something "specifically designed to" in terms of hardware. Instead, in some contexts, the expression "a device configured to" may mean that the device is "capable of" in conjunction with other devices or components.

[0029] The prior art documents described in this disclosure are incorporated herein by reference in their entirety, and it will be understood that the teachings of the prior art documents can be applied by a person having ordinary skill in the art to the parts briefly described in this disclosure.

[0030] FIG. 1 is a block diagram of an elevator system (10) according to one embodiment of the present disclosure.

[0031] Referring to FIG. 1, an elevator control system (10) includes an elevator management device (12), an edge device (14), and a cloud environment (16). The elevator management device (12) may include a control panel that controls an elevator. The edge device (14) may include physical hardware located at a remote location at the network edge. The edge device (14) may be equipped with resources such as a memory and a processor that can collect, process, and execute data in real time with limited assistance from the cloud environment (16). Although the elevator management device (12) and the edge device (14) are illustrated separately in FIG. 1, this is merely exemplary, and it will be understood that the elevator management device (12) and the edge device (14) may be provided as a single device and installed in a building in which an elevator is installed. In one embodiment, the edge device (14) may include any device (e.g., a computing device, a smart device, etc.) equipped with memory and a processor, connected to a cloud environment (16), and capable of utilizing a database (18) of the cloud environment (16). It will be appreciated that the cloud environment (16) may include a database (18) and the configuration necessary to perform general server functions. For example, the cloud environment (16) may be understood as a cloud server. The database (18) of the cloud environment (16) may be configured to store data received from the edge device (14).

[0032] In one embodiment, the edge device (14) is configured to transmit elevator operation information to a database (18) of a cloud environment (16). The edge device (14) may be configured to transmit the elevator operation information to the database (18) of the cloud environment (16) at preset intervals. Accordingly, the database (18) of the cloud environment (16) may accumulate elevator operation information. The edge device (14) may also store the elevator operation information in its own memory. The edge device (14) may be configured to implement an algorithm for determining which floor the elevator will be located on at preset intervals based on the data accumulated in the database (18) of the cloud environment (16). Alternatively, the cloud environment (16) may be configured to implement an algorithm for determining which floor the elevator will be located on at preset intervals based on the accumulated data. That is, the cloud environment (16) may implement an algorithm and transmit the algorithm to the edge device (14). In one embodiment, the edge device (14) and the cloud environment (16) may operate as a distributed computing system.

[0033] In FIG. 1, the edge device (14) and the cloud environment (16) are shown separately for convenience, but it will be understood that the method performed through the edge device (14) and the method performed by the cloud environment (16) can be described as a method performed by a single device if performed by a single management entity. In addition, it will be understood that the edge device (14) can directly perform elevator control, or the cloud environment (16) can perform elevator control. In addition, the steps performed by the edge device (14) can be performed by the cloud environment (16), and the steps performed by the cloud environment (16) can be performed by the edge device (14).

[0034] In one embodiment, the edge device (14) is configured to generate a prediction algorithm for predicting a floor on which an elevator is expected to be called based on accumulated elevator operation information. The edge device (14) may update the prediction algorithm based on the accumulated elevator operation information at preset intervals, for example, in units of seconds (1 second, 2 seconds, 3 seconds, 4 seconds, 5 seconds, …10 seconds, 20 seconds, 30 seconds, etc.), minutes (1 minute, 2 minutes, …10 minutes, etc.), hours, days, weeks, and months. The edge device (14) may receive the accumulated elevator operation information from the cloud environment (16). The edge device (14) may use the prediction algorithm to predict the floor location of the elevator in units of seconds (1 second, 2 seconds, 3 seconds, 4 seconds, 5 seconds, …10 seconds, 20 seconds, 30 seconds, etc.), minutes (1 minute, 2 minutes, …10 minutes, etc.), hours, and the like.

[0035] The elevator management device (12) may be configured to collect elevator operation information and transmit the collected information to the edge device (14). The elevator management device (12) may be configured to collect the collected elevator operation information and transmit it to the edge device (14) at a preset time, for example, in units of milliseconds, seconds, minutes, etc. The edge device (14) may be configured to transmit the elevator operation information to the cloud environment (16) at a preset time, for example, in units of milliseconds, seconds, minutes, etc. The elevator operation information transmitted by the elevator management device (12) to the edge device (14) may be included in data in the form of hexadecimal (source data). The edge device (14) or the cloud environment (16) may be configured to extract the elevator operation information from the data in the form of hexadecimal. In one example, extracting the elevator operation information from the data in the form of hexadecimal may be referred to as data preprocessing. It will be understood that the data in the form of hexadecimal is exemplary and may be in other formats. In one embodiment, the elevator operation information may include the time (including date, day of the week, hour, minute, second, weekend or holiday) at which a request (car request, hall request) occurred, the direction of movement, the waiting time, etc. The elevator operation information may include the characteristics of the elevator, including the maximum floor, rated speed, main board version, etc. The edge device (14) or the cloud environment (16) may group (organize) and store the extracted elevator operation information as desired information. For example, the organized information may be stored in a storage unit (not shown) of the edge device (14) or a database (18) of the cloud environment (16). In one embodiment, the organized information may include the time (e.g., day of the week, hour, minute) at which an elevator call occurred, the floor at which the request occurred, and the target floor.

[0036] In one embodiment, the database (18) of the cloud environment (16) may store raw data or may store elevator operation information extracted from the raw data.

[0037] The edge device (14) transmits the expected algorithm application result to the elevator management device (12), and the elevator management device (12) can use the result to move the elevator to the floor where the elevator is expected to be requested.

[0038] That is, the edge device (14) or cloud environment (16) can use a prediction algorithm to find the floor where the elevator is expected to be called at each preset time unit based on elevator operation information, and move the elevator to the floor where the elevator is expected to be called based on the result.

[0039] FIG. 2 is a block diagram of an elevator control system (200) according to one embodiment of the present disclosure. Although the elevator control system (200) is illustrated as a single unit in FIG. 2, it will be understood that the components (210, 220, 230, 240, 250) of the elevator control system (200) may be distributed across the edge device (14) and the cloud environment (16), since the elevator control system (200) includes an edge device (14) and a cloud environment (16).

[0040] Referring to FIG. 2, the elevator control system (200) includes a communication unit (210), a data storage unit (220), an analysis unit (230), a data processing unit (240), and an elevator control unit (250).

[0041] The communication unit (210) is configured to perform communication with an external device via a network. In one embodiment, both the edge device (14) and the cloud environment (16) include the communication unit. In one embodiment, the communication unit (210) may be configured to perform communication between at least two components of the data storage unit (220), the analysis unit (230), the data processing unit (240), and the elevator control unit (250). The data storage unit (220) is configured to store elevator operation information. The data storage unit (220) may store raw data received from the elevator management device (12). The data storage unit (220) may store raw data processed from the elevator management device (12) as elevator operation information. The data storage unit (220) may store a prediction algorithm. The data storage unit (220) may store the predicted target floor of the elevator derived using the prediction algorithm. The data storage unit (220) may store the result of whether a call was actually made to the predicted target floor by matching the prediction with the result.

[0042] That is, the data storage unit (220) can store all information related to elevator operation. The data storage unit (220) can be configured to store a matrix such as that illustrated in FIGS. 6 to 8.

[0043] In one embodiment, the analysis unit (230) may generate a prediction algorithm based on elevator operation information. Furthermore, the analysis unit (230) may use the prediction algorithm to derive the predicted target floor of the elevator.

[0044] The data processing unit (240) is configured to process the raw data collected from the elevator management device (12) to derive elevator operation information used in the prediction algorithm. In one embodiment, when the raw data is in hexadecimal format, the data processing unit (240) may analyze the raw data to generate call unit data including, for one call, at least one of the time the call occurred (e.g., day of the week, hour, minute), the floor on which the call occurred, and the target floor. The data processing unit (240) may process a continuous set of data in preset time units (e.g., milliseconds, seconds, minutes, hours, etc.). For example, the data processing unit (240) may process data generated in preset time intervals such as 1 second or 1 minute, and organize the data by assigning an ID by matching the time the call occurred (e.g., day of the week, hour, minute), the floor on which the call occurred, the target floor, the waiting time, etc. for one call. The data organized in this way may be referred to as call unit data. One ID may be assigned to one call unit data. Call unit elevator operation information processed by the data processing unit (240) can be stored in the data storage unit (220).

[0045] In addition, the data processing unit (240) can analyze the elevator operation information stored in the data storage unit (320) and organize call-unit data based on at least one of date, holiday, day of the week, hour, minute, target floor, and floor where the call occurred. The data processing unit (240) can extract call-unit data by date, holiday, and day of the week, extract call-unit data by hour and minute, and extract call-unit data by target floor and floor where the call occurred. The data extracted and organized in this way can be stored in the data storage unit (220).

[0046] The analysis unit (230) can sort the call unit elevator operation information stored in the data storage unit (220) to create a matrix as shown in FIGS. 6 to 8, and use this to derive the expected target floor of the elevator.

[0047] In one embodiment, the analysis unit (230) can retrieve call unit data by day of the week stored in the data storage unit (220) and generate a call frequency matrix (e.g., FIG. 6) in which the horizontal axis (x-axis) represents time and the vertical axis (y-axis) represents the floor with the hall call. The time unit is a preset time and can be set by the administrator. For example, FIG. 6 is one of the day-of-the-week matrices generated at 1-minute intervals for elevators installed in a 4-story building every 4 weeks. The numerator is the number of calls on each floor.

[0048] In one embodiment, N may be the maximum number of hole calls that can occur in a minute. Here, the minute unit may vary depending on the setting, that is, it may vary depending on the method to be analyzed. N for the 1st floor and the top floor may be different from N applied to the floors in between. For example, in FIG. 6, N=6, and 5, which is N-1, is applied to the 1st and 4th floors. The maximum number of hole calls that can occur in a minute may vary depending on the properties of the elevator, such as the door speed and rated speed. For example, as an extreme example, in order for the maximum number of hole calls to occur within a minute, the hole call button is pressed, the door opens and closes, and then no one gets on the car, and the hole call button is pressed again repeatedly. In FIG. 6, assuming that the door opens and closes for 5 seconds each, for a total of 10 seconds, the maximum number of hole calls that can occur in a minute is calculated and set to 6. In one embodiment, the middle layer has a lower maximum frequency by 1, since the maximum and first layers only have a down or up call button. Since there are seven days in a week, there can be seven matrices for each day of the week.

[0049] The analysis unit (230) generates a matrix of continuously occurring weight values ​​based on preset time units (e.g., daily, weekly, monthly). For example, a weight matrix for four-week periods is illustrated in FIG. 7 . The horizontal and vertical axes of the matrix regarding weight values ​​may be identical to those of the call frequency matrix.

[0050] In one embodiment, the weighting may be determined based on the time at which the statistics were aggregated. For example, referring to Figure 7, since the data spans four weeks, if two calls occurred on the third floor at 00:02 during the four weeks, the weighting would be 2 / 4.

[0051] The analysis unit (230) multiplies the call frequency matrix and the weight matrix to generate a score matrix (e.g., FIG. 8).

[0052] The analysis unit (230) may determine the expected target floor of the elevator based on the score matrix. For example, the analysis unit (230) may determine that the floor with the highest score is the expected target floor of the elevator for that time period. If the analysis unit (230) determines that the difference in scores between the floor with the highest score and the floor with the next highest score is less than a preset value, the analysis unit (230) may determine the expected target floor of the elevator to be any floor between the floor with the highest score and the floor with the next highest score.

[0053] The analysis unit (230) may store the expected target floor of the elevator in the data processing unit (240) and / or transmit it to the elevator control unit (250). Alternatively, the analysis unit (230) may transmit the score matrix to the elevator control unit (250), from which the elevator control unit (250) may select the expected target floor.

[0054] FIG. 3 is a block diagram of an elevator control system (300) according to one embodiment of the present disclosure. Although the elevator control system (300) is illustrated as a single unit in FIG. 3, it will be understood that the components (310, 320, 330, 340) of the elevator control system (300) may be distributed across the edge device (14) and the cloud environment (16), since the elevator control system (300) includes an edge device (14) and a cloud environment (16).

[0055] Referring to FIG. 3, the elevator control system (300) may include a processor (310), a memory (320), a database (330), and a communication unit (340). In one embodiment, the processor (310) may be any type of processor or controller for performing functions, such as application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, micro-controllers, microprocessors, or other functions.

[0056] The memory (320) may be configured to store information for the operation of the elevator control system (300). The memory (320) may store a plurality of application programs or applications running in the elevator control system (300), data that can be read by the processor, and commands. For example, the memory (320) may include various storage spaces such as a hard disk drive (HDD), a solid state disk (SSD), a silicon disk drive (SDD), a ROM, a RAM, an EPROM, a flash drive, a hard drive, a cloud using a network, etc. In one embodiment, when the command stored in the memory (320) is executed by the processor (310), the method disclosed herein may be performed. In one embodiment, when the command stored in the memory (320) is executed by the processor (310), the functions of the analysis unit (230), the data processing unit (240), and the elevator control unit (250) illustrated in FIG. 2 may be performed.

[0057] The database (330) may be configured to store instructions executed by the processor (310). The database (330) may include various storage spaces such as a hard disk drive (HDD), a solid state disk (SSD), a silicon disk drive (SDD), a ROM, a RAM, an EPROM, a flash drive, a hard drive, a cloud using a network, etc. Although the memory (320) and the database (330) have been described as separate components, it will be understood that the memory (320) and the database (330) may be viewed as a single component.

[0058] The database (330) may, in one embodiment, be configured to store information regarding elevator operation and the matrices illustrated in FIGS. 5 to 7.

[0059] The communication unit (340) is configured to communicate with an external device via a network. The communication method of the network may use a network built according to GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), HSDPA (High Speed ​​Downlink Packet Access), HSUPA (High Speed ​​Uplink Packet Access), LTE (Long Term Evolution), LTE-A (Long Term Evolution-Advanced), etc.), WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), Wi-Fi (Wireless Fidelity) Direct, DLNA (Digital Living Network Alliance), WiBro (Wireless Broadband), and WiMAX (World Interoperability for Microwave Access), but is not limited thereto and may include all transmission method standards to be developed in the future. In addition, the communication method of the network may include all methods that can send and receive data via wired / wireless.

[0060] An artificial intelligence model can be implemented by the processor (310) executing instructions stored in the memory (320). In the present disclosure, the artificial intelligence model may refer to a model that trains a learning model including an artificial neural network (ANN) through a large amount of learning data, optimizes parameters within the artificial neural network, and participates in the operation of a dialogue system (not shown) using the trained learning model. In one embodiment, the artificial intelligence module (not shown) can be trained through Machine Reading Comprehension (MRC). In one embodiment, the artificial neural network model used in the artificial intelligence module is at least one or a combination of a Convolutional Neural Network (CNN), a Deep Neural Network (DNN), a Recurrent Neural Network (RNN), a Restricted Boltzmann Machine (RBM), a Deep Belief Network (DBN), a Bidirectional Recurrent Deep Neural Network (BRDNN), a Variational Auto Encoder (VAE), or a Deep Q-Network, but is not limited to the examples described above.

[0061] FIG. 4 is a flowchart illustrating a method for storing elevator operation information according to one embodiment of the present disclosure. The method of FIG. 4 may be performed by at least one of the edge device (14), the cloud environment (16) illustrated in FIG. 1, and the systems (200, 300) illustrated in FIG. 2 or FIG. 3, or a combination thereof. However, it will be appreciated that the method of FIG. 4 is not limited to the edge device (14), the cloud environment (16), the systems (200, 300), or a combination thereof, and may be performed by devices or systems of other configurations.

[0062] For convenience of explanation, the following description will exemplarily describe an edge device (14) and a cloud environment (16) performing the method illustrated in FIG. 4.

[0063] Referring to FIG. 4, raw data regarding elevator calls and / or operations are collected and interpreted in S410. In one embodiment, raw data regarding elevator calls and / or operations are collected by an elevator management device (12) and transmitted to an edge device (14). The edge device (14) transmits the received raw data to a cloud environment (16) at preset intervals, and the cloud environment (16) can store the raw data. In one embodiment, the edge device (14) can receive and interpret the accumulated raw data. Alternatively, the cloud environment (16) can interpret the raw data and transmit the result of the interpretation to the edge device (14). When the necessary elevator operation information cannot be directly extracted from the raw data, such as when the raw data includes data in hexadecimal format, interpretation of the raw data is necessary. Therefore, when it is possible to directly extract the necessary elevator operation information from the raw data, interpretation of the raw data can be omitted. For example, the elevator management device (12) can be configured to directly transmit elevator operation information to the edge device (14).

[0064] At S420, elevator operation information is extracted. Elevator operation information may include the request (car request, hall request) generation time (including date, day of the week, hour, and minute), movement direction, waiting time, etc. Elevator operation information may be extracted from interpreted source data. Extraction of elevator operation information may be performed by an edge device (14) or a cloud environment (16).

[0065] In S430, elevator operation information can be processed into call unit data. In one embodiment, the edge device (14) or cloud environment (16) can analyze the elevator operation information to generate call unit data including the time (e.g., day of the week, hour, minute), the floor where the call occurred, and the target floor for one call. The edge device (14) or cloud environment (16) can process data generated in units of preset time intervals and organize the data by assigning an ID by matching the time (e.g., day of the week, hour, minute), the floor where the call occurred, the target floor, the waiting time, etc. for one call. Alternatively, the call unit data can be generated by the elevator management device (12).

[0066] In one embodiment, the edge device (14) or the cloud environment (16) can organize call unit data based on at least one of date, holiday, day of the week, hour, minute, target floor, and floor where the call occurred. The edge device (14) or the cloud environment (16) can extract call unit data by date, holiday, and day of the week, extract call unit data by hour and minute, and extract call unit data by target floor and floor where the call occurred.

[0067] Data processed in S430 is stored in S440. For example, call unit data may be stored in a storage unit of an edge device (14) or a cloud environment (16).

[0068] FIG. 5 is a diagram illustrating an elevator control method (500) according to one embodiment of the present disclosure. The method of FIG. 5 may be performed by at least one of the elevator management device (12), the edge device (14), the cloud environment (16) illustrated in FIG. 1, and the systems (200, 300) illustrated in FIG. 2 or FIG. 3, or a combination thereof. However, it will be understood that the method of FIG. 5 is not limited to the elevator management device (12), the edge device (14), the cloud environment (16), the systems (200, 300), or a combination thereof, and may be performed by devices or systems of other configurations. For example, the method (500) of FIG. 5 may be performed by the elevator control unit (250).

[0069] Referring to FIG. 5, a method (500) for moving an elevator to a predicted floor is initiated. At S510, it is determined whether there is an elevator request. The elevator request may include a car call and a hall call. In response to determining that there is an elevator request at S510, a method for moving the elevator to the predicted floor is initiated again. At S520, it is determined whether the elevator is stopped. In response to determining that there is no elevator request at S510, S520 is performed. In response to determining that the elevator is not stopped at S520, a method for moving the elevator to the predicted floor is initiated again. In response to determining that the elevator is stopped at S510, S530 is performed. In S530, it is determined whether the predicted target floor of the elevator exists. In response to determining that the predicted target floor of the elevator does not exist at S530, a method for moving the elevator to the predicted floor is initiated again. In response to determining that the predicted target floor of the elevator exists at S530, S540 is performed. Move the elevator to the target floor at S540.

[0070] In one embodiment, steps S510 and S520 may be integrated and referred to as a step for determining whether the elevator is in operation. That is, in response to determining that the elevator is already in operation, the method (500) may be performed to not move the elevator to the predicted floor but to follow the existing operation, and in response to determining that the elevator is not in operation, to move the elevator to the predicted floor. The method (500) for moving the elevator to the predicted floor may be repeatedly performed at preset time intervals. For example, the method may be repeatedly performed at preset time intervals, such as 1 minute, 3 minutes, 5 minutes, or 10 minutes, as preset by the elevator manager.

[0071] In one embodiment, a method (502) for calculating an algorithm for predicting an elevator floor may be performed separately from a method (500) for moving an elevator to a predicted floor. The method (502) for calculating the algorithm may be performed based on stored elevator operation information as described above, and thus a detailed description thereof will be omitted. The method (502) for calculating an algorithm for predicting an elevator floor may be repeatedly performed at a preset cycle. This is because the elevator operation information may continuously change. A target floor used in S530 of the method (500) for moving an elevator to a predicted floor may be derived according to the separately performed method (502) for calculating the algorithm. The target floor may be transmitted to an entity performing the method (500) for moving an elevator to a predicted floor. For example, the entity performing the method (500) for moving an elevator to a predicted floor may be any one of an elevator management device (12), an edge device (14), a cloud environment (16), and a system (200, 300). Accordingly, the target floor of S530 of the method (500) for moving the elevator to the predicted floor can be set.

[0072] In one embodiment, a call may be received (504) from a user who wishes to use the elevator, separately from the method (500) for moving the elevator to a predicted floor and / or the method (502) for calculating the algorithm. The call may include a hall call and a car call. The call may be transmitted to an entity performing the method (500) for moving the elevator to a predicted floor. The entity performing the method (500) for moving the elevator to a predicted floor may, in response to receiving the call even while moving the elevator according to S540, move the elevator according to the call, regardless of whether the elevator is operated to the target floor.

[0073] The method according to the present disclosure can be implemented as a processor-readable code on a processor-readable recording medium provided in a server, system, equipment, computer, integrated control device, etc. used by a subject. The processor-readable recording medium includes all types of recording devices that store data that can be read by the processor. Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc., and also includes those implemented in the form of a carrier wave, such as transmission via the Internet. In addition, the processor-readable recording medium can be distributed across network-connected computer systems, so that the processor-readable code can be stored and executed in a distributed manner.

[0074] The devices and methods described above may be implemented using hardware components, software components, and / or a combination of hardware components and software components. For example, the devices and components described in the embodiments may be implemented using one or more general-purpose computers or special-purpose computers, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing instructions and responding to them. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. Furthermore, the processing device may access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing device is sometimes described as being used singly; however, those skilled in the art will appreciate that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, the processing device may include multiple processors, or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are also possible.

[0075] Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing device to perform a desired operation or may, independently or collectively, command the processing device. The software and / or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium or device, or transmitted signal wave for interpretation by the processing device or for providing instructions or data to the processing device. The software may also be distributed over networked computer systems and stored or executed in a distributed manner. The software and data may be stored on one or more computer-readable recording media.

[0076] The described embodiments of the present disclosure can also be practiced in distributed computing environments, where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0077] Although the embodiments described above have been described with limited drawings, those skilled in the art will appreciate that various technical modifications and variations can be applied based on the above. For example, appropriate results can still be achieved even if the described techniques are performed in a different order than described, and / or components of the described systems, structures, devices, circuits, etc. are combined or combined in a different manner than described, or are replaced or substituted with other components or equivalents.

[0078] Therefore, other implementations, other embodiments, and equivalents to the claims also fall within the scope of the claims set forth below.

Claims

1. As an elevator control system, A data processing unit configured to process elevator operation information; A data storage unit configured to store the above elevator operation information, wherein the elevator operation information includes call unit data including the date and time when a call occurred and the floor on which the call occurred for each call unit; An analysis unit configured to predict the target floor of the elevator based on the above elevator operation information; and An elevator control unit configured to operate an elevator to a target floor of the elevator, Elevator control system.

2. In paragraph 1, An elevator control system, wherein the analysis unit is configured to organize the call unit data by day of the week and generate a call count matrix including time on the horizontal axis and the floor where the call occurred on the vertical axis.

3. In paragraph 2, An elevator control system, wherein the analysis unit is configured to generate a weight matrix having the same dimension as the call count matrix based on the time at which the elevator operation information is aggregated, and to generate a score matrix by multiplying the call count matrix and the weight matrix.

4. In paragraph 1, The above elevator control unit Determine whether the above elevator is in operation, An elevator control system configured to operate the elevator to the target floor in response to determining that the elevator is not in operation.

5. In paragraph 4, The above elevator control unit Receive an elevator call from a user, An elevator control system configured to operate the elevator by giving priority to the elevator call, regardless of whether the elevator is operated to the target floor in response to receiving the elevator call.

6. In paragraph 1, An elevator control system, wherein the data storage unit is configured to store the call unit data in units of at least one of day of the week, time, and destination floor.

7. A method for controlling an elevator by an elevator control system, A step of receiving and storing elevator operation information; A step of analyzing the above elevator operation information to generate call unit data including the floor and time at which an elevator call occurred; A step of generating a call count matrix based on the call unit data, the horizontal axis being time and the vertical axis being the floor where the call occurred; A step of predicting the target floor of the elevator based on the call count matrix; and Comprising a step of operating an elevator to the target floor, How to control an elevator.

8. In paragraph 7, The step of predicting the target floor of the elevator based on the above call count matrix is: A step of generating a weight matrix having the same dimension as the call count matrix based on the time at which the elevator operation information is aggregated; A step of generating a score matrix by multiplying the call count matrix and the weight matrix, and An elevator control method comprising a step of predicting a target floor of an elevator based on the above score matrix.

9. In paragraph 7, A step of receiving an elevator call from a user; and An elevator control method further comprising a step of operating the elevator by giving priority to the elevator call, regardless of whether the elevator is operated to the target floor in response to receiving the elevator call.

10. In paragraph 7, The step of generating a call count matrix based on the call unit data above, in which the horizontal axis is time and the vertical axis is the floor where the call occurred, is as follows: An elevator control system comprising a step of storing the call unit data by grouping it into at least one unit of day of the week, time, and destination floor.

Citation Information

Patent Citations

  • Apparatus for setting a dispersion backup story of a group control system for an elevator and a method thereof for setting the number of dispersion backup story zones less than the number of elevators

    KR1019990012986A

  • Management controller of elevators

    KR1020000076382A

  • Controller for elevator

    JP1998036019A

  • Method of controlling multi elevator

    KR100202720B1

  • Group control method of elevator for deciding and service optimum operating car for call of platform through evaluated value calculation for corresponding elevator

    KR100430230B1