Elevator emergency dispatching method and system based on fault priority

Abstract

The invention relates to the technical field of elevator dispatching, and discloses an elevator emergency dispatching method and system based on fault priorities, and the method comprises the steps: analyzing fault feature parameters of fault report data in an elevator monitoring terminal based on a fault classification rule of historical fault data in the elevator monitoring terminal; mapping the fault feature parameters to a fault priority mapping table to obtain a basic priority level; dynamic adjustment is conducted in combination with real-time elevator running state data and environment context data, and a final fault priority level is obtained; matching strategies corresponding to the elevator available resources, the maintenance team state and the building operation requirements in a preset fault processing strategy library; sorting the elements according to final priorities, and integrating allocation strategies to generate a self-adaptive emergency scheduling strategy; deconstructing and coding the self-adaptive emergency scheduling strategy to obtain an emergency scheduling instruction; the elevator emergency dispatching efficiency can be improved.

Description

Technical Field

[0001] This invention relates to the field of elevator dispatching technology, and in particular to an elevator emergency dispatching method and system based on fault priority. Background Technology

[0002] Existing elevator emergency dispatching systems mostly adopt a fixed fault priority division mode, without dynamically adapting to real-time elevator operating status, fault evolution characteristics, and environmental context data. This results in high-risk faults not receiving priority handling, while low-risk events excessively consume rescue resources, leading to resource allocation imbalances and insufficient targeted responses.

[0003] Traditional dispatching mechanisms suffer from significant information silos, with a lack of effective data interaction between subsystems. Furthermore, dispatching strategies are formulated based on only a single dimension, failing to comprehensively consider key factors such as available elevator resources, maintenance team distribution, and building accessibility. This results in unreasonable response path selection and poor system coordination, severely impacting the timeliness and efficiency of fault rescue. Therefore, improving the efficiency of elevator emergency dispatching has become an urgent problem to be solved. Summary of the Invention

[0004] This invention provides an elevator emergency dispatching method and system based on fault priority to solve the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides an elevator emergency dispatching method based on fault priority, comprising: S1. Based on the fault classification rules of historical fault data in the elevator monitoring terminal, the fault characteristic parameters of the fault report data in the elevator monitoring terminal are parsed out. S2. Map the fault feature parameters to the fault priority mapping table in the historical fault data to obtain the basic priority level of the fault feature parameters; S3. Based on the real-time elevator operation status data and environmental context data of the elevator monitoring terminal, dynamically adjust the basic priority level to obtain the final fault priority level of the fault characteristic parameters. S4. Match the fault handling strategy in the preset fault handling strategy library with the elevator available resources, maintenance team status and building operation requirements of the elevator monitoring terminal. S5. Based on the final fault priority level, prioritize the elevator available resources, maintenance team status and building operation needs of the elevator monitoring terminal, and integrate and allocate the fault handling strategy according to the priority ranking result to generate the adaptive emergency dispatch strategy of the elevator monitoring terminal. S6. Deconstruct and encode the adaptive emergency dispatch strategy to obtain the emergency dispatch instructions of the elevator monitoring terminal.

[0006] In a preferred embodiment, the step of parsing fault characteristic parameters from fault report data in the elevator monitoring terminal based on fault classification rules of historical fault data in the elevator monitoring terminal includes: Abnormal or missing data in the fault report data of the elevator monitoring terminal are removed to obtain the standardized fault data of the elevator monitoring terminal. Based on the historical fault data of the elevator monitoring terminal, establish fault classification rules for the elevator monitoring terminal; Match the potential fault types between the fault classification rules and the standardized fault data; Based on the potential fault type, extract the fault feature parameters from the standardized fault data.

[0007] In a preferred embodiment, mapping the fault characteristic parameters to a fault priority mapping table in the historical fault data to obtain the basic priority level of the fault characteristic parameters includes: Cluster analysis is performed on the historical fault types and their corresponding historical processing urgency in the historical fault data to obtain the priority level of the historical fault data. The historical fault types are correlated with the priority levels, and a fault priority mapping table for the elevator monitoring terminal is constructed based on the correlation matching results. The fault type identifier in the fault characteristic parameters is input into the fault priority mapping table to obtain the basic priority level of the fault characteristic parameters.

[0008] In a preferred embodiment, the step of dynamically adjusting the basic priority level based on the real-time elevator operating status data and environmental context data from the elevator monitoring terminal to obtain the final fault priority level of the fault characteristic parameters includes: Based on the key parameters of elevator operation in the real-time elevator operation status data of the elevator monitoring terminal, the abnormal modes of the elevator monitoring terminal are identified to assess the urgency of the elevator operation status represented by the elevator monitoring terminal. The environmental characteristic parameters of the environmental context data in the elevator monitoring terminal are analyzed to determine the degree of influence of environmental factors in the environmental context data. Based on the urgency and impact, the basic priority level is dynamically adjusted to obtain the final fault priority level of the fault characteristic parameters.

[0009] In a preferred embodiment, the step of dynamically adjusting the basic priority level based on the urgency and the impact to obtain the final fault priority level of the fault characteristic parameters includes: By integrating the urgency level and the impact level, a fault association combination set for the elevator monitoring terminal is obtained; In the historical fault handling records of the elevator monitoring terminal, evaluate the correlation between the fault association combination set and the aggravation of severity; Based on the correlation assessment results, the relative importance of the urgency and the impact in the priority adjustment is determined; Based on the relative importance, the urgency and the impact are weighted and fused to obtain the priority feature parameters of the basic priority level; Select the priority adjustment direction corresponding to the priority feature parameter from the hierarchical association rules of the historical fault handling records; Based on the priority adjustment direction, the basic priority level is adjusted to obtain the final fault priority level of the fault characteristic parameters.

[0010] In a preferred embodiment, the priority feature parameter is calculated using the following formula: ; In the formula, This represents the priority feature parameter. Indicates the degree of urgency. Indicates the degree of influence. This represents the pre-defined synergistic effect coefficient of the fault escalation correlation based on the fault association combination set. This indicates the preset urgency threshold for the fault escalation correlation based on the fault association combination set. Represents the natural constant.

[0011] In a preferred embodiment, the step of matching fault handling strategies from a preset fault handling strategy library with the elevator monitoring terminal's available elevator resources, maintenance team status, and building operation needs includes: The matching degree between the available elevator carrying capacity and the location of the faulty elevator in the elevator monitoring terminal is evaluated to obtain the resource availability evaluation result of the elevator monitoring terminal. The current location, skill and qualification matching, and task load of the maintenance personnel in the elevator monitoring terminal are checked to comprehensively analyze the team response capability of the maintenance team in the elevator monitoring terminal. The elevator monitoring terminal identifies key areas for ensuring access, special time periods for operation, and service priorities for user groups within the building's operational needs, thus obtaining a classification result of the elevator monitoring terminal's demand importance. The resource availability assessment results, the team response capability analysis results, and the requirement importance classification results are mapped to a preset fault handling strategy library to obtain the fault handling strategy for the elevator monitoring terminal.

[0012] In a preferred embodiment, the step of prioritizing the elevator available resources, maintenance team status, and building operation needs of the elevator monitoring terminal according to the final fault priority level, and then integrating and allocating the fault handling strategy according to the priority ranking result to generate an adaptive emergency dispatch strategy for the elevator monitoring terminal, includes: The available elevator resources, the maintenance team status, and the building operation requirements are integrated into a fault element set for the elevator monitoring terminal. By establishing an association mapping between the final fault priority level and the fault element set, the priority association relationship of the elevator monitoring terminal is obtained. Based on the priority association, the fault elements are prioritized and logically conflicting items in the priority ranking result are removed to obtain the final priority ranking result of the elevator monitoring terminal. Based on the final priority ranking result, the fault handling strategy is integrated to obtain the initial emergency dispatch strategy of the elevator monitoring terminal; The coordination and connection relationships in the initial emergency dispatch strategy are sorted out, and the conflict points in the execution of the initial emergency dispatch strategy are eliminated to obtain the adaptive emergency dispatch strategy of the elevator monitoring terminal.

[0013] In a preferred embodiment, the step of deconstructing and encoding the adaptive emergency dispatch strategy to obtain the emergency dispatch instructions of the elevator monitoring terminal includes: Eliminate the ambiguous statements of the adaptive emergency dispatch strategy to obtain the standardized emergency dispatch strategy of the elevator monitoring terminal; According to the preset instruction encoding rules, the standardized emergency dispatch strategy is converted into a structured encoded fragment that conforms to the system data transmission format; The structured coded segments are logically correlated and then integrated and encapsulated according to the scheduling execution order of the elevator monitoring terminal to obtain the emergency dispatch instructions of the elevator monitoring terminal.

[0014] To address the aforementioned problems, the present invention also provides an elevator emergency dispatching system based on fault priority, the system comprising: The fault feature extraction module is used to parse the fault feature parameters of the fault report data in the elevator monitoring terminal based on the fault classification rules of historical fault data in the elevator monitoring terminal. The basic priority evaluation module is used to map the fault characteristic parameters to the fault priority mapping table in the historical fault data to obtain the basic priority level of the fault characteristic parameters. The dynamic priority adjustment module is used to dynamically adjust the basic priority level based on the real-time elevator operation status data and environmental context data of the elevator monitoring terminal, so as to obtain the final fault priority level of the fault characteristic parameters. The fault handling strategy matching module is used to match fault handling strategies in a preset fault handling strategy library that correspond to the elevator available resources, maintenance team status and building operation requirements of the elevator monitoring terminal. An adaptive scheduling strategy generation module is used to prioritize the elevator available resources, maintenance team status and building operation needs of the elevator monitoring terminal according to the final fault priority level, and to integrate and allocate the fault handling strategy according to the priority ranking result to generate an adaptive emergency scheduling strategy for the elevator monitoring terminal. The dispatch instruction encoding module is used to deconstruct and encode the adaptive emergency dispatch strategy to obtain the emergency dispatch instructions of the elevator monitoring terminal.

[0015] Compared with the prior art, the present invention has the following beneficial effects: 1. This invention uses fault classification rules based on historical fault data from elevator monitoring terminals to accurately analyze fault feature parameters in fault report data, then maps them to a fault priority mapping table to obtain a basic priority level. At the same time, it dynamically adjusts the priority by combining real-time elevator operating status data and environmental context data, so that the final fault priority level can accurately match the actual urgency and impact of the fault, ensuring that high-urgency and high-impact faults are handled first, and improving the accuracy and timeliness of fault response.

[0016] 2. This invention matches elevator available resources, maintenance team status, and building operation needs with strategies from a preset fault handling strategy library. It sorts the above elements according to the final fault priority and integrates the allocation strategies to generate an adaptive emergency dispatch strategy. Furthermore, it deconstructs and encodes the strategy to form clear emergency dispatch instructions, effectively optimizing resource allocation and team collaboration processes, ensuring the synergy and execution efficiency of emergency dispatch, and further improving the overall effect of elevator emergency handling. Attached Figure Description

[0017] Figure 1 A flowchart illustrating an elevator emergency dispatching method based on fault priority, provided in an embodiment of the present invention; Figure 2 A functional block diagram of an elevator emergency dispatch system based on fault priority is provided in an embodiment of the present invention; The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0018] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0019] This application provides an elevator emergency dispatching method based on fault priority. The executing entity of this fault priority-based elevator emergency dispatching method includes, but is not limited to, at least one of the following electronic devices that can be configured to execute the method provided in this application embodiment: a server, a terminal, etc. In other words, the fault priority-based elevator emergency dispatching method can be executed by software or hardware installed on a terminal device or a server device. The server includes, but is not limited to, a single server, a server cluster, a cloud server, or a cloud server cluster. The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0020] Reference Figure 1 The diagram shown is a flowchart illustrating an elevator emergency dispatching method based on fault priority according to an embodiment of the present invention. In this embodiment, the elevator emergency dispatching method based on fault priority includes: S1. Based on the fault classification rules of historical fault data in the elevator monitoring terminal, the fault characteristic parameters of the fault report data in the elevator monitoring terminal are parsed out. In this embodiment of the invention, the step of parsing fault characteristic parameters from fault report data in the elevator monitoring terminal based on fault classification rules of historical fault data in the elevator monitoring terminal includes: Abnormal or missing data in the fault report data of the elevator monitoring terminal are removed to obtain the standardized fault data of the elevator monitoring terminal. Based on the historical fault data of the elevator monitoring terminal, establish fault classification rules for the elevator monitoring terminal; Match the potential fault types between the fault classification rules and the standardized fault data; Based on the potential fault type, extract the fault feature parameters from the standardized fault data.

[0021] Check the key fields of the fault report data in the elevator monitoring terminal, including the fault occurrence time, fault location, fault phenomenon description, and fault-related component number. If any key field of a fault report data is empty, the field content does not match the actual elevator component information, or the field value is outside the reasonable range, then the data is determined to be abnormal missing data. Remove all records determined to be abnormal missing data from the fault report dataset. The remaining fault report data is the standardized fault data of the elevator monitoring terminal.

[0022] Historical fault data from the elevator monitoring terminal over the past three years were collected. Each historical fault data point was analyzed to extract core information such as fault phenomenon, location, scope of impact, and fault repair components. The extracted core information was then categorized based on similarity. For example, "car door cannot close automatically," "landing door is stuck and cannot open," and "door motor failure causes door to not move" were categorized as door system faults. For each categorized fault type, a unified identification standard was summarized. For example, the identification standard for door system faults is "the fault location involves the car door or landing door, the fault phenomenon is abnormal door movement, and the scope of impact includes elevator start / stop or personnel entry / exit." The identification standards for all fault categories were compiled into a standardized document, which serves as the fault classification rules for the elevator monitoring terminal.

[0023] Select a fault record from the standardized fault data of the elevator monitoring terminal, extract the fault phenomenon and location information from the record, and check whether the information of the record meets all the identification criteria of a certain fault category by comparing it with the identification criteria of each fault category in the fault classification rules. If the record's "fault location is the car door, fault phenomenon is that the door repeatedly opens and closes and cannot be locked" is completely consistent with the identification criteria of the door system fault, then the potential fault type corresponding to the fault record is determined to be a door system fault. Complete the matching of all fault records in the standardized fault data with the fault classification rules in the same way to obtain the potential fault type corresponding to each standardized fault data.

[0024] For each identified potential fault type, the characteristic parameters to be extracted for that type of fault are specified. For example, for door system faults, the door closing delay time, door lock device on / off status, and door operator operating current value need to be extracted; for traction system faults, the traction motor speed, traction rope tension, and motor temperature need to be extracted. From the standardized fault data of the elevator monitoring terminal, the fault record corresponding to the potential fault type is located, and the specific data corresponding to the preset characteristic parameters in the record is read. For example, in the door system fault record, "door closing delay time is 8 seconds", "door lock device on / off status is off", and "door operator operating current value is 1.5A" are recorded. These specific data are organized into an ordered information set according to the characteristic parameter category. This information set is the fault characteristic parameter in the standardized fault data.

[0025] The beneficial effects are that by accurately removing abnormal and missing data, the integrity and accuracy of standardized fault data are ensured; the fault classification rules established based on historical fault data are in line with actual application scenarios and have clear classification logic; the potential fault types determined by matching classification rules can truly reflect the essence of the fault; the fault feature parameters extracted based on potential fault types are highly targeted and the data is effective; the four-step operation forms a complete data processing link, providing high-quality data support for subsequent fault priority determination and emergency dispatch strategy formulation, and effectively improving the reliability and accuracy of early data processing for elevator emergency dispatch.

[0026] S2. Map the fault feature parameters to the fault priority mapping table in the historical fault data to obtain the basic priority level of the fault feature parameters; In this embodiment of the invention, the step of mapping the fault feature parameters to a fault priority mapping table in the historical fault data to obtain the basic priority level of the fault feature parameters includes: Cluster analysis is performed on the historical fault types and their corresponding historical processing urgency in the historical fault data to obtain the priority level of the historical fault data. The historical fault types are correlated with the priority levels, and a fault priority mapping table for the elevator monitoring terminal is constructed based on the correlation matching results. The fault type identifier in the fault characteristic parameters is input into the fault priority mapping table to obtain the basic priority level of the fault characteristic parameters.

[0027] Historical fault data from elevator monitoring terminals is collected, and the historical fault type and corresponding historical urgency of each data point are separated. The historical urgency is determined based on the longest allowable time for the maintenance team to arrive at the scene after a fault is reported. For example, a maximum allowable time of no more than 1 hour is considered high urgency, 1 to 4 hours is medium urgency, and more than 4 hours is low urgency. Fault data with the same historical fault type and the same historical urgency range are then grouped together, forming an independent category. For each category, the impact of faults within that group on elevator operation safety and the risk of personnel entrapment is confirmed. For example, groups containing "personnel entrapment faults" are clearly designated as high priority, while groups containing "damage to internal decorative parts only, not affecting functionality" are clearly designated as low priority. Finally, the priority level of the historical fault data is obtained.

[0028] Extract all historical fault types one by one, and map each historical fault type to the priority level determined in the first step. For example, the historical fault type "the landing door cannot be opened, preventing people from entering or exiting the car" corresponds to a high priority level, while the historical fault type "the indicator light inside the elevator is flashing but does not affect the lifting and lowering operation" corresponds to a low priority level. Organize these correspondences into a table in a uniform format. The first column of the table should be filled with the specific name of the historical fault type, and the second column should be filled with the priority level corresponding to the historical fault type. Ensure that each historical fault type has one and only one corresponding priority level in the table, without duplication or omission. This table is the fault priority mapping table of the elevator monitoring terminal.

[0029] Extract a clear fault type identifier from the fault feature parameters. This fault type identifier must completely match the name of the historical fault type. For example, the fault type identifier recorded in the fault feature parameters, "Fault Type Identifier - Abnormal Tension of Traction System Rope", corresponds to "Abnormal Tension of Traction System Rope Fault" in the historical fault type. Compare the fault type identifier row by row in the "Historical Fault Type" column of the fault priority mapping table. After finding a historical fault type that is completely consistent with the identifier, read the "Priority Level" of the row where the historical fault type is located. This priority level is the basic priority level of the fault feature parameters.

[0030] The beneficial effects are that by clustering analysis of historical fault types and their urgency, the priority level can be accurately matched with the actual urgency and safety impact of the fault. The constructed fault priority mapping table clarifies the fixed correspondence between fault type and priority. The process of obtaining the basic priority level by querying the mapping table through the fault type identifier is efficient and unambiguous. The entire process ensures the rationality and accuracy of the basic priority level determination, and provides a reliable initial basis for subsequent dynamic adjustment of priority based on real-time data, effectively improving the efficiency and quality of elevator fault priority determination.

[0031] S3. Based on the real-time elevator operation status data and environmental context data of the elevator monitoring terminal, dynamically adjust the basic priority level to obtain the final fault priority level of the fault characteristic parameters. In this embodiment of the invention, the step of dynamically adjusting the basic priority level based on the real-time elevator operating status data and environmental context data of the elevator monitoring terminal to obtain the final fault priority level of the fault characteristic parameters includes: Based on the key parameters of elevator operation in the real-time elevator operation status data of the elevator monitoring terminal, the abnormal modes of the elevator monitoring terminal are identified to assess the urgency of the elevator operation status represented by the elevator monitoring terminal. The environmental characteristic parameters of the environmental context data in the elevator monitoring terminal are analyzed to determine the degree of influence of environmental factors in the environmental context data. Based on the urgency and impact, the basic priority level is dynamically adjusted to obtain the final fault priority level of the fault characteristic parameters.

[0032] The step of dynamically adjusting the basic priority level based on the urgency and impact to obtain the final fault priority level of the fault characteristic parameters includes: By integrating the urgency level and the impact level, a fault association combination set for the elevator monitoring terminal is obtained; In the historical fault handling records of the elevator monitoring terminal, evaluate the correlation between the fault association combination set and the aggravation of severity; Based on the correlation assessment results, the relative importance of the urgency and the impact in the priority adjustment is determined; Based on the relative importance, the urgency and the impact are weighted and fused to obtain the priority feature parameters of the basic priority level; Select the priority adjustment direction corresponding to the priority feature parameter from the hierarchical association rules of the historical fault handling records; Based on the priority adjustment direction, the basic priority level is adjusted to obtain the final fault priority level of the fault characteristic parameters.

[0033] The calculation formula for the priority feature parameter is as follows: ; In the formula, This represents the priority feature parameter. Indicates the degree of urgency. Indicates the degree of influence. This represents the pre-defined synergistic effect coefficient of the fault escalation correlation based on the fault association combination set. This indicates the preset urgency threshold for the fault escalation correlation based on the fault association combination set. Represents the natural constant.

[0034] From the real-time elevator operation status data of the elevator monitoring terminal, key elevator operation parameters are extracted, including the elevator's real-time operating speed, car leveling accuracy, door lock closure signal stability, and traction motor operating temperature. Specifically, the operating speed must be checked to ensure it is within ±5% of the equipment's rated speed; the leveling accuracy must be checked to ensure it is controlled within ±3mm; the door lock closure signal must be checked to ensure it experiences fewer than two disconnections within one minute; and the traction motor operating temperature must be checked to ensure it is below 120℃. If the operating speed exceeds the rated range for 10 seconds, or the leveling accuracy deviation exceeds 5mm, or the door lock signal experiences more than three disconnections within one minute, or the motor temperature exceeds 130℃, it is identified as an abnormal mode. Based on the degree of threat posed by the abnormal mode to the safe operation of the elevator, the urgency level is divided into three levels: high, medium, and low, each corresponding to a fixed value: 3 for high, 2 for medium, and 1 for low. This value represents the urgency level, which is the urgency level in the formula.

[0035] From the environmental context data of the elevator monitoring terminal, environmental characteristic parameters are analyzed, including real-time pedestrian flow statistics through floor access control card swipe data, whether the current time period is the morning peak (7:30-9:00) or evening peak (17:30-19:00), whether there are large-scale meetings, exams, or other concentrated pedestrian activities scheduled in the building, and whether the malfunctioning elevator is located on a key access floor such as the 1st floor or the top floor. Based on these parameters, the degree of impact is determined. If the pedestrian flow is more than three times the daily average and is during peak hours, the malfunctioning elevator is on the 1st floor, and there is a large meeting in the building, the degree of impact is high. If the pedestrian flow is one time the daily average and is during off-peak hours, the malfunctioning elevator is on a middle, non-critical floor, and there are no large-scale events, the degree of impact is low. The degree of impact is medium if it falls between the two. The degree of impact is further divided into three levels: high, medium, and low, each corresponding to a fixed value: high corresponds to 3, medium to 2, and low to 1. This value is the degree of impact, which is the degree of impact in the formula.

[0036] The urgency level results obtained from the assessment are matched one-to-one with the determined impact level results to form a structured set containing all possible combinations such as "urgency-high, impact-high", "urgency-high, impact-medium", "urgency-high, impact-low", and "urgency-medium, impact-high". This set is the fault association combination set of the elevator monitoring terminal. For this fault association combination set, the fault escalation cases corresponding to each combination in the historical fault handling records of the elevator monitoring terminal are reviewed to determine the critical value of urgency level within each combination. When the urgency level reaches this value, the probability of fault escalation increases significantly. This critical value is the formula based on fault association. The formula sets a threshold for the urgency of the correlation between the combination set and the fault escalation. It also evaluates the correlation of each combination with the severity of the fault in historical fault handling records. Combinations with strong correlation are assigned a higher synergy coefficient, combinations with moderate correlation are assigned a medium value, and combinations with weak correlation are assigned a lower value. For example, strong correlation corresponds to 0.8, moderate correlation to 0.5, and weak correlation to 0.2. This assigned value is the synergy coefficient assigned to the fault escalation correlation based on the fault correlation combination set in the formula. The natural constant in the formula is a fixed constant in mathematics, with a fixed value of 2.71828, which is directly used in the calculation.

[0037] Retrieve the elevator monitoring terminal's historical fault handling records for the past 5 years. From these records, select historical fault cases that are completely consistent with each combination in the fault association set. Statistically analyze the number of times the fault severity, such as the spread from a single elevator fault to multiple elevator faults, or the increase in severity from no one trapped to someone trapped, is amplified in the historical cases corresponding to each combination. Calculate the proportion of these amplified instances to the total number of faults in that combination. If the proportion exceeds 80%, the combination is considered to have a strong correlation with the amplification of severity; 50%-80% is considered medium; and below 50% is considered weak. Record the correlation determination results for each combination, which is the correlation assessment result of the fault association combination set with the amplification of severity.

[0038] In the correlation assessment results, the severity aggravation ratios corresponding to "urgency" and "impact" within each fault association combination are compared. If the ratio corresponding to "urgency" is more than 20% higher than that of "impact," then the relative importance of urgency in priority adjustment is determined to be higher than that of impact, and the weight of urgency is set at 60% and that of impact at 40%. If the ratio corresponding to "impact" is more than 20% higher than that of "urgency," then the weight of impact is set at 60% and that of urgency at 40%. If the difference between the two ratios is less than 20%, then the weights of both are 50%, thus clarifying the weight allocation and representing the relative importance of urgency and impact in priority adjustment.

[0039] The priority characteristic parameters are obtained by synthesizing the calculation logic of the formula. The formula is implemented through two parts. The first part combines the urgency and the impact. Based on the urgency, the logarithmic operation is used to amplify the superposition effect of the impact on the urgency, reflecting the basic correlation effect between the two. The second part introduces the synergy coefficient and the urgency threshold. First, the product of the urgency and the impact is calculated. Then, the strength of the product is adjusted by exponential operation according to the difference between the actual urgency and the threshold. Finally, the synergy coefficient is used to control the overall weight of this adjustment. The results of the two parts are added together, taking into account the urgency, the impact, the synergy effect between the two, and the role of the urgency threshold, to obtain a quantitative parameter that can comprehensively reflect the fault priority characteristics. At the same time, according to the determined relative importance weight, the urgency value is multiplied by its weight, and the impact value is multiplied by its weight. The result is the priority characteristic parameter of the basic priority level. For example, if the urgency is high 3 with a weight of 60% and the impact is high 3 with a weight of 40%, then 3×0.6+3×0.4=3 is calculated. The result 3 is the priority characteristic parameter.

[0040] The hierarchical association rules in the historical fault handling records of the elevator monitoring terminal are analyzed. The rules are presented in the form of "priority feature parameter value range - priority adjustment direction", specifically "parameter ≥ 2.8 - adjustment direction is to increase by one level", "2.2 ≤ parameter < 2.8 - adjustment direction is to remain unchanged", and "parameter < 2.2 - adjustment direction is to decrease by one level". The current priority feature parameter value is compared with the value range in the rule to find the value range that matches perfectly. The adjustment direction corresponding to this range is read, and this direction is the priority adjustment direction corresponding to the priority feature parameter.

[0041] The initial levels of the basic priority level are clearly defined as high, medium, and low. If the priority adjustment direction is to increase by one level, the basic priority level is adjusted from low to medium and from medium to high. If the adjustment direction is to keep it unchanged, the initial level of the basic priority level remains unchanged. If the adjustment direction is to decrease by one level, the basic priority level is adjusted from high to medium and from medium to low. The level obtained after adjustment is the final fault priority level of the fault characteristic parameters.

[0042] The beneficial effects are that by combining real-time elevator operating status and environmental context data step by step, a complete dynamic adjustment link is formed, from abnormal pattern identification, formula parameter determination, formula calculation of priority feature parameters, to adjustment direction screening and final level determination. This ensures that the final fault priority level can comprehensively and accurately reflect the actual emergency situation and environmental impact of the fault, avoids priority deviation caused by single-dimensional judgment, and provides a scientific and reliable priority basis for subsequent fault handling strategy matching and resource allocation, effectively improving the rationality and effectiveness of priority determination in elevator emergency dispatch.

[0043] S4. Match the fault handling strategy in the preset fault handling strategy library with the elevator available resources, maintenance team status and building operation requirements of the elevator monitoring terminal. In this embodiment of the invention, the step of matching the fault handling strategy corresponding to the elevator available resources, maintenance team status, and building operation requirements of the elevator monitoring terminal in a preset fault handling strategy library includes: The matching degree between the available elevator carrying capacity and the location of the faulty elevator in the elevator monitoring terminal is evaluated to obtain the resource availability evaluation result of the elevator monitoring terminal. The current location, skill and qualification matching, and task load of the maintenance personnel in the elevator monitoring terminal are checked to comprehensively analyze the team response capability of the maintenance team in the elevator monitoring terminal. The elevator monitoring terminal identifies key areas for ensuring access, special time periods for operation, and service priorities for user groups within the building's operational needs, thus obtaining a classification result of the elevator monitoring terminal's demand importance. The resource availability assessment results, the team response capability analysis results, and the requirement importance classification results are mapped to a preset fault handling strategy library to obtain the fault handling strategy for the elevator monitoring terminal.

[0044] Extract specific information about available elevator resources from the elevator monitoring terminal, including the rated load, current operating status, and floor coverage of available elevators. Simultaneously determine the specific floor where the faulty elevator is located and the daily passenger flow on that floor. If the available elevator's floor coverage includes the floor where the faulty elevator is located, it is currently idle, and its rated load can meet the daily passenger flow requirements of that floor, then the matching degree between the available elevator's carrying capacity and the faulty elevator's location is considered high. If the available elevator can cover the floor where the faulty elevator is located but currently needs to complete its existing transport tasks, or its rated load can only meet 80% of the daily passenger flow on that floor, then the matching degree is considered medium. If the available elevator cannot cover the floor where the faulty elevator is located, or requires waiting more than 10 minutes before becoming available, or its rated load is less than 60% of the daily passenger flow on that floor, then the matching degree is considered low. Based on the high, medium, and low matching degree levels, obtain the resource availability assessment result of the elevator monitoring terminal.

[0045] The elevator monitoring terminal's positioning system obtains the specific floor where maintenance personnel are currently located. The difference between this floor and the floor where the malfunctioning elevator is located is used as the distance determination criterion: a difference of 1-5 floors indicates a short distance, 6-10 floors indicates a medium distance, and more than 10 floors indicates a long distance. The maintenance personnel's skill qualification files are reviewed to verify if they hold a maintenance qualification certificate corresponding to the type of elevator malfunction. Holding a certificate indicates a high skill qualification match, while not holding one indicates a low match. The maintenance dispatch records are used to confirm the number of malfunction tasks currently being handled by the maintenance personnel: 0 tasks indicate a low load, 1 task indicates a medium load, and 2 or more tasks indicate a high load. If the distance is short, the skill qualification match is high, and the load is low, the team's response capability is high. If the distance is medium, the skill qualification match is high, and the load is medium, or if the distance is short, the skill qualification match is high, and the load is medium, the team's response capability is medium. If the distance is long, the skill qualification match is low, or the load is high, the team's response capability is low. Based on the high, medium, and low response capability levels, the team response capability analysis results of the maintenance team in the elevator monitoring terminal are obtained.

[0046] The functional zoning of buildings in elevator monitoring terminals is analyzed. Areas with high daily foot traffic and high requirements for efficient passage, such as hospital emergency room floors, main entrance connecting floors of shopping malls, and high-rise office areas of office buildings, are classified as critical areas with high passage guarantee needs. Areas with moderate foot traffic, such as middle floors of ordinary residential buildings and mid-level office areas of office buildings, are classified as ordinary areas with medium passage guarantee needs. Areas with very low foot traffic, such as unused floors and equipment rooms, are classified as non-critical areas with low passage guarantee needs. The morning peak hours (7:30-9:00), evening peak hours (17:30-19:00), and peak hospital visit times are classified as periods of particularly high demand, including 10:00 AM. -12:00 and 14:00-16:00 are designated as special medium-demand periods, and 23:00-6:00 is designated as a special low-demand period. Elderly people, patients, and pregnant women within the building are classified as high-priority users, ordinary office workers and shoppers as medium-priority users, and temporary visitors as low-priority users. Considering the needs for ensuring access to key areas, operational requirements during special periods, and service priorities for user groups, if all three are high, the demand importance is high; if two are medium, or one high and two medium, the demand importance is medium; if all three are low, or two low and one medium, the demand importance is low. Based on the high, medium, and low levels of demand importance, the demand importance classification results for the elevator monitoring terminal are obtained.

[0047] The pre-defined fault handling strategy library stores corresponding fault handling strategies according to the combination relationship of "resource availability assessment results - team response capability analysis results - demand importance classification results". Each combination corresponds to a unique and clear strategy. For example, the combination of "high resource availability - high team response capability - high demand importance" corresponds to the strategy of "immediately dispatching a matching available elevator to the floor where the faulty elevator is located, temporarily replacing the faulty elevator to take on the transportation task, and at the same time dispatching the nearest maintenance team with matching skills and qualifications and no task load to arrive at the faulty floor within 5 minutes to carry out maintenance work". The combination of "medium resource availability - medium team response capability - medium demand importance" corresponds to the strategy of "dispatching an available elevator that is expected to be available in 5 minutes, and dispatching it to the floor where the faulty elevator is located after it becomes available, and at the same time notifying a maintenance team with one task load and matching skills and qualifications to arrive at the faulty floor within 10 minutes after completing the existing task". The resource availability assessment results, team response capability analysis results, and demand importance classification results obtained above are combined into a specific combination. The entry that completely matches the combination is searched in the fault handling strategy library, and the strategy content corresponding to the entry is retrieved to obtain the corresponding fault handling strategy.

[0048] The beneficial effects are that by accurately assessing the matching degree of available elevator resources, the response capability of the maintenance team, and the importance of building operation needs in a step-by-step manner, it ensures that the fault handling strategies matched from the preset fault handling strategy library are highly consistent with the actual resource situation, team capabilities, and operational needs, avoiding resource mismatch or strategy-demand disconnect, improving the scientific nature and pertinence of fault handling strategy formulation, laying a reliable foundation for subsequent integration and allocation strategies based on the final fault priority, and effectively ensuring the efficiency and rationality of fault handling during elevator emergency dispatch.

[0049] S5. Based on the final fault priority level, prioritize the elevator available resources, maintenance team status and building operation needs of the elevator monitoring terminal, and integrate and allocate the fault handling strategy according to the priority ranking result to generate the adaptive emergency dispatch strategy of the elevator monitoring terminal. In this embodiment of the invention, the step of prioritizing the elevator available resources, maintenance team status, and building operation needs of the elevator monitoring terminal according to the final fault priority level, and integrating and allocating the fault handling strategy according to the priority ranking result to generate an adaptive emergency dispatch strategy for the elevator monitoring terminal, includes: The available elevator resources, the maintenance team status, and the building operation requirements are integrated into a fault element set for the elevator monitoring terminal. By establishing an association mapping between the final fault priority level and the fault element set, the priority association relationship of the elevator monitoring terminal is obtained. Based on the priority association, the fault elements are prioritized and logically conflicting items in the priority ranking result are removed to obtain the final priority ranking result of the elevator monitoring terminal. Based on the final priority ranking result, the fault handling strategy is integrated to obtain the initial emergency dispatch strategy of the elevator monitoring terminal; The coordination and connection relationships in the initial emergency dispatch strategy are sorted out, and the conflict points in the execution of the initial emergency dispatch strategy are eliminated to obtain the adaptive emergency dispatch strategy of the elevator monitoring terminal.

[0050] Extract specific information about available elevator resources, including the number of available elevators, rated load, current operating status, and covered floor range; specific information about the maintenance team status, including the number of maintenance personnel, their current location, skill and qualification types, and current workload; and specific information about building operation needs, including the location of key areas, duration of special periods, and distribution of high-priority users. Organize this information in the order of "available elevator resources - maintenance team status - building operation needs" to form a set containing all information and with a clear structure. This set is the fault element set of the elevator monitoring terminal.

[0051] The specific levels of the final fault priority are clearly defined. For high priority levels, association rules are established with the fault element set. This means prioritizing the use of available elevator resources that are idle, have high rated load capacity, and can cover the faulty floor; prioritizing the allocation of maintenance teams that are close to the faulty floor, have matching skills and qualifications, and have no workload; and prioritizing the building operation needs of high-priority users in critical areas and special time periods. For medium priority levels, association rules are established. This means prioritizing the use of available elevator resources that are in operation but expected to be idle within 5 minutes and can cover the faulty floor; and allocating maintenance teams that are moderately close to the faulty floor, have matching skills and qualifications, and have one workload; and meeting the building operation needs of medium-priority users in ordinary areas and non-special time periods. For low priority levels, association rules are established. This means prioritizing the use of available elevator resources that are expected to be idle within 10 minutes and can cover the faulty floor; and allocating maintenance teams that are far from the faulty floor, have matching skills and qualifications, and have two workloads; and meeting the building operation needs of low-priority users in non-critical areas and low-demand time periods. The overall set of these association rules constitutes the priority association relationship of the elevator monitoring terminal.

[0052] Based on the rules corresponding to different final fault priority levels in the priority association relationship, the elements in the fault element set are sorted. If the final fault priority level is high, the available elevator resources are sorted in the order of "idle > idle within 5 minutes > idle within 10 minutes", the maintenance team status is sorted in the order of "close distance and no load > close distance and 1 load > medium distance and no load", and the building operation needs are sorted in the order of "critical area > ordinary area > non-critical area". After sorting, the sorting results are checked for logical conflicts, such as whether two elevators that are both in the "idle" state are requested to be called at the same time, but only one elevator is actually idle. If such conflicts exist, the conflicting sorting items are removed, and the sorting content that conforms to the actual situation is retained to obtain the final priority sorting result of the elevator monitoring terminal.

[0053] Based on the final priority ranking result, the corresponding fault handling strategy is extracted. For example, if the final priority ranking result is "Available elevator resources - Idle elevators, Maintenance team status - Nearby unloaded teams, Building operation needs - Critical areas", then the fault handling strategy is extracted as "Dispatch an idle elevator to the faulty floor to undertake the transportation task, dispatch a nearby unloaded maintenance team to the faulty floor within 5 minutes, and prioritize the passage of personnel in critical areas". These strategies are integrated in the execution order of "Elevator dispatch - Maintenance dispatch - Operation support" to ensure that there are no obvious contradictions between the strategies in time and space, forming a complete strategy document. This document is the initial emergency dispatch strategy of the elevator monitoring terminal.

[0054] The coordination and connection relationships of each link in the initial emergency dispatch strategy are sorted out. For example, the estimated arrival time of the elevator to the faulty floor and the estimated arrival time of the maintenance team are clarified to ensure that the elevator has completed temporary transport preparation when the maintenance team arrives, avoiding time misalignment. At the same time, conflict points in the strategy execution process are checked. For example, if the initial strategy requires the maintenance team to arrive within 5 minutes, but the team needs to cross 15 floors and all elevators are currently busy, it is identified as a conflict point. The conflict is resolved by adjusting to dispatch another maintenance team that is closer. After sorting out the coordination and connection and eliminating conflict points, the resulting strategy is the adaptive emergency dispatch strategy of the elevator monitoring terminal.

[0055] The beneficial effects are that by integrating fault elements, accurately establishing priority associations, scientifically sorting and eliminating conflicts, rationally integrating strategies and eliminating execution conflicts, the generated adaptive emergency dispatch strategy can be highly adapted to the final fault priority level, actual resource status and operational needs. This not only ensures the logic and feasibility of strategy execution, but also realizes the dynamic adaptation of elevator emergency dispatch, effectively improving the rationality and execution efficiency of elevator emergency dispatch strategy, and providing reliable support for the rapid handling of elevator faults.

[0056] S6. Deconstruct and encode the adaptive emergency dispatch strategy to obtain the emergency dispatch instructions of the elevator monitoring terminal.

[0057] In this embodiment of the invention, the step of deconstructing and encoding the adaptive emergency dispatch strategy to obtain the emergency dispatch instructions of the elevator monitoring terminal includes: Eliminate the ambiguous statements of the adaptive emergency dispatch strategy to obtain the standardized emergency dispatch strategy of the elevator monitoring terminal; According to the preset instruction encoding rules, the standardized emergency dispatch strategy is converted into a structured encoded fragment that conforms to the system data transmission format; The structured coded segments are logically correlated and then integrated and encapsulated according to the scheduling execution order of the elevator monitoring terminal to obtain the emergency dispatch instructions of the elevator monitoring terminal.

[0058] The adaptive emergency dispatch strategy was reviewed sentence by sentence to identify ambiguous statements such as "arrive at the faulty floor as soon as possible," "call nearby available elevators," and "appropriately increase the frequency of service" without clear specific standards. "Arrive at the faulty floor as soon as possible" was corrected to "arrive at the faulty floor within 5 minutes of the dispatch command," clarifying the time limit; "call nearby available elevators" was corrected to "call available elevators within 3 floors of the faulty elevator that are in an idle state," clarifying the spatial range and elevator status; and "appropriately increase the frequency of service" was corrected to "adjust the frequency of service to once every 5 minutes," clarifying the specific frequency standard. This ensured that all statements in the strategy had quantifiable and executable clear standards, with no ambiguity. The resulting strategy is the standardized emergency dispatch strategy for the elevator monitoring terminal.

[0059] The pre-defined instruction coding rules clearly stipulate that elevator dispatch instructions begin with "E", maintenance dispatch instructions begin with "M", and operation support instructions begin with "O". Each instruction is followed by the execution time, target floor, and core execution content, separated by commas. For each specific instruction in the standardized emergency dispatch strategy, such as "dispatch a maintenance team to the 12th floor to handle traction system failure within 5 minutes of the dispatch instruction", it is converted into "M,5,12, traction system failure maintenance" according to the rules; such as "call an available elevator within 3 floors of the faulty elevator that is idle to the 9th floor to undertake the transportation task", it is converted into "E,3,9, idle elevator transportation". All standardized instructions are converted according to this rule, and each resulting coded segment is a structured coded segment that conforms to the system data transmission format.

[0060] All structured coded segments are extracted one by one. First, the temporal logical correlation is checked. For example, if there are two segments, "E,2,9, Idle elevator operation" and "M,3,9, Door system fault repair", it is confirmed that the elevator can reach the 9th floor within 2 minutes and the repair team can reach the 9th floor within 3 minutes, with no time conflict. Next, the location logical correlation is checked to confirm that the target floor in all segments is consistent with the floor where the faulty elevator is located or the floor in the key area, with no location mismatch. Finally, the correlation of execution content is checked to confirm that the content of elevator operation, repair processing, and operation support all match the fault type, with no content contradiction. The verified structured coded segments are arranged in the dispatch execution order of "Elevator dispatch instruction → Repair dispatch instruction → Operation support instruction". An instruction start identifier "DISP-" is added to the beginning of the arranged coded string, and an instruction end identifier "-END" is added to the end to form a complete instruction text, which is the emergency dispatch instruction of the elevator monitoring terminal.

[0061] The beneficial effects are that by eliminating ambiguous expressions, the clarity and executability of standardized emergency dispatch strategies are ensured; by encoding according to preset rules, the strategies are transformed into structured fragments that the system can recognize; and by using logical verification and sequential integration, the rationality and completeness of the instructions are ensured. The resulting emergency dispatch instructions are accurate, standardized, and directly executable, effectively avoiding dispatch delays caused by ambiguous instructions or logical conflicts, and improving the efficiency of issuing and executing elevator emergency dispatch instructions.

[0062] like Figure 2 The diagram shown is a functional block diagram of an elevator emergency dispatch system based on fault priority provided in an embodiment of the present invention.

[0063] The elevator emergency dispatching system 100 based on fault priority described in this invention can be installed in an electronic device. Depending on the functions implemented, the elevator emergency dispatching system 100 based on fault priority may include a fault feature extraction module 101, a basic priority evaluation module 102, a dynamic priority adjustment module 103, a fault handling strategy matching module 104, an adaptive dispatching strategy generation module 105, and a dispatching instruction encoding module 106. The modules described in this invention can also be referred to as units, which are a series of computer program segments that can be executed by the processor of an electronic device and can perform a fixed function, and are stored in the memory of the electronic device.

[0064] In this embodiment, the functions of each module / unit are as follows: The fault feature extraction module 101 is used to parse the fault feature parameters of the fault report data in the elevator monitoring terminal based on the fault classification rules of the historical fault data in the elevator monitoring terminal. The basic priority evaluation module 102 is used to map the fault feature parameters to the fault priority mapping table in the historical fault data to obtain the basic priority level of the fault feature parameters. The dynamic priority adjustment module 103 is used to dynamically adjust the basic priority level based on the real-time elevator operation status data and environmental context data of the elevator monitoring terminal, so as to obtain the final fault priority level of the fault characteristic parameters. The fault handling strategy matching module 104 is used to match fault handling strategies in a preset fault handling strategy library that correspond to the elevator available resources, maintenance team status and building operation requirements of the elevator monitoring terminal. The adaptive scheduling strategy generation module 105 is used to prioritize the elevator available resources, maintenance team status and building operation needs of the elevator monitoring terminal according to the final fault priority level, and to integrate and allocate the fault handling strategy according to the priority ranking result to generate the adaptive emergency scheduling strategy of the elevator monitoring terminal. The scheduling instruction encoding module 106 is used to deconstruct and encode the adaptive emergency scheduling strategy to obtain the emergency scheduling instructions of the elevator monitoring terminal.

[0065] In the several embodiments provided by this invention, it should be understood that the disclosed methods and systems can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.

[0066] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0067] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in the form of hardware plus software functional modules.

[0068] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0069] This application embodiment can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0070] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. An elevator emergency dispatching method based on fault priority, characterized in that, The method includes: S1. Based on the fault classification rules of historical fault data in the elevator monitoring terminal, the fault characteristic parameters of the fault report data in the elevator monitoring terminal are parsed out. S2. Map the fault feature parameters to the fault priority mapping table in the historical fault data to obtain the basic priority level of the fault feature parameters; S3. Based on the real-time elevator operation status data and environmental context data of the elevator monitoring terminal, dynamically adjust the basic priority level to obtain the final fault priority level of the fault characteristic parameters. S4. Match the fault handling strategy in the preset fault handling strategy library with the elevator available resources, maintenance team status and building operation requirements of the elevator monitoring terminal. S5. Based on the final fault priority level, prioritize the elevator available resources, maintenance team status and building operation needs of the elevator monitoring terminal, and integrate and allocate the fault handling strategy according to the priority ranking result to generate the adaptive emergency dispatch strategy of the elevator monitoring terminal. S6. Deconstruct and encode the adaptive emergency dispatch strategy to obtain the emergency dispatch instructions of the elevator monitoring terminal.

2. The elevator emergency dispatching method based on fault priority as described in claim 1, characterized in that, The fault classification rules based on historical fault data in the elevator monitoring terminal are used to parse fault characteristic parameters from fault report data in the elevator monitoring terminal, including: Abnormal or missing data in the fault report data of the elevator monitoring terminal are removed to obtain the standardized fault data of the elevator monitoring terminal. Based on the historical fault data of the elevator monitoring terminal, establish fault classification rules for the elevator monitoring terminal; Match the potential fault types between the fault classification rules and the standardized fault data; Based on the potential fault type, extract the fault feature parameters from the standardized fault data.

3. The elevator emergency dispatching method based on fault priority as described in claim 1, characterized in that, The step of mapping the fault feature parameters to a fault priority mapping table in the historical fault data to obtain the basic priority level of the fault feature parameters includes: Cluster analysis is performed on the historical fault types and their corresponding historical processing urgency in the historical fault data to obtain the priority level of the historical fault data. The historical fault types are correlated with the priority levels, and a fault priority mapping table for the elevator monitoring terminal is constructed based on the correlation matching results. The fault type identifier in the fault characteristic parameters is input into the fault priority mapping table to obtain the basic priority level of the fault characteristic parameters.

4. The elevator emergency dispatching method based on fault priority as described in claim 1, characterized in that, The final fault priority level of the fault characteristic parameters is obtained by dynamically adjusting the basic priority level based on the real-time elevator operation status data and environmental context data of the elevator monitoring terminal, including: Based on the key parameters of elevator operation in the real-time elevator operation status data of the elevator monitoring terminal, the abnormal modes of the elevator monitoring terminal are identified to assess the urgency of the elevator operation status represented by the elevator monitoring terminal. The environmental characteristic parameters of the environmental context data in the elevator monitoring terminal are analyzed to determine the degree of influence of environmental factors in the environmental context data. Based on the urgency and impact, the basic priority level is dynamically adjusted to obtain the final fault priority level of the fault characteristic parameters.

5. The elevator emergency dispatching method based on fault priority as described in claim 4, characterized in that, The step of dynamically adjusting the basic priority level based on the urgency and impact to obtain the final fault priority level of the fault characteristic parameters includes: By integrating the urgency level and the impact level, a fault association combination set for the elevator monitoring terminal is obtained; In the historical fault handling records of the elevator monitoring terminal, evaluate the correlation between the fault association combination set and the aggravation of severity; Based on the correlation assessment results, the relative importance of the urgency and the impact in the priority adjustment is determined; Based on the relative importance, the urgency and the impact are weighted and fused to obtain the priority feature parameters of the basic priority level; Select the priority adjustment direction corresponding to the priority feature parameter from the hierarchical association rules of the historical fault handling records; Based on the priority adjustment direction, the basic priority level is adjusted to obtain the final fault priority level of the fault characteristic parameters.

6. The elevator emergency dispatching method based on fault priority as described in claim 5, characterized in that, The calculation formula for the priority feature parameter is as follows: ； In the formula, This represents the priority feature parameter. Indicates the degree of urgency. Indicates the degree of influence. This represents the pre-defined synergistic effect coefficient of the fault escalation correlation based on the fault association combination set. This indicates the preset urgency threshold for the fault escalation correlation based on the fault association combination set. Represents the natural constant.

7. The elevator emergency dispatching method based on fault priority as described in claim 1, characterized in that, The step of matching fault handling strategies from a preset fault handling strategy library with the elevator monitoring terminal's available elevator resources, maintenance team status, and building operation needs includes: The matching degree between the available elevator carrying capacity and the location of the faulty elevator in the elevator monitoring terminal is evaluated to obtain the resource availability evaluation result of the elevator monitoring terminal. The current location, skill and qualification matching, and task load of the maintenance personnel in the elevator monitoring terminal are checked to comprehensively analyze the team response capability of the maintenance team in the elevator monitoring terminal. The elevator monitoring terminal identifies key areas for ensuring access, special time periods for operation, and service priorities for user groups within the building's operational needs, thus obtaining a classification result of the elevator monitoring terminal's demand importance. The resource availability assessment results, the team response capability analysis results, and the requirement importance classification results are mapped to a preset fault handling strategy library to obtain the fault handling strategy for the elevator monitoring terminal.

8. The elevator emergency dispatching method based on fault priority as described in claim 1, characterized in that, The process involves prioritizing the elevator's available resources, maintenance team status, and building operation needs based on the final fault priority level, and then integrating and coordinating the fault handling strategy according to the priority ranking results to generate an adaptive emergency dispatch strategy for the elevator monitoring terminal, including: The available elevator resources, the maintenance team status, and the building operation requirements are integrated into a fault element set for the elevator monitoring terminal. By establishing an association mapping between the final fault priority level and the fault element set, the priority association relationship of the elevator monitoring terminal is obtained. Based on the priority association, the fault elements are prioritized and logically conflicting items in the priority ranking result are removed to obtain the final priority ranking result of the elevator monitoring terminal. Based on the final priority ranking result, the fault handling strategy is integrated to obtain the initial emergency dispatch strategy of the elevator monitoring terminal; The coordination and connection relationships in the initial emergency dispatch strategy are sorted out, and the conflict points in the execution of the initial emergency dispatch strategy are eliminated to obtain the adaptive emergency dispatch strategy of the elevator monitoring terminal.

9. The elevator emergency dispatching method based on fault priority as described in claim 1, characterized in that, The step of deconstructing and encoding the adaptive emergency dispatch strategy to obtain the emergency dispatch instructions of the elevator monitoring terminal includes: Eliminate the ambiguous statements of the adaptive emergency dispatch strategy to obtain the standardized emergency dispatch strategy of the elevator monitoring terminal; According to the preset instruction encoding rules, the standardized emergency dispatch strategy is converted into a structured encoded fragment that conforms to the system data transmission format; The structured coded segments are logically correlated and then integrated and encapsulated according to the scheduling execution order of the elevator monitoring terminal to obtain the emergency dispatch instructions of the elevator monitoring terminal.

10. An elevator emergency dispatching system based on fault priority, used to implement the elevator emergency dispatching method based on fault priority as described in claim 1, the system comprising: The fault feature extraction module is used to parse the fault feature parameters of the fault report data in the elevator monitoring terminal based on the fault classification rules of historical fault data in the elevator monitoring terminal. The basic priority evaluation module is used to map the fault characteristic parameters to the fault priority mapping table in the historical fault data to obtain the basic priority level of the fault characteristic parameters. The dynamic priority adjustment module is used to dynamically adjust the basic priority level based on the real-time elevator operation status data and environmental context data of the elevator monitoring terminal, so as to obtain the final fault priority level of the fault characteristic parameters. The fault handling strategy matching module is used to match fault handling strategies in a preset fault handling strategy library that correspond to the elevator available resources, maintenance team status and building operation requirements of the elevator monitoring terminal. An adaptive scheduling strategy generation module is used to prioritize the elevator available resources, maintenance team status and building operation needs of the elevator monitoring terminal according to the final fault priority level, and to integrate and allocate the fault handling strategy according to the priority ranking result to generate an adaptive emergency scheduling strategy for the elevator monitoring terminal. The dispatch instruction encoding module is used to deconstruct and encode the adaptive emergency dispatch strategy to obtain the emergency dispatch instructions of the elevator monitoring terminal.

Images