Priority ranking algorithm and system for urban rail transit vehicle fault handling schemes

Abstract

The invention discloses a priority ordering algorithm and system for urban rail transit vehicle fault disposal schemes, relates to the technical field of environmental urban rails, and aims to automatically recommend fault disposal schemes according to fault information, provide decision support for a driver, reduce safety risks in the vehicle operation process, remind the driver of how to dispose faults and improve the fault disposal efficiency. The risk that the driver disposes mistakenly, does not dispose or disposes incompletely is reduced; the method improves the fault handling efficiency, shortens the fault handling time, and reduces the influence of the urban rail transit vehicle fault on the vehicle operation, and comprises the following steps: S1, fault data collection: carrying out communication with the urban rail transit vehicle to obtain the fault information of the vehicle; s2, fault data analysis: analyzing the fault information, and extracting a fault label; and S3, fault disposal scheme matching: performing retrieval and matching in a fault disposal scheme database and an expert experience database according to the fault tag.

Description

Technical Field

[0001] The present invention relates to the field of urban rail technology, and in particular to a priority sorting algorithm and system for urban rail transit vehicle fault handling solutions. Background Art

[0002] With the acceleration of urbanization, the number of vehicles and operating mileage have increased significantly, placing higher demands on operational efficiency and reliability. Currently, urban rail transit vehicles have numerous systems capable of recording and displaying vehicle faults, but fault handling relies primarily on manuals and driver proficiency, resulting in low efficiency. Furthermore, due to the diverse types of vehicle faults, including mechanical, electrical, and software failures, and the fact that currently urban rail transit vehicles can only record and display faults, drivers will report the fault and await action, or follow the relevant manual for handling. If they forget or are unsure of the correct action, they will consult the paper version of the fault handling plan and promptly address it accordingly.

[0003] However, the existing urban rail transit vehicle fault handling methods have the following defects: 1. They require high professional skills from the driver and rely on paper handling manuals and the driver's proficiency. Urban rail transit vehicles have many types of faults, and drivers are required to fully remember every step of the handling process for each fault; 2. They require high psychological quality from the driver. When a driver encounters a vehicle fault, he may feel nervous and other emotions, resulting in not knowing how to handle the fault, not being able to hear or remember the handling instructions, and not being able to find the corresponding handling plan when checking the paper manual; 3. When the driver is unsure or forgets how to handle the fault, he can only report the fault and wait for orders or check the paper manual, and cannot handle the fault in a timely manner, which makes the vehicle operation safe. Summary of the Invention

[0004] The purpose of the present invention is to provide a priority sorting algorithm and system for urban rail transit vehicle fault handling solutions to solve the problems raised in the above background technology.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] The priority sorting algorithm for urban rail transit vehicle fault handling solutions includes the following steps:

[0007] S1, fault data collection, communicate with urban rail transit vehicles to obtain vehicle fault information;

[0008] S2. Fault data analysis: analyzing the fault information and extracting fault labels;

[0009] S3, fault handling solution matching, searching and matching in the fault handling solution database and the expert experience database based on the fault label, and matching one or more fault handling solutions based on the content and similarity with the fault label;

[0010] S4. Optimize fault handling solutions. This involves recommending one or more fault handling solutions based on the recommended factors and their weights, and confirming the priority of the recommended solutions.

[0011] S5. Display of fault handling solutions: Displaying fault handling solutions to the driver based on their priority.

[0012] S6. Determine whether the fault has been resolved; if so, report that the vehicle is operating normally; if not, proceed to the next step;

[0013] S7. Return to the recommended solution, process according to other recommended solutions, and repeat step S6. If none of the recommended solutions can solve the problem, issue an alarm and report the fault.

[0014] Preferably, said S4 comprises the steps of:

[0015] Determine whether the fault matches the fault handling solution database and the expert experience database. If so, directly display the fault handling solution; if not, return to the "report processing" solution and recommend the corresponding partial solution. If the corresponding partial solution does not exist in the fault handling solution database and the expert experience database, recommend a comprehensive solution.

[0016] Preferably, S3 includes the steps of: when the treatment plan fails to solve the fault, reminding the manager of the fault type and recommending a new treatment plan, and reminding the manager whether to modify the corresponding treatment plan in the database. If so, the accuracy, click rate, etc. will be re-calculated after the treatment plan is modified.

[0017] The S2 comprises the steps of:

[0018] If there are multiple faults within the specified time, the correlation between the multiple faults is determined, and the faults are divided into fault classification labels, fault location labels, and fault critical labels based on the correlation.

[0019] The step S7 further includes the following steps:

[0020] The system learns autonomously. By mining, analyzing and integrating a large amount of fault data and treatment plan data, the system forms a new treatment plan in the database;

[0021] Fault handling solution communication: Drivers can share fault handling solutions and cases with other drivers through voice commands, exchange experiences, and improve overall fault handling capabilities.

[0022] The system is continuously optimized. It automatically mines and analyzes driver feedback data and new treatment solutions in the database, automatically discovering new failure modes and patterns, fault labeling systems, and treatment solutions in the database.

[0023] System integration and collaborative work, the system is continuously optimized and integrated with other urban rail transit systems to improve the collaborative work capability and overall efficiency of the entire urban rail transit system.

[0024] The system for handling urban rail transit vehicle faults provided by the present invention is characterized by comprising:

[0025] Fault data acquisition module, used to communicate with urban rail transit vehicles to obtain vehicle fault information;

[0026] A fault data analysis module is used to analyze the fault information and extract fault labels;

[0027] A fault handling solution matching module is used to search and match the fault handling solution database and the expert experience database according to the fault label, and match one or more fault handling solutions based on the content and similarity with the fault label;

[0028] The fault handling solution optimization module is used to recommend one or more fault handling solutions based on the recommended factors and their weights, and to determine the priority of the recommended solutions.

[0029] The fault handling solution display module is used to display the fault handling solution to the driver according to the priority of the solution;

[0030] Fault judgment module, used to judge whether the fault is resolved;

[0031] The processing module is used to return a recommended solution when the fault is not resolved, handle it according to other recommended solutions, and issue an alarm and report the fault when none of the recommended solutions can solve the problem:

[0032] The system's autonomous learning module is used to mine, analyze, and integrate large amounts of fault data and treatment plan data to form new treatment plans within the database;

[0033] The fault handling solution communication module is used by drivers to share fault handling solutions and cases with other drivers in the community through voice commands, exchanging experiences and improving the overall fault handling level;

[0034] The system's continuous optimization module is used to automatically mine and analyze driver feedback data and new processing solutions in the database, automatically discovering new failure modes and patterns, fault labeling systems, and processing solutions in the database;

[0035] The system integration and collaborative work module is used to integrate with other urban rail transit systems to improve the collaborative work capability and overall efficiency of the entire urban rail transit system.

[0036] The fault data acquisition module includes:

[0037] The judgment unit is used to judge whether the fault matches the fault handling solution database and the expert experience database. When it matches, the fault handling solution is directly displayed. When it does not match, the "report processing" solution is returned and the corresponding partial handling solution is recommended. When the corresponding partial handling solution does not exist in the fault handling solution database and the expert experience database, a comprehensive handling solution is recommended.

[0038] The fault handling solution matching module includes:

[0039] The reminder unit is used to remind managers of the fault type and recommend a new solution when the solution fails to solve the fault. It also reminds managers whether to modify the corresponding solution in the database. After the solution is modified, the accuracy and click rate will be recalculated.

[0040] Compared with the prior art, the present invention has the following beneficial effects:

[0041] 1. Automatically recommend fault handling solutions based on fault information, provide decision support for drivers, and reduce safety risks during vehicle operation.

[0042] 2. It can remind the driver how to handle the fault, reducing the risk of the driver handling it incorrectly, not knowing how to handle it, or taking incomplete handling steps.

[0043] 3. Improve fault handling efficiency, shorten fault handling time, and reduce the impact of urban rail transit vehicle failures on vehicle operations.

[0044] 4. Make full use of fault data, driver feedback data, etc. for in-depth analysis and mining, and continuously optimize recommended solutions, so that the system can self-learn and continuously improve, and better adapt to complex and changing fault conditions and operational needs.

[0045] 5. Through integration and coordination with other urban rail transit systems, data sharing and business collaboration between systems are achieved, improving the overall efficiency of the entire urban rail transit system. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 A flowchart for intelligently recommending fault handling solutions;

[0047] Figure 2 Schematic diagram of the intelligent fault resolution solution. DETAILED DESCRIPTION

[0048] In the description of the present invention, it should be understood that the terms "longitudinal", "transverse", "up", "down", "top", "bottom", "inside", "outside", etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present invention.

[0049] In the present invention, unless otherwise expressly specified or limited, the terms "mounted," "connected," "connect," "fixed," etc. should be understood broadly. For example, they may refer to fixed connection, detachable connection, or integration; mechanical connection or electrical connection; direct connection or indirect connection through an intermediate medium; internal communication between two components or interaction between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention based on specific circumstances.

[0050] The technical solution of this patent is further described in detail below in conjunction with specific implementation methods.

[0051] The priority sorting algorithm for urban rail transit vehicle fault handling solutions includes:

[0052] S1. Fault data collection: Communicate with urban rail transit vehicles to obtain vehicle fault information. By communicating with urban rail transit vehicles, the fault information collected includes traditional fault codes, fault occurrence time, vehicle real-time operating parameters such as speed, acceleration, current, voltage, temperature, etc., as well as real-time working status information of each vehicle system. At the same time, auxiliary data such as vehicle mileage, cumulative operating time, and recent maintenance records are collected to provide more comprehensive data support for subsequent in-depth analysis of the cause of the fault.

[0053] S2. Fault data analysis: analyzing the fault information and extracting fault labels;

[0054] S3, fault handling solution matching, searching and matching in the fault handling solution database and the expert experience database based on the fault label, and matching one or more fault handling solutions based on the content and similarity with the fault label;

[0055] S4. Optimize fault handling solutions. This involves recommending one or more fault handling solutions based on the recommended factors and their weights, and confirming the priority of the recommended solutions.

[0056] S5. Display of fault handling solutions: Displaying fault handling solutions to the driver based on their priority.

[0057] S6. Determine whether the fault has been resolved; if so, report that the vehicle is operating normally; if not, proceed to the next step;

[0058] S7: Return to the recommended solution and proceed according to other recommended solutions, and repeat step S6. If none of the recommended solutions can solve the problem, an alarm is issued and the fault is reported.

[0059] The S4 comprises the steps of:

[0060] Determine whether the fault matches the fault resolution solution database and the expert experience database. If so, the resolution solution is displayed directly. If not, the "report and process" solution is returned and the corresponding partial solution is recommended. If the partial solution does not exist in the fault resolution solution database or the expert experience database, a comprehensive solution is recommended. If the database does not contain a solution for "a single door fault at the platform," the solution for "door opening fault" is recommended. If the database does not contain a solution for "door opening fault," the solution for "door fault" is recommended. If the database matches multiple solutions, if the number does not exceed three, the solutions are displayed directly. If the number exceeds three, the three solutions with the most matching tags are selected for display and ranked according to accuracy, click-through rate, and other factors.

[0061] The S3 includes the following steps: when the treatment plan fails to solve the fault, reminding the manager of the fault type and recommending a new treatment plan, and reminding the manager whether to modify the corresponding treatment plan in the database. If so, the accuracy, click rate, etc. will be re-calculated after the treatment plan is modified.

[0062] The S2 comprises the steps of:

[0063] If multiple faults occur within the specified timeframe, the correlation between these faults is determined and the faults are classified into fault classification labels, fault location labels, and fault critical labels. If multiple faults occur within the specified timeframe, the correlation between these faults is determined and fault classification labels are added based on the correlation. For example, if a signal indicating that door 1 of car 1 is open after arriving at the platform is collected, the fault signal is analyzed to extract the fault classification: "Door Fault", fault location: "Car 1 Door 1", fault content: "Door Open Fault", and location information: "Platform". The system also determines whether there was a door fault shortly before the fault. If so, it determines whether the fault location is the same as or on the same side as "Car 1, Door 1." If the doors are the same, a "Platform Single Door Failure" label is added. If the doors are different but on the same side, a "Entire Side of Doors Failed to Open After the Train Arrived and Stopped Correctly" label is added. If the doors are different but not on the same side, a "Partial Door Failure After the Train Arrived and Stopped Correctly" label is added. The fault resolution database contains standardized faults and corresponding resolutions. The expert experience database contains expert resolution experiences and resolutions for faults where it's difficult to pinpoint the fault location or where there are multiple related faults.

[0064] The step S7 further includes the following steps:

[0065] The system learns autonomously. By mining, analyzing and integrating a large amount of fault data and treatment plan data, the system forms a new treatment plan in the database;

[0066] Fault handling solution communication: Drivers can see virtual operation steps and prompt information at the fault scene through AR glasses or the in-vehicle display. Using the voice interaction function, drivers can share S5 fault handling solution cases with other drivers through voice commands, making it easier for other drivers to exchange experiences and improve overall fault handling capabilities.

[0067] The system is continuously optimized. It automatically mines and analyzes driver feedback data and new treatment solutions in the database, automatically discovering new failure modes and patterns, fault labeling systems, and treatment solutions in the database.

[0068] System integration and collaborative work, the system is continuously optimized and integrated with other urban rail transit systems to improve the collaborative work capability and overall efficiency of the entire urban rail transit system.

[0069] Multi-factor dynamic weighted fault prioritization algorithm; including

[0070] S.1.1 For the nth fault handling solution to be recommended, the system needs to extract the following key indicators: historical success rate factor SF, handling time estimation factor TF, driver proficiency factor DDF, solution feasibility factor FF, current train operation status factor TOSF, and passenger density factor PDF;

[0071] S.1.2 Based on the above extracted factors, the priority score of the nth fault handling solution is calculated using the dynamic weighted formula (1):

[0072] Where w SF 、w TF 、w DDF 、w FF 、w TOSF 、w PDF are the weights of each factor respectively;

[0073] The weight coefficients of factors S and 1.3 are dynamically adjusted according to the current operating conditions using formula (2):

[0074] Where, Represents the weight coefficient of the i-th factor before dynamic adjustment; represents the dynamically adjusted weight coefficient of the i-th factor; OC represents the current operating situation; f change (OC) represents the dynamic adjustment function;

[0075] S.1.4 Sort all the recommended solutions according to the priority score of each solution. Solutions with higher priority scores are ranked higher, and solutions with lower priority scores are ranked lower.

[0076] A system for handling urban rail transit vehicle faults, characterized by comprising:

[0077] Fault data acquisition module, used to communicate with urban rail transit vehicles to obtain vehicle fault information;

[0078] A fault data analysis module is used to analyze the fault information and extract fault labels;

[0079] A fault handling solution matching module is used to search and match the fault handling solution database and the expert experience database according to the fault label, and match one or more fault handling solutions based on the content and similarity with the fault label;

[0080] The fault handling solution optimization module is used to recommend one or more fault handling solutions based on the recommended factors and their weights, and to determine the priority of the recommended solutions.

[0081] The fault handling solution display module is used to display the fault handling solution to the driver according to the priority of the solution;

[0082] Fault judgment module, used to judge whether the fault is resolved;

[0083] The processing module is used to return a recommended solution when the fault is not resolved, process it according to other recommended solutions, and issue an alarm and report the fault when none of the recommended solutions can solve the problem.

[0084] The system's autonomous learning module is used to mine, analyze, and integrate large amounts of fault data and treatment plan data to form new treatment plans within the database;

[0085] The fault handling solution communication module is used by drivers to share fault handling solutions and cases with other drivers in the community through voice commands, exchanging experiences and improving the overall fault handling level;

[0086] The system's continuous optimization module is used to automatically mine and analyze driver feedback data and new processing solutions in the database, automatically discovering new failure modes and patterns, fault labeling systems, and processing solutions in the database;

[0087] The system integration and collaborative work module is used to integrate with other urban rail transit systems to improve the collaborative work capability and overall efficiency of the entire urban rail transit system.

[0088] The fault data acquisition module includes:

[0089] The judgment unit is used to judge whether the fault matches the fault handling solution database and the expert experience database. When it matches, the fault handling solution is directly displayed. When it does not match, the "report processing" solution is returned and the corresponding partial handling solution is recommended. When the corresponding partial handling solution does not exist in the fault handling solution database and the expert experience database, a comprehensive handling solution is recommended.

[0090] The fault handling solution matching module includes:

[0091] The reminder unit is used to remind managers of the fault type and recommend a new solution when the solution fails to solve the fault. It also reminds managers whether to modify the corresponding solution in the database. After the solution is modified, the accuracy and click rate will be recalculated.

[0092] The fault data analysis module includes:

[0093] It is used to judge the correlation of multiple faults and classify the faults into fault classification labels, fault location labels, and fault critical labels based on the correlation.

[0094] The fault handling solution database includes standardized faults and corresponding handling solutions.

[0095] The working principle and operating method of the system of the urban rail transit vehicle fault handling solution are the same as the working principle and operating method of the priority sorting algorithm of the above-mentioned urban rail transit vehicle fault handling solution, and will not be described in detail.

[0096] In addition, it should be understood that although this specification is described in terms of implementation methods, not every implementation method contains only one independent technical solution. This narrative method of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment can also be appropriately combined to form other implementation methods that can be understood by those skilled in the art.

Claims

1. A priority sorting algorithm for urban rail transit vehicle fault handling solutions, characterized in that: The following steps are involved: S1, fault data collection, communicate with urban rail transit vehicles to obtain vehicle fault information; S2. Fault data analysis: analyzing the fault information and extracting fault labels; S3, fault handling solution matching, searching and matching in the fault handling solution database and the expert experience database based on the fault label, and matching one or more fault handling solutions based on the content and similarity with the fault label; S4. Optimize fault handling solutions. This involves recommending one or more fault handling solutions based on the recommended factors and their weights, and confirming the priority of the recommended solutions. S5. Display of fault handling solutions: Displaying fault handling solutions to the driver based on their priority. S6. Determine whether the fault has been resolved; if so, report that the vehicle is operating normally; if not, proceed to the next step; S7. Return to the recommended solution, process according to other recommended solutions, and repeat step S6. If none of the recommended solutions can solve the problem, issue an alarm and report the fault.

2. The priority sorting algorithm for urban rail transit vehicle fault handling scheme according to claim 1 is characterized in that: The S4 comprises the steps of: Determines whether the fault matches the fault resolution solution database and the expert experience database. If so, displays the fault resolution solution directly. If not, returns the "report and handle" resolution solution and recommends a corresponding partial resolution solution. If no corresponding partial resolution solution exists in the fault resolution solution database or the expert experience database, recommends a comprehensive resolution solution.

3. The priority sorting algorithm for urban rail transit vehicle fault handling scheme according to claim 2 is characterized in that: The S3 comprises the steps of: When the solution fails to resolve the fault, the administrator is reminded of the fault type and a new solution is recommended. At the same time, the administrator is reminded whether to modify the corresponding solution in the database. If so, the accuracy, click rate, etc. will be re-calculated after the solution is modified.

4. The priority sorting algorithm for urban rail transit vehicle fault handling scheme according to claim 3 is characterized in that: Said S2 comprises the steps of: If there are multiple faults within the specified time, the correlation between the multiple faults is determined, and the faults are divided into fault classification labels, fault location labels, and fault critical labels based on the correlation.

5. The prioritization algorithm for urban rail transit vehicle fault handling scheme according to claim 4, further comprising the steps of: The system learns autonomously. By mining, analyzing and integrating a large amount of fault data and treatment plan data, the system forms a new treatment plan in the database; Fault handling solution communication: Drivers can share fault handling solutions and cases with other drivers through voice commands, exchange experiences, and improve overall fault handling capabilities. The system is continuously optimized. The system automatically mines and analyzes the feedback data from drivers' exchanges of experience and new processing solutions in the database, and automatically discovers new fault modes and patterns, fault labeling systems and processing solutions in the database; system integration and collaborative work, the system is continuously optimized and integrated with other systems of urban rail transit to improve the collaborative working ability and overall efficiency of the entire urban rail transit system.

6. A system for handling urban rail transit vehicle faults, characterized in that: include: Fault data acquisition module, used to communicate with urban rail transit vehicles to obtain vehicle fault information; A fault data analysis module is used to analyze the fault information and extract fault labels; A fault handling solution matching module is used to search and match the fault handling solution database and the expert experience database according to the fault label, and match one or more fault handling solutions based on the content and similarity with the fault label; The fault handling solution optimization module is used to recommend one or more fault handling solutions based on the recommended factors and their weights, and to determine the priority of the recommended solutions. The fault handling solution display module is used to display the fault handling solution to the driver according to the priority of the solution; Fault judgment module, used to judge whether the fault is resolved; The processing module is used to return a recommended solution when the fault is not resolved, process it according to other recommended solutions, and issue an alarm and report the fault when none of the recommended solutions can solve the problem.

7. The system for handling urban rail transit vehicle faults according to claim 6, characterized in that: The fault data acquisition module includes: The judgment unit is used to determine whether the fault matches the fault handling solution database and the expert experience database. If it matches, the fault handling solution is directly displayed. If it does not match, the "report processing" solution is returned and the corresponding partial solution is recommended. If the corresponding partial solution does not exist in the fault handling solution database and the expert experience database, a comprehensive solution is recommended.

8. The system for handling urban rail transit vehicle faults according to claim 6, characterized in that: The fault handling solution matching module includes: The reminder unit is used to remind managers of the fault type and recommend a new solution when the solution fails to solve the fault. It also reminds managers whether to modify the corresponding solution in the database. After the solution is modified, the accuracy and click rate will be recalculated.

9. The system for handling urban rail transit vehicle faults according to claim 6, characterized in that: The fault data analysis module includes: It is used to determine the correlation of multiple faults and classify the faults into fault classification labels, fault location labels, and fault critical labels based on the correlation.

10. The system for handling urban rail transit vehicle faults according to claim 6, comprising: The system's autonomous learning module is used to mine, analyze, and integrate large amounts of fault data and treatment plan data to form new treatment plans within the database; The fault handling solution communication module is used by drivers to share fault handling solutions and cases with other drivers in the community through voice commands, exchanging experiences and improving the overall fault handling level; The system's continuous optimization module is used to automatically mine and analyze driver feedback data and new processing solutions in the database, automatically discovering new failure modes and patterns, fault labeling systems, and processing solutions in the database; The system integration and collaborative work module is used to integrate with other urban rail transit systems to improve the collaborative work capability and overall efficiency of the entire urban rail transit system.

Images