Maintenance shop information pushing method and device, electronic equipment and storage medium

Abstract

The invention relates to a maintenance shop information pushing method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining vehicle fault information which represents the fault of a target vehicle, and determining the vehicle position of the target vehicle; the distance between the vehicle position and the maintenance shop is smaller than or equal to a preset distance threshold value, a maintenance shop set is obtained, the fault type of the target vehicle is determined based on the vehicle fault information, and a target maintenance shop is determined from the maintenance shop set to push target maintenance shop information of the target maintenance shop, the type of the target maintenance shop is matched with the fault type. Therefore, through matching of the fault type and the type of the maintenance shop, the target maintenance shop suitable for processing the current fault is determined, and the effect of pushing appropriate target maintenance shop information when the vehicle has the fault is achieved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for pushing repair shop information. Background Art

[0002] With the improvement of technological capabilities, the structure, power system, power system and other aspects of the vehicle are constantly being updated. When failures occur in different structures, power systems, power systems and other aspects, different repair methods are required. However, users cannot understand the specific repair methods for various types of vehicle failures, or even if they understand the repair methods, they cannot perform repairs themselves. Therefore, currently when a vehicle fails, it can be repaired by a repair shop.

[0003] When users are looking for repair shops, they do not know whether each repair shop can repair the current fault of the vehicle, and what the specific repair effect is. At this time, choosing an inappropriate repair shop will cause time and economic losses to the user. Therefore, there is a problem that suitable repair shop information cannot be obtained when the vehicle breaks down. Summary of the invention

[0004] In order to solve the above technical problems, the present application provides a method, device, electronic device and storage medium for pushing repair shop information.

[0005] In a first aspect, the present application provides a method for pushing repair shop information, the method comprising:

[0006] Acquiring vehicle fault information, wherein the vehicle fault information indicates a fault of a target vehicle;

[0007] determining a vehicle position of the target vehicle;

[0008] Determine a repair shop whose distance from the vehicle location is less than or equal to a preset distance threshold, and obtain a repair shop set;

[0009] Based on the vehicle fault information, determining the fault type of the target vehicle;

[0010] A target repair shop is determined from the repair shop set to push target repair shop information of the target repair shop, wherein a type of the target repair shop matches the fault type.

[0011] Optionally, determining the vehicle position of the target vehicle includes:

[0012] Based on the vehicle fault information, determining a maintenance type of the target vehicle, the maintenance type indicating whether the fault of the target vehicle requires maintenance at a repair shop;

[0013] When the maintenance type indicates that the fault of the target vehicle does not require maintenance at a maintenance shop, outputting self-repair information;

[0014] In a case where the repair type indicates that the failure of the target vehicle requires repair by a repair shop, a vehicle position of the target vehicle is determined.

[0015] Optionally, determining the maintenance type of the target vehicle based on the vehicle fault information includes:

[0016] Comparing the vehicle fault information with the fault case information in the fault case information set to determine whether there is fault case information matching the vehicle fault information;

[0017] In the case where there is no fault case information matching the vehicle fault information in the fault case information set, determining that the repair type indicates that repair at a repair shop is required;

[0018] When there is fault case information matching the vehicle fault information in the fault case information set, the fault case information matching the vehicle fault information is determined as target fault case information, and based on the target fault case information, the maintenance type of the target vehicle is determined.

[0019] Optionally, determining the maintenance type of the target vehicle based on the target fault case information includes:

[0020] Based on the target fault case information, determining first maintenance strategy information, wherein the first maintenance strategy information indicates a strategy for maintaining the target vehicle;

[0021] Acquire first input information, where the first information represents instruction information of whether maintenance at a maintenance shop is required, which is input based on the first maintenance strategy information;

[0022] A maintenance type of the target vehicle is determined based on the first input information.

[0023] Optionally, the repair shop set includes repair shop types, and,

[0024] The step of determining a target repair shop from the set of repair shops includes:

[0025] Determining whether there is a repair shop in the repair shop set whose repair shop type matches the fault type based on a preset correspondence table, wherein the preset correspondence table indicates a matching relationship between the repair shop type and the fault type;

[0026] In the case that there is a repair shop whose repair shop type matches the fault type in the repair shop set, the repair shop whose repair shop type matches the fault type is determined as a target repair shop.

[0027] Optionally, when there is a repair shop whose repair shop type matches the fault type in the repair shop set, determining the repair shop whose repair shop type matches the fault type as the target repair shop includes:

[0028] In the case that there is a repair shop whose repair shop type matches the fault type in the repair shop set, determining the set of repair shops whose repair shop type matches the fault type as a repair shop subset;

[0029] Determine a repair success rate of each repair shop in the repair shop subset, wherein the repair success rate represents a success rate of the repair shop in repairing the fault;

[0030] The repair shop with the highest repair success rate is determined as the target repair shop.

[0031] Optionally, the method further includes:

[0032] Acquiring second maintenance strategy information, where the second maintenance strategy information indicates a maintenance strategy determined by the target maintenance shop based on the vehicle fault information;

[0033] In a case where the maintenance strategy indicated by the second maintenance strategy information belongs to an excessive maintenance type, another maintenance shop in the maintenance shop subset is extracted as an updated target maintenance shop.

[0034] In a second aspect, the present application provides a device for pushing repair shop information, the device comprising:

[0035] A first acquisition module, used to acquire vehicle fault information, wherein the vehicle fault information indicates a fault of a target vehicle;

[0036] A first determination module, used to determine the vehicle position of the target vehicle;

[0037] A second determination module is used to determine a repair shop whose distance from the vehicle position is less than or equal to a preset distance threshold, and obtain a repair shop set;

[0038] A third determination module, configured to determine a fault type of the target vehicle based on the vehicle fault information;

[0039] The target module is used to determine a target repair shop from the repair shop set to push target repair shop information of the target repair shop, wherein the type of the target repair shop matches the fault type.

[0040] In a third aspect, an electronic device is provided, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0041] Memory, used to store computer programs;

[0042] The processor is used to implement the method described in any embodiment of the first aspect when executing the program stored in the memory.

[0043] According to a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method described in any one of the embodiments of the first aspect is implemented.

[0044] The above technical solution provided by the embodiment of the present application has the following advantages compared with the prior art:

[0045] The method provided by the embodiment of the present application is as follows: obtaining vehicle fault information, the vehicle fault information indicates the fault of the target vehicle, and determining the vehicle position of the target vehicle, determining the repair shop whose distance from the vehicle position is less than or equal to the preset distance threshold, obtaining a repair shop set, and determining the fault type of the target vehicle based on the vehicle fault information, and determining the target repair shop from the repair shop set to push the target repair shop information of the target repair shop, wherein the type of the target repair shop matches the fault type. Thus, by matching the fault type with the type of the repair shop, the target repair shop suitable for handling the current fault is determined, and the effect of pushing appropriate target repair shop information when the vehicle fails is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0047] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0048] Figure 1 A flowchart of a method for pushing repair shop information provided in an embodiment of the present application;

[0049] Figure 2 A flowchart of a method for pushing repair shop information provided by another embodiment of the present application;

[0050] Figure 3A flowchart of a method for pushing repair shop information provided by another embodiment of the present application;

[0051] Figure 4 A schematic diagram of the structure of a device for pushing repair shop information provided in an embodiment of the present application;

[0052] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The following will describe the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention, not for limiting the scope of protection of the present invention.

[0054] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0055] With the improvement of vehicle technology, electrification, networking and intelligence have become the trend of vehicle improvement and development. Therefore, all aspects of the vehicle are constantly being updated, such as body structure, power system, chassis system, electronic and electrical system, etc., which makes vehicle maintenance increasingly complicated and the universality of maintenance methods is constantly decreasing. Different repair shops can repair different types of faults. For example, repair shop A can repair the body structure but not the power system, and repair shop B can repair the power system but not the body structure. At this time, when the vehicle has a power system failure, if you go to repair shop A, it will not be able to provide maintenance services for the vehicle, which will cause time and economic losses to users. Therefore, there is a problem of not being able to effectively choose a suitable repair shop when the vehicle fails.

[0056] Figure 1 A flowchart of a method for pushing repair shop information provided in an embodiment of the present application.

[0057] like Figure 1 As shown, the present application discloses an embodiment, providing a method for pushing repair shop information, the method comprising:

[0058] S110: Acquire vehicle fault information, where the vehicle fault information indicates a fault of the target vehicle;

[0059] In this embodiment, the method for pushing repair shop information can be applied to a server or client, such as an application in a mobile phone, an application in a vehicle control system, etc. The specific process of obtaining vehicle fault information can be based on the user inputting instruction information containing information such as fault code, fault phenomenon, and vehicle running status before the fault, to obtain vehicle fault information, or based on the vehicle control system actively collecting vehicle fault information when a vehicle fault is detected, to obtain vehicle fault information.

[0060] S120: Determine the vehicle position of the target vehicle.

[0061] In this embodiment, after obtaining the vehicle fault information, the specific fault condition of the vehicle can be determined based on the vehicle fault information, so as to judge whether the current vehicle needs to be repaired by a repair shop. If the repair shop needs to be repaired, the vehicle position of the target vehicle needs to be determined. The process of determining the vehicle position can be based on the position information input by the user, or based on the positioning information of the target vehicle. After determining the vehicle position of the target vehicle, the repair shop that can be selected can be determined according to the vehicle position. Therefore, S120 determining the vehicle position of the target vehicle may include:

[0062] Based on the vehicle fault information, determining a repair type of the target vehicle, the repair type indicating whether the fault of the target vehicle requires repair at a repair shop;

[0063] When the repair type indicates that the fault of the target vehicle does not require repair by a repair shop, outputting self-repair information;

[0064] In a case where the repair type indicates that the failure of the target vehicle requires repair at a repair shop, the vehicle position of the target vehicle is determined.

[0065] In this embodiment, based on the vehicle fault information, the maintenance type of the target vehicle is determined. The maintenance type indicates whether the fault of the target vehicle needs to be repaired by a repair shop. For example, the maintenance type can be 0 or 1, 0 indicates that no repair shop is needed, and 1 indicates that repair shop is needed. When the maintenance type indicates that the fault of the target vehicle does not need to be repaired by a repair shop, such as the battery is dead, the handbrake is not pulled, and other easy-to-eliminate faults, self-repair information is output at this time. The self-repair information may include the maintenance manual information corresponding to the current fault information, so that the user can repair the fault of the target vehicle based on the maintenance manual information. When the maintenance type indicates that the fault of the target vehicle needs to be repaired by a repair shop, such as the power system fault, sensor abnormality, and other faults that are difficult to eliminate by themselves, the vehicle position of the target vehicle needs to be determined at this time, so as to determine the repair shop that can be selected near the vehicle position. After obtaining the vehicle fault information, it can be determined whether the vehicle needs to be repaired by a repair shop based on the maintenance type determined by the vehicle fault information, so as to pre-judge the fault of the target vehicle, and avoid some easy-to-eliminate faults that cause users to go to the repair shop, resulting in time and economic consumption.

[0066] like Figure 2 As shown, in one embodiment, determining the maintenance type of the target vehicle based on the vehicle fault information includes:

[0067] S121: Compare the vehicle fault information with the fault case information in the fault case information set to determine whether there is fault case information matching the vehicle fault information;

[0068] S122: if there is no fault case information matching the vehicle fault information in the fault case information set, determining that the repair type indicates that repair at a repair shop is required;

[0069] S123: When there is fault case information matching the vehicle fault information in the fault case information set, the fault case information matching the vehicle fault information is determined as target fault case information, and based on the target fault case information, a maintenance type of the target vehicle is determined.

[0070] In this embodiment, the storage entity of the fault case information set may be a database, an application platform, a system, etc. The fault case information set is used to store a number of preset fault case information. The fault case information may include the cause of the vehicle fault, the processing process, the processing result, the repair shop processing status, etc. For example, it may specifically include: the driving state before the fault, the fault vehicle information, the fault phenomenon, the fault code, the fault cause, the fault handling countermeasures, the fault repair shop information, etc.; the driving state before the fault may be whether the working environment and parking environment of the vehicle before the fault occurs are extreme, whether the vehicle has other abnormalities, etc., such as whether the vehicle has waded, whether the vehicle has been exposed to the sun for a long time, whether the vehicle has occasional oil leakage, etc.; the fault vehicle Vehicle information may include: vehicle brand, vehicle model, vehicle production date, etc.; fault phenomenon may be information about vehicle abnormal phenomenon subjectively felt by the owner when the vehicle breaks down, such as software abnormality information, vehicle abnormal noise information, power abnormality information, etc.; fault code may be fault alarm prompt information, fault alarm code, etc.; fault cause may be external factor information or internal factor information causing the fault, such as component damage, component matching abnormality, software abnormality, driver-related reasons, driving road condition-related reasons, etc.; fault handling countermeasures may include replacement of parts, software upgrade, automatic disappearance of fault, etc.; fault handling repair shop information may be whether the repair shop is a 4S shop, the address of the repair shop, fault handling satisfaction, etc.

[0071] The fault case information set may also include statistical result information based on the fault case information statistics. The statistical result information may include automobile brand failure rate, vehicle fault type ranking, component failure rate, component fault type ranking, vehicle similar fault cause analysis and measures, component similar fault cause analysis and measures, repair shop handling success rate of different fault types, various types of fault handling procedures, etc. The statistical result information may count the cause, handling process, handling result, repair shop handling status, etc. of the fault case information, so that in the process of determining whether there is fault case information matching the vehicle fault information in the fault case information set, auxiliary judgment can be made based on the statistical result information. Here, The match is that the similarity between the vehicle fault information and the fault case information reaches the preset similarity threshold, then the two are considered to match. The match between the two means that the fault represented by the current vehicle fault information can refer to the fault handling situation in the fault case information to determine whether it is necessary to go to a repair shop for repair, that is, the repair type of the target vehicle can be determined based on the target fault case information, which plays a role in quickly determining the repair type of the target vehicle; and when there is no fault case information matching the vehicle fault information in the fault case information set, it means that the relevant information of the fault of the target vehicle cannot be obtained based on the fault case information. At this time, it is necessary to go to a repair shop for processing, that is, determining the repair type means that it needs to be repaired by a repair shop.

[0072] When the storage subject of the fault case information set is an application platform, the application platform may include an application platform access module, an application platform management module, an application platform statistics module, and an application platform application module.

[0073] The application platform access module is used to confirm the member subject and the member points of the member subject; the application platform can adopt a membership system, and the member subjects can include host manufacturers, parts manufacturers, 4S repair shops, individual repair shops, repair enthusiasts, car users, etc. Member subjects can include two types of subject subjects: one is a large subject type, such as large host manufacturers and various large parts manufacturers. The initial points of large subject type members are k = 1000 points; the other is a small and medium-sized subject type, such as small enterprises, 4S repair shops, individual repair shops, repair enthusiasts, car users, etc. The initial points of small and medium-sized subject types are k = 450 points; wherein, the determination of the subject type can be determined according to preset rules, such as the number of personnel, establishment time, etc.

[0074] All member entities can upload vehicle fault case information to the application platform. Fault case information may include: driving status before the fault, fault vehicle information, fault phenomenon, fault code, fault cause, fault handling countermeasures, fault repair shop information, etc. The fault case information uploaded by members may specifically be a repair order, video, photo or other supporting material information.

[0075] The application platform management module is used for the review of fault case information, value assessment, rewards, and member permission settings.

[0076] The review of fault case information means judging whether the case is a real case based on the uploaded fault case information. If the case is a false case, the member points of the uploaded member entity will be deducted. The specific deduction method can be 5% of the total points for the first time, 20% of the total points for the second time, and 50% of the total points for the third time.

[0077] The value assessment of fault case information means evaluating the market value of the case from three dimensions: complete case information, case subordinate information, and case novelty information. The application platform determines the case integral value Φ based on the case value assessment.

[0078] The complete information of the case indicates the degree of comprehensiveness of the description of the case status by the member who uploaded the fault case information, such as the time of fault occurrence, fault description, fault handling countermeasures, fault cause, fault vehicle model, fault component manufacturer, fault handling code, fault handling satisfaction, etc. The complete information coefficient of the case can be divided into three levels: 1-0.7 (very comprehensive), 0.7-0.4 (relatively comprehensive), and 0.4-0 (not comprehensive).

[0079] The case dependency information indicates that the case is classified according to the functions of the parts involved, and the case dependency coefficient з is divided into four levels: 0.8 (chassis module, power module, electronic appliances), 0.5 (body, air conditioning), 0.3 (interior and exterior decoration, body accessories and others).

[0080] Case novelty information indicates the similarity between the current case and the cases in the case library. The novelty coefficient σ is divided into three levels: 1-0.6 (similarity 0-30%), 0.6-0.3 (similarity 30-60%), and 0.3-0 (similarity 60-100%).

[0081] The case integral value Φ = δ × з × σ is obtained by combining the coefficient δ of case complete information, the coefficient з of case subordinate information, and the coefficient σ of case novel information. The application platform assigns members points and corresponding material rewards based on the case integral value Φ: Φ < 0.1, 1 point; 0.1 < Φ ≤ 0.25, 2 points; 0.25 < Φ ≤ 0.35, 3 points; 0.35 < Φ, 4 points.

[0082] The case reward mechanism means that members are awarded points based on case points and given corresponding material rewards. The method and level of material rewards can be set according to the needs of the application platform.

[0083] The statistical analysis module is used to associate data such as the time of fault occurrence, fault description, fault handling measures, fault cause, fault vehicle model, fault component manufacturer, fault code, fault cause, fault handling measures, and fault repair shop information, and use mathematical models to achieve key information statistics, such as: automobile brand failure rate, vehicle fault type ranking, component failure rate, component fault type ranking, analysis and measures of similar vehicle fault causes, analysis and measures of similar component fault causes, confidence index of different types of fault repair shops, and various types of fault handling procedures, etc., to provide data support and decision-making basis for users to purchase vehicles, vehicle manufacturer product optimization, vehicle manufacturer component selection, component manufacturer product improvement, and automobile user fault handling.

[0084] The confidence index of repair shops for different types of faults refers to the system determining the types of faults that different repair shops are good at handling (such as power-related faults, electronic and electrical related faults, chassis-related faults, etc.) based on the case subordinate module and fault repair satisfaction, and classifying the repair shops to help users quickly find repair shops with a high confidence index based on the fault type, thereby improving repair efficiency.

[0085] At the same time, the application platform will set viewing permissions for statistical data based on factors such as the importance of the information, the requirements of the case provider, and the particularity of the case. Different permissions have different capabilities for querying and obtaining information. There are four levels of permissions, including level one, level two, level three, and level four.

[0086] Level 1 permissions can query the following information, including but not limited to: automobile brand failure rate, vehicle failure type ranking, component failure rate, component failure type ranking, analysis and measures for similar vehicle failure causes, analysis and measures for similar component failure causes, confidence index of repair shops for different types of failures, and procedures for handling various types of failures.

[0087] The second-level permissions can query the following information, including but not limited to: analysis of causes and measures for similar failures of the whole vehicle, analysis of causes and measures for similar failures of parts and components, confidence index of repair shops for different types of failures, and procedures for handling various types of failures.

[0088] Level 3 permissions can query the following information, including but not limited to: analysis of causes and measures for similar vehicle failures, confidence index of repair shops for different types of failures, and procedures for handling various types of failures.

[0089] Level 4 permissions allow you to query the following information, including but not limited to: various types of fault handling procedures, etc.

[0090] The different authority levels of the member subject can be determined according to the member point value k. For example, when k≥1500, the first level authority can be obtained; 1000<k≤1500, the second level authority can be obtained; 500<k≤1000, the third level authority can be obtained; k<500, the fourth level authority can be obtained.

[0091] In one embodiment, determining the maintenance type of the target vehicle based on the target fault case information includes:

[0092] Based on the target fault case information, determining first maintenance strategy information, the first maintenance strategy information indicating a strategy for maintaining the target vehicle;

[0093] Acquire first input information, where the first information represents instruction information of whether a repair shop needs to be repaired based on the first repair strategy information;

[0094] A maintenance type of the target vehicle is determined based on the first input information.

[0095] In this embodiment, after determining the target fault case information that matches the vehicle fault information, the first maintenance strategy information can be determined based on the target fault case information. The first maintenance strategy information indicates a strategy for repairing the target vehicle, such as the processing process, processing result, and maintenance shop processing status light information included in the target fault case information. At this time, the first maintenance strategy information can be output for the user to view. The user can determine whether the maintenance shop needs to be repaired based on the first maintenance strategy information and input the first input information. For example, after viewing the first maintenance strategy information, the user believes that the vehicle cannot be repaired by itself. At this time, the user inputs the instruction information indicating that the maintenance shop needs to be repaired as the first input information. On the contrary, after viewing the first maintenance strategy information, the user believes that the vehicle can be repaired by itself. At this time, the user inputs the instruction information indicating that the maintenance shop does not need to be repaired as the first input information. In addition, the first maintenance strategy information can be predicted and processed by using a learning model, a prediction algorithm, etc., and a prediction result can be output. The prediction result indicates whether the maintenance shop needs to be repaired. At this time, the first input information can be obtained based on the prediction result, and the first input information can also be obtained in other ways. Finally, the maintenance type of the target vehicle can be determined based on the first input information.

[0096] S130: Determine the repair shops whose distances to the vehicle location are less than or equal to a preset distance threshold, and obtain a set of repair shops.

[0097] In this embodiment, after determining the vehicle location, a repair shop whose distance from the vehicle location is less than or equal to a preset distance threshold can be determined. The preset distance threshold can be set according to demand, such as 5 kilometers, 10 kilometers, etc. The set of repair shops whose distance from the vehicle location is less than or equal to the preset distance threshold is determined as a repair shop set. It should be noted that the repair shop set can be a set of information of each repair shop, and the repair shop information can include information such as the repair shop location, status, repair fault type, and repair shop type.

[0098] S140: Determine the fault type of the target vehicle based on the vehicle fault information.

[0099] In this embodiment, since the vehicle fault information indicates the fault of the target vehicle, and vehicle faults are diverse, each type of fault has its own type. For example, failure to ignite belongs to the fault type of the electric system, and acceleration problems belong to the fault type of the power system. Therefore, the fault type can be a power system fault type, a chassis fault type, an electric system fault type, a component fault type, etc. The fault type of the target vehicle is determined by the vehicle fault information, which makes it easy to determine the repair shop suitable for repairing the target vehicle according to the fault type.

[0100] S150: Determine a target repair shop from the repair shop set to push target repair shop information of the target repair shop, wherein the type of the target repair shop matches the fault type.

[0101] In this embodiment, the process of determining the target repair shop in the repair shop set may be to determine the target repair shop according to the matching degree between the fault type and the type of the repair shop in the repair shop set, the repair shop set may include the repair shop type, and S150 determines the target repair shop from the repair shop set, which may include:

[0102] Based on a preset correspondence table, determining whether there is a repair shop in the repair shop set whose repair shop type matches the fault type, wherein the preset correspondence table indicates a matching relationship between the repair shop type and the fault type;

[0103] In the case that there is a repair shop whose repair shop type matches the fault type in the repair shop set, the repair shop whose repair shop type matches the fault type is determined as the target repair shop.

[0104] In this embodiment, since there are many types of vehicle faults and the repair scope of each repair shop is limited, this embodiment uses the repair shop type to indicate the repair scope of the repair shop. For example, if a repair shop can only repair power system faults, then the repair shop type may be a power system repair shop type. If the repair shop can repair power system and chassis faults, then the repair shop type may be a power system repair shop type and a chassis repair shop type. Therefore, there may be one or more repair shop types. The preset correspondence table indicates the matching relationship between the repair shop type and the fault type. The matching relationship indicates that the repair shop of the repair shop type can repair the fault indicated by the fault type. Therefore, the matching relationship may be a one-to-one match, or a many-to-one or one-to-one match. Any number is acceptable, for example, the power system repair shop type matches the power system fault type, or the chassis repair shop type matches the chassis fault type and the component fault type respectively; when there is no repair shop in the repair shop set whose repair shop type matches the fault type, it means that there is no repair shop in the repair shop set that can repair the fault represented by the current vehicle fault information. At this time, the unmatched repair shop information can be output to remind the user; when there is a repair shop in the repair shop set whose repair shop type matches the fault type, it means that there is a repair shop in the repair shop set that can repair the fault represented by the current vehicle fault information. At this time, the repair shop whose repair shop type matches the fault type can be determined as the target repair shop.

[0105] After the target repair shop is determined, the target repair shop information of the target repair shop can be pushed, and the specific push method can be push in the form of text message push, push in the form of video data, etc.

[0106] Since there may be multiple repair shops in the repair shop set whose repair shop types match the fault type, there is a problem of needing to determine a target repair shop from the multiple repair shops.

[0107] In one embodiment, when there is a repair shop whose repair shop type matches the fault type in the repair shop set, determining the repair shop whose repair shop type matches the fault type as the target repair shop includes:

[0108] In the case that there are repair shops whose repair shop types match the fault types in the repair shop set, determining the set of repair shops whose repair shop types match the fault types as a repair shop subset;

[0109] Determine the repair success rate of each repair shop in the repair shop subset, where the repair success rate represents the success rate of the repair shop in repairing the fault;

[0110] The repair shop with the highest repair success rate is determined as the target repair shop.

[0111] In this embodiment, when there are repair shops whose repair shop types match the fault types in the repair shop set, the set of repair shops whose repair shop types match the fault types is determined as a repair shop subset, and the repair shops in the repair shop subset are all able to repair the faults indicated by the vehicle fault information. At this time, the repair success rate of each repair shop in the repair shop subset is determined, and the repair success rate indicates the success rate of the repair shop in repairing the fault. In combination with the foregoing content, the fault case information set may also include statistical result information obtained based on the fault case information statistics, and the statistical result information may include the success rate of the repair shop in repairing the fault. Therefore, the success rate of the repair shop in the fault case information set is extracted to determine the repair success rate of each repair shop in the repair shop subset. The repair success rate of each repair shop in the repair shop subset can be determined by a method such as presetting a repair success rate set of each repair shop and determining the repair success rate of each repair shop in the repair shop subset according to the preset repair success rate set of the repair shops; then the repair shop with the largest repair success rate is determined as the target repair shop, thereby playing the role of determining the repair shop with the largest repair success rate in the repair shop subset as the target repair shop. In addition, according to user needs, in addition to determining the repair success rate of each repair shop in the repair shop subset to determine the target repair shop, the target repair shop that meets the user needs can also be determined from the repair shop subset through information such as the repair rate of the repair shop and the repair cost of the repair shop; the specific process is similar to that of the present embodiment and will not be repeated here.

[0112] When users have their vehicles repaired at a repair shop, they often encounter abnormal charges and excessive repairs, which results in excessively high repair costs for users.

[0113] like Figure 3 As shown, in one embodiment, the method may further include:

[0114] S160: Acquire second maintenance strategy information, where the second maintenance strategy information indicates a maintenance strategy determined by the target maintenance shop based on the vehicle fault information;

[0115] S161: when the maintenance strategy indicated by the second maintenance strategy information belongs to the over-maintenance type, extract another maintenance shop in the maintenance shop subset as an updated target maintenance shop;

[0116] S162: When the maintenance strategy indicated by the second maintenance strategy information does not belong to the excessive maintenance type, output maintenance rationality information.

[0117] In this embodiment, after the target repair shop is determined, the second repair strategy information can be obtained. For example, after the target repair shop is determined, the vehicle fault information is sent to the target repair shop terminal, and the target repair shop terminal feeds back the second repair strategy information based on the vehicle fault information. The second repair strategy information indicates the repair strategy determined by the target repair shop based on the vehicle fault information. The second repair strategy information may include information such as the repair method, repair cost, and repair process. Then, it can be determined whether the repair strategy indicated by the second repair strategy information belongs to the excessive repair type. The specific determination method may be user determination or learning model prediction determination. The user determination process may be: the user may view the second repair strategy information, An update instruction is input, and the update instruction indicates an instruction on whether to update a target repair shop. For example, if a user views the second repair strategy information and believes that the repair strategy represented by the second repair strategy information belongs to the excessive repair type, then an update instruction on updating the target repair shop is input. On the contrary, if a user views the second repair strategy information and believes that the repair strategy represented by the second repair strategy information does not belong to the excessive repair type, then an update instruction on not needing to update the target repair shop is input. The learning model prediction and judgment process may be: predicting and processing the second repair strategy information according to a learning model or a prediction algorithm to obtain an output result, and the output result indicates whether the repair strategy represented by the second repair strategy information belongs to the excessive repair type. Among them, the over-maintenance type indicates that the maintenance strategy represented by the second maintenance strategy information has unreasonable over-maintenance items. For example, the fault can be repaired only by replacing component A, while the maintenance strategy represented by the second maintenance strategy information indicates that component A and component B need to be replaced. At this time, the maintenance strategy belongs to the over-maintenance type; in the case that the maintenance strategy represented by the second maintenance strategy information belongs to the over-maintenance type, it means that the current maintenance strategy is unreasonable. At this time, another maintenance shop in the maintenance shop subset can be extracted as the updated target maintenance shop, and the steps in this embodiment are performed again on the updated target maintenance shop until the maintenance strategy of the target maintenance shop does not belong to the over-maintenance type; in the second dimension When the maintenance strategy represented by the maintenance strategy information does not belong to the excessive maintenance type, it means that the current maintenance strategy is reasonable. At this time, the reasonable maintenance information can be output to solve the problem of abnormal charges, excessive maintenance, etc. when the user repairs the vehicle failure in the repair shop, resulting in excessive maintenance costs for the user. It should be noted that the excessive maintenance type in this embodiment is only an example. In specific implementation, it can also be one or more unreasonable types such as excessive charging type and excessive maintenance cycle type. The specific judgment process can be similar to the above and will not be repeated here. In this way, the effect of updating the target repair shop can be achieved when the maintenance strategy determined by the target repair shop based on the vehicle fault information is unreasonable.

[0118] like Figure 4 As shown, the present application also discloses an embodiment, providing a device for pushing repair shop information, the device comprising:

[0119] A first acquisition module 410 is used to acquire vehicle fault information, where the vehicle fault information indicates a fault of a target vehicle;

[0120] A first determination module 420, for determining a vehicle position of a target vehicle;

[0121] A second determination module 430 is used to determine a repair shop whose distance to the vehicle location is less than or equal to a preset distance threshold, and obtain a repair shop set;

[0122] A third determination module 440 is used to determine the fault type of the target vehicle based on the vehicle fault information;

[0123] The target module 450 is used to determine a target repair shop from the repair shop set to push target repair shop information of the target repair shop, wherein the type of the target repair shop matches the fault type.

[0124] In one embodiment, the first determining module 420 may include:

[0125] A first determination unit is used to determine a maintenance type of the target vehicle based on the vehicle fault information, where the maintenance type indicates whether the fault of the target vehicle requires maintenance at a repair shop;

[0126] An output unit, configured to output self-repair information when the repair type indicates that the fault of the target vehicle does not require repair by a repair shop;

[0127] The second determining unit is configured to determine the vehicle position of the target vehicle when the maintenance type indicates that the failure of the target vehicle needs to be repaired by a maintenance shop.

[0128] In one embodiment, the first determining unit may include:

[0129] A judgment subunit, used to compare the vehicle fault information with the fault case information in the fault case information set to determine whether there is fault case information matching the vehicle fault information;

[0130] A first determination subunit is used to determine that the repair type indicates that repair at a repair shop is required when there is no fault case information matching the vehicle fault information in the fault case information set;

[0131] The second determination subunit is used to determine the fault case information matching the vehicle fault information as target fault case information when there is fault case information matching the vehicle fault information in the fault case information set, and to determine the maintenance type of the target vehicle based on the target fault case information.

[0132] In one embodiment, the second determining subunit may include:

[0133] A third determining subunit is used to determine first maintenance strategy information based on the target fault case information, where the first maintenance strategy information represents a strategy for maintaining the target vehicle;

[0134] A first acquisition subunit is used to acquire first input information, where the first information represents instruction information input based on the first maintenance strategy information whether maintenance at a maintenance shop is required;

[0135] The fourth determining subunit is used to determine the maintenance type of the target vehicle based on the first input information.

[0136] In one embodiment, the repair shop set includes a repair shop type, and,

[0137] The target module 450 may include:

[0138] A third determining unit is used to determine whether there is a repair shop in the repair shop set whose repair shop type matches the fault type based on a preset corresponding relationship table, wherein the preset corresponding relationship table indicates a matching relationship between the repair shop type and the fault type;

[0139] The fourth determining unit is configured to determine the repair shop whose repair shop type matches the fault type as a target repair shop when there is a repair shop whose repair shop type matches the fault type in the repair shop set.

[0140] In one embodiment, the fourth determining unit may include:

[0141] In the case that there are repair shops whose repair shop types match the fault types in the repair shop set, determining the set of repair shops whose repair shop types match the fault types as a repair shop subset;

[0142] A fifth determining subunit is used to determine a repair success rate of each repair shop in the repair shop subset, where the repair success rate represents a success rate of the repair shop repairing the fault;

[0143] The sixth determining subunit is used to determine the repair shop with the highest repair success rate as the target repair shop.

[0144] In one embodiment, the method further comprises:

[0145] A second acquisition module is used to acquire second maintenance strategy information, where the second maintenance strategy information represents a maintenance strategy determined by a target maintenance shop based on vehicle fault information;

[0146] The extraction module is used to extract another repair shop in the repair shop subset as an updated target repair shop when the repair strategy indicated by the second repair strategy information belongs to the over-repair type.

[0147] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.

[0148] like Figure 5 As shown, an embodiment of the present application provides an electronic device, including a processor 510, a communication interface 520, a memory 530 and a communication bus 540, wherein the processor 510, the communication interface 520, and the memory 530 communicate with each other through the communication bus 540, and the memory 530 is used to store computer programs;

[0149] In one embodiment of the present application, the processor 510 is used to implement the method provided by any one of the aforementioned method embodiments when executing the program stored in the memory 530.

[0150] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method provided in any of the aforementioned method embodiments are implemented.

[0151] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0152] The above describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0153] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for pushing repair shop information, characterized in that: The method comprises: Acquiring vehicle fault information, wherein the vehicle fault information indicates a fault of a target vehicle; determining a vehicle position of the target vehicle; Determine a repair shop whose distance from the vehicle location is less than or equal to a preset distance threshold, and obtain a repair shop set; Based on the vehicle fault information, determining the fault type of the target vehicle; A target repair shop is determined from the repair shop set to push target repair shop information of the target repair shop, wherein a type of the target repair shop matches the fault type.

2. The method according to claim 1, characterized in that The determining the vehicle position of the target vehicle comprises: Based on the vehicle fault information, determining a maintenance type of the target vehicle, the maintenance type indicating whether the fault of the target vehicle requires maintenance at a repair shop; When the maintenance type indicates that the fault of the target vehicle does not require maintenance at a maintenance shop, outputting self-repair information; In a case where the repair type indicates that the failure of the target vehicle requires repair by a repair shop, a vehicle position of the target vehicle is determined.

3. The method according to claim 2, characterized in that The determining, based on the vehicle fault information, a maintenance type of the target vehicle includes: Comparing the vehicle fault information with the fault case information in the fault case information set to determine whether there is fault case information matching the vehicle fault information; In the case where there is no fault case information matching the vehicle fault information in the fault case information set, determining that the repair type indicates that repair at a repair shop is required; When there is fault case information matching the vehicle fault information in the fault case information set, the fault case information matching the vehicle fault information is determined as target fault case information, and based on the target fault case information, the maintenance type of the target vehicle is determined.

4. The method according to claim 3, characterized in that The determining, based on the target fault case information, a maintenance type of the target vehicle includes: Based on the target fault case information, determining first maintenance strategy information, wherein the first maintenance strategy information indicates a strategy for maintaining the target vehicle; Acquire first input information, where the first information represents instruction information of whether maintenance at a maintenance shop is required, which is input based on the first maintenance strategy information; A maintenance type of the target vehicle is determined based on the first input information.

5. The method according to claim 1, characterized in that The step of determining a target repair shop from the set of repair shops includes: Based on a preset correspondence table, determining whether there is a repair shop in the repair shop set whose repair shop type matches the fault type, wherein the preset correspondence table indicates a matching relationship between the repair shop type and the fault type; In the case that there is a repair shop whose repair shop type matches the fault type in the repair shop set, the repair shop whose repair shop type matches the fault type is determined as a target repair shop.

6. The method according to claim 5, characterized in that In the case that there is a repair shop whose repair shop type matches the fault type in the repair shop set, determining the repair shop whose repair shop type matches the fault type as a target repair shop includes: In the case that there are repair shops whose repair shop types match the fault type in the repair shop set, determining the set of repair shops whose repair shop types match the fault type as a repair shop subset; Determine a repair success rate of each repair shop in the repair shop subset, wherein the repair success rate represents a success rate of the repair shop in repairing the fault; The repair shop with the highest repair success rate is determined as the target repair shop.

7. The method according to claim 6, characterized in that The method further comprises: Acquiring second maintenance strategy information, where the second maintenance strategy information indicates a maintenance strategy determined by the target maintenance shop based on the vehicle fault information; In a case where the maintenance strategy indicated by the second maintenance strategy information belongs to an excessive maintenance type, another maintenance shop in the maintenance shop subset is extracted as an updated target maintenance shop.

8. A device for pushing repair shop information, characterized in that: The device comprises: A first acquisition module, used to acquire vehicle fault information, wherein the vehicle fault information indicates a fault of a target vehicle; A first determination module, used to determine the vehicle position of the target vehicle; A second determination module is used to determine a repair shop whose distance from the vehicle position is less than or equal to a preset distance threshold, and obtain a repair shop set; A third determination module, configured to determine a fault type of the target vehicle based on the vehicle fault information; The target module is used to determine a target repair shop from the repair shop set to push target repair shop information of the target repair shop, wherein the type of the target repair shop matches the fault type.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing the method according to any one of claims 1 to 7 when executing a program stored in a memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images