Elevator dispatching methods, elevator dispatching devices and electronic equipment
By receiving scheduling requests from the elevator and combining historical elevator weights and operating status information, the target elevator weights are dynamically adjusted, solving the problem of poor performance of existing elevator scheduling methods and achieving more efficient elevator scheduling and improved user satisfaction.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA MOBILE M2M
- Filing Date
- 2022-12-29
- Publication Date
- 2026-05-26
AI Technical Summary
The existing elevator dispatching method has the problem of poor dispatching effect, especially when user demand is concentrated during peak hours, it is difficult to meet the actual elevator usage needs of users.
By receiving scheduling requests from the elevator terminal, and combining historical elevator weights and operating status information, the target elevator weights for each floor are dynamically adjusted to generate optimal scheduling information. Taking into account the elevator's direction of travel, load information, and current user waiting status, the elevator stopping order is optimized.
It enables dynamic adjustment of elevator dispatching information, improves elevator operating efficiency and user experience, meets users' actual elevator usage needs, and enhances dispatching effectiveness.
Smart Images
Figure CN116902712B_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of Internet of Things (IoT) technology, specifically relating to an elevator scheduling method, an elevator scheduling device, and an electronic device. Background Technology
[0002] With the increasing number of high-rise buildings in cities, elevators have become an indispensable part of daily life.
[0003] In existing technologies, two elevator scheduling methods are most common: First Come First Serve (FCFS) and Shortest Seek Time First (SSTF). FCFS is a random service scheduling method. SSTF specifically selects the floor whose request signal in the request signal queue the elevator can reach first as the elevator's service target. However, existing scheduling methods still suffer from poor scheduling efficiency. Summary of the Invention
[0004] The purpose of this application is to provide an elevator scheduling method, elevator scheduling device, and electronic device that can solve the problem of poor scheduling effect of existing elevator scheduling methods.
[0005] In a first aspect, embodiments of this application provide an elevator scheduling method, applied to a server, the method comprising:
[0006] The system receives a scheduling request sent by the elevator terminal. The scheduling request includes historical elevator weights and the elevator terminal's operating status information. The operating status information includes user waiting information for each floor corresponding to the elevator terminal. The historical elevator weights are used to indicate the priority of each floor's stopping order during the last elevator scheduling.
[0007] Based on the operating status information and the historical elevator weights, the target elevator weights for each floor are determined. The target elevator weights are used to indicate the priority of the elevator's stopping order on each floor.
[0008] Based on the target elevator weight, scheduling information corresponding to the scheduling request is generated.
[0009] Optionally, the operating status information may further include first status information corresponding to the elevator end, wherein the first status information includes at least one of the following: elevator running direction, elevator load information, and elevator floor.
[0010] The step of generating scheduling information corresponding to the scheduling request based on the target elevator weight includes:
[0011] The scheduling information is generated based on the target elevator weight and the first state information.
[0012] Optionally, the user waiting information includes the number of people waiting on each floor and the waiting time of users on each floor; the operating status information also includes second status information, which includes the number of people located inside the elevator.
[0013] The step of determining the target elevator weight for each floor based on the operational status information and the historical elevator weights includes:
[0014] Based on the number of people waiting, the second status information, and the historical elevator weights, the current elevator weights for each floor are determined.
[0015] Based on the number of people waiting and the waiting time, determine the waiting weight for each floor;
[0016] The target elevator weight is determined based on the current elevator weight and the waiting weight.
[0017] Optionally, determining the waiting weight for each floor based on the number of people waiting and the waiting time includes:
[0018] Based on the number of people waiting on each floor, a first parameter is determined, which includes the sum of the number of people waiting on each floor.
[0019] Based on the waiting time of each floor, a second parameter is determined, which includes the sum of the waiting times of each floor;
[0020] Based on the first parameter and the number of people waiting on each floor, a first additional weight is determined for each floor;
[0021] Based on the second parameter and the waiting time of each floor, a second additional weight is determined for each floor;
[0022] The waiting weight for each floor is determined based on the first additional weight and the second additional weight.
[0023] Optionally, the second status information further includes a target time difference, which is the time difference between the time when the elevator sends the scheduling request and the time when the elevator is put into use;
[0024] Based on the number of people waiting, the second status information, and the historical elevator weights, the current elevator weights for each floor are determined, including:
[0025] The first sub-weight of each floor is determined based on the number of people inside the elevator and the number of people waiting.
[0026] Based on the first sub-weight, the target time difference, and the historical elevator weight, the current elevator weight of each floor is determined.
[0027] Secondly, embodiments of this application provide an elevator scheduling method applied at an elevator, the method comprising:
[0028] Obtain a scheduling request, which includes historical elevator weights and the elevator's operating status information. The operating status information includes user waiting information for each floor corresponding to the elevator. The historical elevator weights are used to indicate the priority of each floor's stopping order during the last elevator scheduling.
[0029] The scheduling request is sent to the server.
[0030] Thirdly, this application provides an elevator dispatching device applied to a server, the elevator dispatching device comprising:
[0031] The receiving module is used to receive a scheduling request sent by the elevator terminal. The scheduling request includes historical elevator weights and the elevator terminal's operating status information. The operating status information includes user waiting information for each floor corresponding to the elevator terminal. The historical elevator weights are used to indicate the priority of each floor's stopping order during the last elevator scheduling.
[0032] The determination module is used to determine the target elevator weight for each floor based on the operating status information and the historical elevator weight. The target elevator weight is used to indicate the priority of each floor in the stopping order.
[0033] The generation module is used to generate scheduling information corresponding to the scheduling request based on the target elevator weight.
[0034] Fourthly, embodiments of this application provide an elevator dispatching device applied at an elevator end, the elevator dispatching device comprising:
[0035] The acquisition module is used to acquire a scheduling request. The scheduling request includes historical elevator weights and the operating status information of the elevator terminal. The operating status information includes user waiting information for each floor corresponding to the elevator terminal. The historical elevator weights are used to indicate the priority of each floor in the last elevator scheduling.
[0036] The sending module is used to send the scheduling request to the server.
[0037] Fifthly, embodiments of this application provide an electronic device, which includes a processor and a memory. The memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, they implement the steps of the elevator scheduling method as described in the first and second aspects.
[0038] In a sixth aspect, embodiments of this application provide a readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the elevator scheduling method as described in the first and second aspects.
[0039] In this embodiment, the final scheduling information is obtained by comprehensively processing the current operating status of the elevator and the priority of each floor during the last elevator scheduling. This enables dynamic adjustment of the scheduling information, thereby ensuring that the scheduling information can meet the actual needs of users and achieve better scheduling results. Attached Figure Description
[0040] Figure 1 This is one of the flowcharts illustrating the elevator scheduling method provided in the embodiments of this application;
[0041] Figure 2 A second schematic flowchart of the elevator scheduling method provided in this application embodiment;
[0042] Figure 3 This is a flowchart illustrating the elevator dispatching process.
[0043] Figure 4 A flowchart illustrating the process of determining the target elevator weight for each floor based on the operating status information and the historical elevator weight in the elevator scheduling method provided in this application embodiment;
[0044] Figure 5 A schematic diagram of an elevator dispatching device applied to a server, provided in an embodiment of this application;
[0045] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0046] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.
[0047] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0048] The elevator scheduling method provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.
[0049] like Figure 1 As shown in the embodiment of this application, the elevator scheduling method applied to the server includes the following steps:
[0050] Step S1: Receive a scheduling request sent by the elevator terminal. The scheduling request includes historical elevator weights and the elevator terminal's operating status information. The operating status information includes user waiting information for each floor corresponding to the elevator terminal. The historical elevator weights are used to indicate the priority of each floor's stopping order during the last elevator scheduling.
[0051] The elevator dispatching method provided in this application can be applied to elevator systems in residential buildings, office buildings, shopping malls, and other buildings. When a user presses the elevator up or down button on any floor, a request for elevator use will be sent to the elevator terminal. After receiving the user's request, the elevator terminal sends a dispatch request to the server. The dispatch request includes historical elevator weights, which include the sub-weights corresponding to each floor in the elevator system during the last elevator dispatch. The sub-weights are sorted according to their values to determine the priority of dispatching elevators to each floor during the last elevator dispatch.
[0052] The dispatch request also includes the elevator's operational status information obtained at the moment the elevator section receives the user's request for elevator use. The operational status information includes user waiting information on each floor, the number of people in each elevator, the direction of travel of each elevator, and the location of each elevator.
[0053] Step S2: Based on the operating status information and the historical elevator weights, determine the target elevator weights for each floor. The target elevator weights are used to indicate the priority of the elevator's stopping order on each floor.
[0054] After receiving the scheduling request from the elevator terminal, the server processes the operating status information and historical elevator weight information contained in the scheduling request, and generates the target elevator weight corresponding to each floor. The larger the target elevator weight value of a floor, the higher the priority of the floor's stopping order. That is, the elevator is dispatched to the corresponding floor in descending order of the target elevator weight value.
[0055] Optionally, when calculating the target elevator usage weight for each floor during peak hours (7-9 am, 5-7 pm), in addition to obtaining the elevator's operating status at the moment a user submits an elevator usage request, the elevator's operating status information is obtained every minute. This allows for timely scheduling of the operating status information to calculate the target elevator usage weight when a user submits an elevator usage command. During off-peak hours, the elevator's operating status information can be obtained every 5 minutes. The above intervals and information acquisition frequency are adjustable.
[0056] Optionally, for a target elevator system at a specific time each day, such as the typical peak usage time of 8 AM, the target passenger weight for each floor at 8 AM yesterday is used as the historical passenger weight. This is then combined with the elevator's operational status information at 8 AM today to calculate the target passenger weight for each floor at 8 AM today. As the target elevator system operates, the target passenger weight for each floor at 8 AM each day is continuously iterated, and the target passenger weight for each floor at 8 AM each day will increasingly reflect users' actual elevator usage habits.
[0057] Step S3: Generate scheduling information corresponding to the scheduling request based on the target elevator weight.
[0058] The elevator terminal can consist of multiple elevators or a single elevator. After the server generates the target passenger weights for each floor, each elevator is subject to limitations imposed by its actual operating status, such as whether the elevator is overloaded, whether its direction of travel meets the user's needs, and the floor it is located on. Therefore, it is necessary to combine the target passenger weights for each floor, the elevator dispatch priority, and information such as whether the elevator is overloaded and the floor it is located to make a comprehensive judgment to form dispatch information.
[0059] As an optional implementation method, such as Figure 2As shown, after receiving a user's elevator request, the elevator terminal begins data collection to obtain the elevator's operating status information and historical passenger weights. Further, the data is sent to the server, which generates elevator scheduling information based on the data; the specific process is detailed in steps S1 to S3 above. Further, the elevator terminal determines whether it has received the user's request. If not, the process of data collection, data transmission to the server, and elevator scheduling information generation is repeated. If a user has received the request, it determines whether there are other users' elevator requests. If there are no other requests, the elevator scheduling process ends. If there are other requests, the process of data collection, data transmission to the server, elevator scheduling information generation, and determining whether to receive the user's request is repeated.
[0060] In the elevator scheduling method provided in this application embodiment, the final scheduling information is obtained by comprehensively processing the current operating status of the elevator and the priority of each floor when the elevator was last scheduled. This realizes the dynamic adjustment of the scheduling information, thereby ensuring that the scheduling information can meet the actual needs of users and has a better scheduling effect.
[0061] Optionally, the operating status information may further include first status information corresponding to the elevator end, the first status information including at least one of the following: elevator running direction, elevator load information, and the floor where the elevator is located.
[0062] The elevator terminal may include a single elevator or multiple elevators. The elevator operates in both vertical and horizontal directions. The elevator's load-bearing information and maximum load capacity are used to determine whether the elevator is overloaded. The distance between the elevator and each floor is determined by the elevator's current floor level.
[0063] Optionally, step S3, generating scheduling information corresponding to the scheduling request based on the target elevator weight, includes:
[0064] The scheduling information is generated based on the target elevator weight and the first state information.
[0065] like Figure 3As shown, during elevator scheduling, the server generates target passenger weights for each floor, obtains the first state information of all elevators, generates scheduling information based on a custom algorithm, and sends the scheduling information to the corresponding elevators to complete the scheduling. The process of generating scheduling information based on the custom algorithm is as follows: the optimal solution is calculated by comprehensively considering the target passenger weights for each floor, the elevator's direction of travel, its load information, and the floor it is located on. Understandably, under the same conditions, direct elevator access is more efficient than intermediate stops; the fewer stops an elevator makes, the higher its operating efficiency. For example, for the target floor with the highest target passenger weight, based on the user's elevator usage needs on the target floor, the first elevator with the same direction of user needs is found. From the first elevator, the target elevator closest to the target floor is selected, and the target elevator stops at the target floor. After the user enters the target elevator, the target elevator cannot be overloaded.
[0066] The target passenger weight for each floor is combined with information such as elevator direction of travel, elevator load information, and the floor where the elevator is located to generate scheduling information, which can improve the operating efficiency of elevators and thus improve the user experience.
[0067] Optionally, the user waiting information includes the number of people waiting on each floor and the waiting time of users on each floor; the operating status information also includes second status information, which includes the number of people located inside the elevator.
[0068] By capturing image information from cameras on each floor and then using image processing technology, the number of people waiting on each floor can be obtained. The image information also includes time information; based on the current time and the time each user started waiting, the waiting time for each user can be calculated. The sum of the waiting times for all users on a floor is the total waiting time for that floor. Similarly, the number of people inside the elevator can also be obtained using cameras and image processing technology.
[0069] Optionally, such as Figure 4 As shown, step S2, based on the operating status information and the historical elevator weights, determines the target elevator weights for each floor, including:
[0070] Step S21: Based on the number of people waiting, the second status information, and the historical elevator weights, determine the current elevator weights for each floor.
[0071] The current elevator weight of a floor is determined by combining real-time information such as the number of people waiting on each floor and the number of people inside the elevator with the floor's historical elevator weight, which indicates the elevator stopping priority of the floor in the last scheduling process. The number of people waiting is compared with the number of people inside the elevator; the more people waiting, the higher the floor's elevator weight needs to be to meet the needs of more users.
[0072] Step S22: Determine the waiting weight for each floor based on the number of people waiting and the waiting time.
[0073] If there are many people waiting on a particular floor, the elevator weighting of that floor needs to be increased to meet user demand. Conversely, if the waiting time on the same floor is long, users will become dissatisfied, so the elevator weighting of that floor also needs to be increased. Therefore, both the number of people waiting and the waiting time need to be included in the process of determining the target elevator weighting to ensure that the target elevator weighting can meet the elevator needs of different users to the greatest extent possible.
[0074] Step S23: Determine the target elevator weight based on the current elevator weight and the waiting weight.
[0075] The target elevator weight is the sum of the current elevator weight and the waiting weight. The target elevator weight is determined based on the number of people waiting, the number of people inside the elevator, historical elevator weights, and waiting time, further ensuring that the target elevator weight can meet users' elevator needs to the greatest extent.
[0076] Optionally, step S22, based on the number of people waiting and the waiting time, determines the waiting weight for each floor, including:
[0077] Based on the number of people waiting on each floor, a first parameter is determined, which includes the sum of the number of people waiting on each floor.
[0078] Get the number of people waiting on each floor at the current moment, and sum the number of people waiting on each floor to get the first parameter.
[0079] A second parameter is determined based on the waiting time on each floor, and the second parameter includes the sum of the waiting times on each floor.
[0080] The waiting time for each floor includes the sum of the waiting times for all users on that floor. The second parameter is obtained by summing the waiting times for each floor.
[0081] Based on the first parameter and the number of people waiting on each floor, a first additional weight is determined for each floor.
[0082] First additional weight:
[0083]
[0084] Where i represents the floor level, P i The number of people waiting on the i-th floor is represented by h, where h represents the highest level of the floor.
[0085] Based on the second parameter and the waiting time for each floor, a second additional weight is determined for each floor.
[0086] Second additional weight:
[0087]
[0088] Where i represents the floor level, T i The waiting time is represented by h, where h represents the highest floor level.
[0089] The waiting weight for each floor is determined based on the first additional weight and the second additional weight.
[0090] The waiting weight:
[0091]
[0092] The number of people waiting and their waiting time on each floor are compared with the total number of people waiting and their waiting time. The ratio is calculated, and the sum of the two ratios is used as the waiting weight. The waiting weight fully considers the impact of users' waiting behavior on their urgency of using the elevator. The current elevator usage weight derived from the waiting weight will better meet users' elevator usage needs.
[0093] Optionally, the second status information further includes a target time difference, which is the time difference between the time when the elevator sends the scheduling request and the time when the elevator is put into use;
[0094] The target time difference can be expressed in seconds, minutes, hours, days, or years, but in the elevator scheduling method provided in this application embodiment, days are generally used as the unit, and rounded up.
[0095] Optionally, step S21, based on the number of waiting passengers, the second status information, and the historical elevator weights, determines the current elevator weight for each floor, including:
[0096] Based on the number of people inside the elevator and the number of people waiting, determine the first sub-weight for each floor.
[0097] First sub-weight:
[0098] W i =P i / F i
[0099] Where i represents the floor level, W i P represents the first sub-weight. i F represents the number of people waiting on the i-th floor. i This indicates the number of people located inside the elevator.
[0100] Based on the first sub-weight, the target time difference, and the historical elevator weight, the current elevator weight of each floor is determined.
[0101] The current elevator weight:
[0102] W n =(W n-1 ×(n-1)+W i ) / n
[0103] Where n represents the target time difference, i.e., the time difference between the moment the elevator sends the scheduling request and the moment the elevator is put into use, and the unit of n is days. W i W represents the first sub-weight. n This represents the current elevator usage weight. The first sub-weight is the sum of all weights over (n-1) days, plus the weight at the current moment. This sum is then divided by n days to obtain the average, which is the current elevator usage weight. As the current elevator usage weight is continuously updated, it will increasingly reflect the user's actual elevator usage habits.
[0104] This application provides an elevator scheduling method applied to elevator terminals, including:
[0105] Obtain a scheduling request, which includes historical elevator weights and the elevator's operating status information. The operating status information includes user waiting information for each floor corresponding to the elevator. The historical elevator weights are used to indicate the priority of each floor's stopping order during the last elevator scheduling.
[0106] The scheduling request is sent to the server.
[0107] The elevator scheduling method described above, applied to elevator terminals, can be used in elevator systems of residential buildings, office buildings, shopping malls, and other buildings. When a user presses the elevator's up or down button on any floor, the elevator terminal receives the user's elevator usage request, collects the scheduling request information, and sends it to the server. This allows the server to quickly generate an elevator scheduling strategy to meet the customer's elevator usage needs. It should be noted that the principle of the elevator scheduling method applied to elevator terminals is the same as that of the elevator scheduling method applied to the server, and will not be repeated here.
[0108] The elevator scheduling method applied to the server provided in this application embodiment can be executed by an elevator scheduling device. This application embodiment takes the elevator scheduling device executing the elevator scheduling method applied to the server as an example, and combines it with the appendix... Figure 5 This application describes the elevator dispatching device terminal 500 provided. The elevator dispatching device includes:
[0109] The receiving module 501 is used to receive a scheduling request sent by the elevator terminal. The scheduling request includes historical elevator weights and the operating status information of the elevator terminal. The operating status information includes user waiting information for each floor corresponding to the elevator terminal. The historical elevator weights are used to indicate the priority of each floor in the last elevator scheduling.
[0110] The determining module 502 is used to determine the target elevator weight for each floor based on the operating status information and the historical elevator weight, wherein the target elevator weight is used to indicate the priority of each floor in the stopping order;
[0111] The generation module 503 is used to generate scheduling information corresponding to the scheduling request based on the target elevator weight. Optionally, the operating status information further includes first status information corresponding to the elevator, the first status information including at least one of the following: elevator running direction, elevator load information, and the floor where the elevator is located;
[0112] The generation module is also used to generate the scheduling information based on the target elevator weight and the first state information.
[0113] Optionally, the user waiting information includes the number of people waiting on each floor and the waiting time of users on each floor; the operating status information also includes second status information, which includes the number of people located inside the elevator.
[0114] The determining module is also used for:
[0115] Based on the number of people waiting, the second status information, and the historical elevator weights, the current elevator weights for each floor are determined.
[0116] Based on the number of people waiting and the waiting time, determine the waiting weight for each floor;
[0117] The target elevator weight is determined based on the current elevator weight and the waiting weight.
[0118] Optionally, the determining module is further configured to:
[0119] Based on the number of people waiting on each floor, a first parameter is determined, which includes the sum of the number of people waiting on each floor.
[0120] Based on the waiting time of each floor, a second parameter is determined, which includes the sum of the waiting times of each floor;
[0121] Based on the first parameter and the number of people waiting on each floor, a first additional weight is determined for each floor;
[0122] Based on the second parameter and the waiting time of each floor, a second additional weight is determined for each floor;
[0123] The waiting weight for each floor is determined based on the first additional weight and the second additional weight.
[0124] Optionally, the second status information further includes a target time difference, which is the time difference between the time when the elevator sends the scheduling request and the time when the elevator is put into use;
[0125] The determining module is also used for:
[0126] The first sub-weight of each floor is determined based on the number of people inside the elevator and the number of people waiting.
[0127] Based on the first sub-weight, the target time difference, and the historical elevator weight, the current elevator weight of each floor is determined.
[0128] After receiving a scheduling request from the elevator terminal, the elevator scheduling device applied to the server can process the historical elevator weights and the elevator terminal's operating status information in the scheduling request to generate scheduling information corresponding to the scheduling request.
[0129] It should be noted that the elevator scheduling device provided in this application embodiment can realize all the technical processes of the elevator scheduling method applied to the server and achieve the same technical effect. To avoid repetition, it will not be described again here.
[0130] This application embodiment also provides an elevator scheduling device applied to an elevator terminal. The elevator scheduling device applied to an elevator terminal is capable of executing the above-described elevator scheduling method applied to an elevator terminal. The elevator scheduling device includes:
[0131] The acquisition module is used to acquire a scheduling request. The scheduling request includes historical elevator weights and the operating status information of the elevator terminal. The operating status information includes user waiting information for each floor corresponding to the elevator terminal. The historical elevator weights are used to indicate the priority of each floor in the last elevator scheduling.
[0132] The sending module is used to send the scheduling request to the server.
[0133] After receiving a user's elevator usage request, the elevator dispatching device applied to the elevator terminal obtains the dispatching request through the acquisition module. The dispatching request includes historical elevator weights and the current elevator terminal operating status information. Then, the dispatching module sends the dispatching request to the server so that the server generates elevator dispatching information corresponding to the dispatching request to meet the user's elevator usage needs.
[0134] The device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. Non-mobile electronic devices can also be servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service machines, etc. This application embodiment does not specifically limit the scope of the device.
[0135] Optionally, such as Figure 6 As shown, this application embodiment also provides an electronic device 600, including a processor 601 and a memory 602. The memory 602 stores a program or instructions that can run on the processor 601. When the program or instructions are executed by the processor 601, they implement the various steps of the elevator scheduling method embodiment described above and can achieve the same technical effect. To avoid repetition, they will not be described again here.
[0136] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.
[0137] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the elevator scheduling method embodiments described above and achieve the same technical effect. To avoid repetition, they will not be described again here.
[0138] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.
[0139] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
[0140] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0141] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. An elevator scheduling method, applied to a server, characterized in that, The method includes: The system receives a scheduling request sent by the elevator terminal. The scheduling request includes historical elevator weights and the elevator terminal's operating status information. The operating status information includes user waiting information for each floor corresponding to the elevator terminal. The historical elevator weights are used to indicate the priority of each floor's stopping order during the last elevator scheduling. Based on the operating status information and the historical elevator weights, the target elevator weights for each floor are determined. The target elevator weights are used to indicate the priority of the elevator's stopping order on each floor. Based on the target elevator weight, generate scheduling information corresponding to the scheduling request; The user waiting information includes the number of people waiting on each floor and the waiting time for users on each floor; the operating status information also includes second status information, which includes the number of people located inside the elevator. The step of determining the target elevator weight for each floor based on the operational status information and the historical elevator weights includes: Based on the number of people waiting, the second status information, and the historical elevator weights, the current elevator weights for each floor are determined. Based on the number of people waiting and the waiting time, determine the waiting weight for each floor; The target elevator weight is determined based on the current elevator weight and the waiting weight; The second status information also includes a target time difference, which is the time difference between the time when the elevator sends the scheduling request and the time when the elevator is put into use; Based on the number of people waiting, the second status information, and the historical elevator weights, the current elevator weights for each floor are determined, including: Based on the number of people inside the elevator and the number of people waiting, a first sub-weight is determined for each floor. The method for determining the first sub-weight is as follows: ,in, Indicates the floor level. Indicates the first sub-weight. Indicates the first The number of people waiting on each floor. This indicates the number of people located inside the elevator. Based on the first sub-weight, the target time difference, and the historical elevator weight, the current elevator weight for each floor is determined. The current elevator weight is determined as follows: ,in, This refers to the target time difference, which is the time difference between the moment the elevator sends the scheduling request and the moment the elevator is put into use. The unit is days. Indicates the first sub-weight. This indicates the current elevator weight. This represents the historical elevator weight.
2. The elevator scheduling method as described in claim 1, characterized in that, The operating status information also includes first status information corresponding to the elevator end, and the first status information includes at least one of the following: elevator running direction, elevator load information, and elevator floor; The step of generating scheduling information corresponding to the scheduling request based on the target elevator weight includes: The scheduling information is generated based on the target elevator weight and the first state information.
3. The elevator scheduling method as described in claim 1, characterized in that, The determination of the waiting weight for each floor based on the number of people waiting and the waiting time includes: Based on the number of people waiting on each floor, a first parameter is determined, which includes the sum of the number of people waiting on each floor. Based on the waiting time of each floor, a second parameter is determined, which includes the sum of the waiting times of each floor; Based on the first parameter and the number of people waiting on each floor, a first additional weight is determined for each floor; Based on the second parameter and the waiting time of each floor, a second additional weight is determined for each floor; The waiting weight for each floor is determined based on the first additional weight and the second additional weight.
4. An elevator dispatching device, applied at the server end, characterized in that, The elevator dispatching device includes: The receiving module is used to receive a scheduling request sent by the elevator terminal. The scheduling request includes historical elevator weights and the elevator terminal's operating status information. The operating status information includes user waiting information for each floor corresponding to the elevator terminal. The historical elevator weights are used to indicate the priority of each floor's stopping order during the last elevator scheduling. The determination module is used to determine the target elevator weight for each floor based on the operating status information and the historical elevator weight. The target elevator weight is used to indicate the priority of each floor in the stopping order. The generation module is used to generate scheduling information corresponding to the scheduling request based on the target elevator weight; The user waiting information includes the number of people waiting on each floor and the waiting time for users on each floor; the operating status information also includes second status information, which includes the number of people located inside the elevator. The determining module is also used for: Based on the number of people waiting, the second status information, and the historical elevator weights, the current elevator weights for each floor are determined. Based on the number of people waiting and the waiting time, determine the waiting weight for each floor; The target elevator weight is determined based on the current elevator weight and the waiting weight; The second status information also includes a target time difference, which is the time difference between the time when the elevator sends the scheduling request and the time when the elevator is put into use; The determining module is also used for: Based on the number of people inside the elevator and the number of people waiting, a first sub-weight is determined for each floor. The method for determining the first sub-weight is as follows: ,in, Indicates the floor level. Indicates the first sub-weight. Indicates the first The number of people waiting on each floor. This indicates the number of people located inside the elevator. Based on the first sub-weight, the target time difference, and the historical elevator weight, the current elevator weight for each floor is determined. The current elevator weight is determined as follows: ,in, This refers to the target time difference, which is the time difference between the moment the elevator sends the scheduling request and the moment the elevator is put into use. The unit is days. Indicates the first sub-weight. This indicates the current elevator weight. This represents the historical elevator weight.
5. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the steps of the elevator scheduling method as described in any one of claims 1 to 3.
6. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the elevator scheduling method as described in any one of claims 1 to 3.