Vehicle fault reminder method, reminder platform, terminal device and readable storage medium

Abstract

An embodiment of the present application provides a vehicle fault reminder method, a reminder platform, a terminal device and a readable storage medium, the method comprising: obtaining a fault code of a target vehicle; determining, based on the fault code, target repair cost information corresponding to repairing the target vehicle within at least two different preset time periods; outputting the target repair cost information to a user of the target vehicle, thereby prompting the user with information related to the vehicle fault in an intuitive manner, allowing the user to choose a suitable time to repair the vehicle, which is conducive to controlling the economic and safety issues that may be caused by a vehicle fault, better meeting the actual needs of the user, improving the user experience, and enhancing user stickiness.

Description

Technical Field

[0001] The present application belongs to the field of vehicle maintenance technology, and in particular relates to a vehicle fault reminder method, a reminder platform, a terminal device and a readable storage medium. Background Art

[0002] The vehicle fault code (hereinafter referred to as fault code) is a code reflected by the vehicle computer (Electronic Control Unit, ECU) after the vehicle fails. By interpreting the fault code, the possible cause and location of the fault can be correctly identified. Since the fault code is a professional code, it is difficult for ordinary users to understand the meaning of the vehicle fault corresponding to the fault code, and they are even less able to know the economic and safety problems that may be caused by the vehicle failure.

[0003] Therefore, the method for providing information related to vehicle faults in the prior art cannot meet the actual needs of users. Summary of the invention

[0004] The embodiments of the present application provide a vehicle fault reminder method, reminder platform, terminal device and readable storage medium, which can intuitively prompt the user with information related to the vehicle fault, thereby reducing the impact on personal health and property losses that may be caused by the vehicle fault.

[0005] In a first aspect, an embodiment of the present application provides a vehicle fault reminder method, comprising:

[0006] Get the fault code of the target vehicle;

[0007] Determining target repair cost information corresponding to repair of the target vehicle within at least two different preset time periods according to the fault code;

[0008] The target repair cost information is output to a user of the target vehicle.

[0009] Optionally, determining target repair cost information corresponding to repair of the target vehicle within at least two different preset time periods according to the fault code includes:

[0010] Determining, based on the fault code, an associated code corresponding to maintenance of the target vehicle within at least two different preset time periods;

[0011] Obtaining first maintenance cost information corresponding to maintenance performed on the fault code within at least two different preset time periods, and obtaining second maintenance cost information corresponding to maintenance performed on the association code within at least two different preset time periods;

[0012] Target maintenance cost information is determined according to the first maintenance cost information and the second maintenance cost information.

[0013] Optionally, the target maintenance cost information includes at least one of maintenance cost, maintenance time, life data of the faulty component and life data of the vehicle.

[0014] Optionally, after the step of obtaining the fault code of the target vehicle, the following steps are further included:

[0015] Determine the corresponding precautions based on the fault code;

[0016] Output the notes to the user;

[0017] The precautions include at least one of a dangerous driving environment, a latest maintenance time, a maximum driving distance, and a scrapping reminder.

[0018] Optionally, outputting the target maintenance cost information to the user of the target vehicle includes:

[0019] The target maintenance cost information is visualized and output to the user of the target vehicle.

[0020] Optionally, the target maintenance cost information is visualized and output to the user of the target vehicle, including:

[0021] The target maintenance cost information is output to the user in the form of a chart.

[0022] Optionally, after obtaining the fault code of the target vehicle, the following is also included:

[0023] Determine whether the fault code belongs to the preset serious fault code;

[0024] If so, executing the steps of determining target repair cost information corresponding to repair of the target vehicle within at least two different preset time periods according to the fault code and the following steps;

[0025] If not, the steps of determining target repair cost information corresponding to repairing the target vehicle within at least two different preset time periods according to the fault code and subsequent steps are not performed.

[0026] In a second aspect, an embodiment of the present application provides a vehicle fault reminder platform, including:

[0027] An acquisition module, used to acquire the fault code of the target vehicle;

[0028] A target repair cost information determination module, used to determine target repair cost information corresponding to repair of a target vehicle within at least two different preset time periods according to the fault code;

[0029] The output module is used to output the target maintenance cost information to the user of the target vehicle.

[0030] Optionally, the target maintenance cost information determination module further includes:

[0031] Determining, based on the fault code, an associated code corresponding to maintenance of the target vehicle within at least two different preset time periods;

[0032] Obtaining first maintenance cost information corresponding to maintenance performed on the fault code within at least two different preset time periods, and obtaining second maintenance cost information corresponding to maintenance performed on the association code within at least two different preset time periods;

[0033] Target maintenance cost information is determined according to the first maintenance cost information and the second maintenance cost information.

[0034] The target maintenance cost information includes at least one of maintenance cost, maintenance time, life data of the faulty component, and life data of the vehicle.

[0035] Optionally, the vehicle fault reminder platform also includes a precaution module, which is used to determine corresponding precautions based on the fault code; and output the precautions to the user; wherein the precautions include at least one of a dangerous driving environment, a latest maintenance time, a longest driving distance, and a scrapping reminder.

[0036] Optionally, the output module is further used to visualize the target maintenance cost information and output it to the user of the target vehicle, for example, output the target maintenance cost information to the user in the form of a chart.

[0037] Optionally, the vehicle fault reminder platform also includes a judgment module for determining whether the fault code belongs to a preset serious fault code; if so, executing the target repair cost information corresponding to the target vehicle being repaired within at least two different preset time periods based on the fault code and subsequent steps; if not, not executing the target repair cost information corresponding to the target vehicle being repaired within at least two different preset time periods based on the fault code.

[0038] In a third aspect, an embodiment of the present application provides a terminal device, a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the vehicle fault reminder method of any one of the above-mentioned first aspects is implemented.

[0039] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and is characterized in that when the computer program is executed by a processor, it implements the vehicle fault reminder method of any one of the above-mentioned first aspects.

[0040] In a fifth aspect, an embodiment of the present application provides a computer program product. When the computer program product is run on a terminal device, the terminal device executes the vehicle fault reminder method of any one of the above-mentioned first aspects.

[0041] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0042] The embodiment of the present application obtains the fault code of the target vehicle; determines the target repair cost information corresponding to the repair of the target vehicle within at least two different preset time periods based on the fault code; and outputs the target repair cost information to the user of the target vehicle, thereby prompting the user with information related to the vehicle fault in an intuitive manner, allowing the user to choose an appropriate time to repair the vehicle, which is conducive to controlling the economic and safety problems that may be caused by the vehicle failure, better meeting the actual needs of the user, improving the user experience, and enhancing user stickiness.

[0043] It can be understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0045] Figure 1 is a schematic block diagram of the architecture of the system provided by the first embodiment of the present application;

[0046] Figure 2 is a flow chart of a vehicle fault reminder method provided in the second embodiment of the present application;

[0047] Figure 3 is a flow chart of a vehicle fault reminder method provided in the fourth embodiment of the present application;

[0048] Figure 4 is a flowchart of a vehicle fault reminder method provided in the fifth embodiment of the present application;

[0049] Figure 5a This is a schematic diagram of the time period-maintenance cost effect of the vehicle fault reminder method provided in the fifth embodiment of the present application;

[0050] Figure 5b This is a schematic diagram of the time period-maintenance duration effect of the vehicle fault reminder method provided in the fifth embodiment of the present application;

[0051] Figure 6 is a flow chart of a vehicle fault reminder method provided in a sixth embodiment of the present application;

[0052] Figure 7 is a flow chart of a vehicle fault reminder method provided in the seventh embodiment of the present application;

[0053] Figure 8 is a structural diagram of a vehicle fault reminder platform provided in the eighth embodiment of the present application;

[0054] Fig. 9 It is a structural diagram of the terminal device provided in the ninth embodiment of the present application. DETAILED DESCRIPTION

[0055] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0056] The technical solution provided in the embodiments of the present application is described in detail below.

[0057] Embodiment 1

[0058] See also Figure 1 The system architecture schematic block diagram of the first embodiment of the present application for providing a vehicle fault reminder service to a user is shown, and the system may include a vehicle fault reminder platform 11 and at least one user terminal 12. As an example and not a limitation, Figure 1 The user terminal 12 is a mobile phone. In some other cases, the user terminal 12 may also include various terminal devices such as mobile phones, tablet computers, personal digital assistants (PDAs), mobile Internet devices (MIDs), smart wearable devices (such as smart watches and smart bracelets), and vehicles, which are not limited in the embodiments of the present application.

[0059] A corresponding application may be installed on the user terminal 12, and the user may obtain the vehicle fault reminder service provided by the system through the application. At the same time, through the application, users may also share maintenance techniques in the forum or answer questions in the community. Of course, the vehicle fault reminder service provided by the system may also be presented through a public account (e.g., a WeChat public account) or a mini program (e.g., a WeChat mini program). In other words, if the user needs the vehicle fault reminder service provided by the embodiment of the present application, the vehicle fault reminder platform 11 provided by the embodiment of the present application may be accessed through a corresponding application, a public account or a mini program.

[0060] Embodiment 2

[0061] See also Figure 2A flow chart of a vehicle fault reminder method provided in the second embodiment of the present application is shown. The method provided in the embodiment of the present application can be specifically described in conjunction with steps S201 to S203.

[0062] Step 201: Obtain the fault code of the target vehicle.

[0063] When a user's vehicle breaks down, the fault code corresponding to the fault can be determined through fault detection. In the embodiment of the present application, the vehicle in which the fault occurs is referred to as the target vehicle. The fault detection can be performed through third-party software or equipment, or a corresponding application, official account or mini-program installed on the user terminal 12. The fault code is used to indicate a vehicle fault, and the specific meaning of each fault code can be queried through the manual, etc. For example, P0101 means: the passenger air flow meter circuit is bad, P0102 means: the passenger air flow meter circuit input voltage is too low, etc.

[0064] Step 202: Determine target repair cost information corresponding to repair of the target vehicle within at least two different preset time periods according to the fault code.

[0065] When different vehicle failures correspond to different fault codes, different fault codes may cause different economic and safety issues. Furthermore, even for the same fault code, if the user performs repairs in different preset time periods, the economic and safety issues that may be caused are also different. For example, if the user performs repairs immediately after the vehicle fails, the economic cost is relatively low. If the user postpones repairs after the vehicle fails, the impact of the failure may be aggravated, the repair cost may be increased, and even other failures may occur in the vehicle due to delay in repairs, and the economic cost of repairs will inevitably increase. The target repair cost information is used to describe the cost information corresponding to the repair of the target vehicle in at least two different preset time periods, and can be used to reflect the economic and safety issues corresponding to repairs in at least two different preset time periods. Therefore, the target repair cost information corresponding to the fault code in different preset time periods is also different.

[0066] The preset time period is used to indicate the time for the user to perform maintenance after the vehicle fails. For example, if the user performs maintenance within 1 day or within 3 days, 1 day or 3 days is the time period, which can be abbreviated as 1 day or 3 days. Different fault codes may correspond to different preset time periods.

[0067] Step 203: Output the target maintenance cost information to the user of the target vehicle, for example, send it to the user terminal through a network, or display it on the user terminal.

[0068] The embodiment of the present application determines the target repair cost information corresponding to the repair of the target vehicle within at least two different preset time periods according to the fault code, and outputs the target repair cost information to the user, so that the user can intuitively understand the information related to the vehicle fault and the possible economic and safety problems, allowing the user to choose the appropriate time to repair the vehicle, thereby achieving the purpose of making the user pay attention to the vehicle fault and deal with the vehicle fault as soon as possible, while better meeting the actual needs of the user, improving the user experience, and enhancing user stickiness.

[0069] Embodiment 3

[0070] As an embodiment of the present invention, the following steps may also be included before step 202:

[0071] Collect data related to the fault code in advance, and then integrate and store the repair cost information of the fault code in different time periods based on the collected data.

[0072] In order to determine which different target maintenance cost information should correspond to different fault codes when they are repaired in different preset time periods, multiple fault code-related data can be collected in advance. These data can be various data materials related to the cost information corresponding to the maintenance of the fault codes in different preset time periods. For example, it can be the maintenance technical data shared by maintenance technicians in the forum in the application, official account or mini-program installed on the aforementioned user terminal 12, or the answer data in the community question answering column, or the vehicle fault handling related data obtained on the Internet using big data technology.

[0073] Through these data, the maintenance cost information required for maintenance and processing of each fault code in different time periods is integrated. For example, the processing fee for the fault code "P1805" within 1 day is 800 yuan, and the processing fee for the fault code "P1805" within 3 days is 1500 yuan, the processing fee for the fault code "P1805" within 3 to 6 days is 2800 yuan, and the processing fee for the fault code "P1805" within 6 days or more is 5300 yuan. Among them, the maintenance cost information includes at least one of: maintenance cost, maintenance time, life data of the faulty component and vehicle life data. Among them, the maintenance cost is used to indicate the cost to be paid for maintenance processing, the maintenance time is used to indicate the time spent on maintenance processing, the life data of the faulty component is used to indicate the impact of the vehicle failure on the life of the faulty component, and the life data of the vehicle is used to indicate the impact of the vehicle failure on the life of the vehicle.

[0074] Similarly, the maintenance time, life data of the faulty parts and life data of the vehicle corresponding to maintenance processing in different time periods after a vehicle failure may also be different.

[0075] In some embodiments, the integration of the above data includes deduplication, deletion of unreasonable data or merging of data, etc., so as to generate target maintenance cost information corresponding to the fault code for maintenance in different preset time periods. For example, the forum post of maintenance technician Xiao Zhang describes the corresponding relationship between the maintenance costs for the fault code "P1805" and the maintenance costs for maintenance in different preset time periods for the fault, and the maintenance technician Xiao Wang involves the corresponding relationship between the maintenance costs for the fault code "P1805" and the maintenance costs for maintenance in different preset time periods in the community question answering column, but the maintenance cost data provided by Xiao Zhang and Xiao Wang are not exactly the same. For example, data A means that the processing fee for the fault code "P1805" within 1 day is 1,000 yuan, data B means that the processing fee for the fault code "P1805" within 1 day is 800 yuan, data C means that the processing fee for the fault code "P1805" within 1 day is 600 yuan, and data D means that the processing fee for the fault code "P1805" within 1 day is 10,000 yuan. Then, when integrating, you can first delete the unreasonable data D, and then calculate the average value of data A, B and C (1,000+800+600) / 3=800 yuan, and use the average value 800 as the corresponding repair cost for the fault code "P1805" within 1 day.

[0076] The embodiment of the present application predetermines and stores target repair cost information for target vehicles corresponding to different faults within at least two different preset time periods, and directly queries the stored correspondence according to the fault code when the user needs it, thereby determining the target repair cost information, thereby improving the timeliness of feedback.

[0077] Embodiment 4

[0078] See also Figure 3 A flow chart of a vehicle fault reminder method provided by the fourth embodiment of the present application is shown, and the method may include the following steps:

[0079] Step 301: Obtain the fault code of the target vehicle.

[0080] Step 302: Determine, based on the fault code, an associated code corresponding to maintenance of the target vehicle within at least two different preset time periods.

[0081] After a vehicle failure, if the user delays repairs, the vehicle may further cause other failures. In the embodiment of the present application, the vehicle failure that occurred first is referred to as the first failure, and other failures that may be caused are referred to as associated failures. The fault code corresponding to the associated failure is referred to as the associated code. Usually, the first failure is different from the associated failure. For example, the fault code of the first failure is "P1805", and the associated failures that may be caused by the first failure may include "P2008" vortex control valve and "P2103" electronic throttle control motor power supply-B1, etc., where "P2008" and "P2103" are the associated codes of the associated failures.

[0082] Determine the associated code corresponding to the target vehicle being repaired within at least two different preset time periods based on the fault code, including: determining the associated faults of the vehicle that may be caused by the first fault through an application, public account or mini-program installed by a third-party system or the user terminal 12, and obtaining the corresponding associated code.

[0083] Step 303: Obtain first maintenance cost information corresponding to maintenance performed on the fault code within at least two different preset time periods, and obtain second maintenance cost information corresponding to maintenance performed on the association code within at least two different preset time periods.

[0084] As mentioned above, for the same fault code, if the user performs repairs in different preset time periods, the economic and safety issues that may be caused are also different, and therefore the associated faults may also be different. The first repair cost information is used to describe the cost information corresponding to the repair of the first fault in at least two different preset time periods, and the second repair cost information is used to describe the cost information corresponding to the repair of the associated fault in at least two different preset time periods. The first repair cost information and the second repair cost information are different when they correspond to repairs in different preset time periods. For example, if the vehicle is difficult to shift into gear during the gear shifting process, it is mostly because the gearbox gear is damaged. The price of replacing the gearbox gear will not exceed one thousand. If the gearbox is scrapped due to failure to repair in time, the price of replacing the entire gearbox will exceed ten thousand yuan.

[0085] Step 304: Determine target maintenance cost information according to the first maintenance cost information and the second maintenance cost information.

[0086] When the first fault will not cause associated faults, there is no second maintenance cost information; when the first fault may cause associated faults, it is necessary to comprehensively determine the target maintenance cost information based on the first maintenance cost information and the second maintenance cost information. For example, "P1805", the first maintenance cost information corresponding to the first fault includes that the maintenance time corresponding to maintenance in 1 day and 3 days is 1 day and 3 days, the second maintenance cost information corresponding to the associated codes "P2008" and "P2103" includes that the maintenance time corresponding to maintenance in 1 day and 3 days is 2 days and 4 days, and the target maintenance cost information includes that the maintenance time corresponding to maintenance in 1 day and 3 days is 1+2=3 days and 3+4=7 days. It can be understood that the summation process is only an example.

[0087] Step 305: Output the target maintenance cost information to the user of the target vehicle.

[0088] The principles and implementation details of the above steps S301 and S305 are the same as those of steps S201 and S203 in the second embodiment. The specific implementation process can refer to the description of steps S201 and S203, which will not be repeated here.

[0089] The embodiment of the present application obtains first repair cost information corresponding to repairs performed on a fault code within at least two different preset time periods, and obtains second repair cost information corresponding to repairs performed on an associated code within at least two different preset time periods, and determines target repair cost information based on the first repair cost information and the second repair cost information, which is then output to the user, thereby providing the user with more complete vehicle fault information, allowing the user to choose an appropriate time to repair the vehicle, thereby helping to reduce economic and safety issues that may be caused by vehicle faults.

[0090] Embodiment 5

[0091] See also Figure 4 A flowchart of a vehicle fault reminder method provided by the fifth embodiment of the present application is shown, and the method may include the following steps:

[0092] Step 401: Obtain the fault code of the target vehicle.

[0093] Step 402: Determine target repair cost information corresponding to repair of the target vehicle within at least two different preset time periods according to the fault code.

[0094] Step 403: Visualizing the target maintenance cost information and then inputting it to the user, specifically including:

[0095] Visualization processing includes allowing the use of graphics, image processing, computer vision and user interface to visually interpret the target maintenance cost information through expression, modeling and display of solids, surfaces, attributes and animations, so as to output the target maintenance cost information to the user clearly and effectively through graphical means.

[0096] Optionally, convert the target maintenance cost information into a chart, such as a bubble chart, pie chart, bar chart, or line chart, such as Figure 5a The schematic diagram of the time period-maintenance cost effect of the vehicle fault reminder method in one embodiment of the present application is shown, Figure 5a The horizontal axis represents the time period, and the vertical axis represents the corresponding maintenance cost, which intuitively displays the corresponding relationship between time period and maintenance cost to the user; Figure 5b The schematic diagram of the time period-maintenance duration effect of the vehicle fault reminder method in one embodiment of the present application is shown, Figure 5b The horizontal axis represents the time period, and the vertical axis represents the corresponding maintenance duration, intuitively displaying the correspondence between time period and maintenance duration to the user.

[0097] The principles and implementation details of the above steps S401 and S402 are the same as those of steps S201 and S202 in the second embodiment. The specific implementation process can refer to the description of steps S201 and S202, which will not be repeated here.

[0098] The embodiment of the present application visualizes the target repair cost information and outputs it to the user, thereby intuitively displaying vehicle fault-related information to the user, which can attract the user's attention and handle the fault as soon as possible to reduce losses, allowing the user to choose an appropriate time to repair the vehicle, thereby improving the user's experience.

[0099] Embodiment 6

[0100] See also Figure 6 A flow chart of a vehicle fault reminder method provided by the sixth embodiment of the present application is shown, and the method may include the following steps:

[0101] Step 601: Obtain the fault code of the target vehicle.

[0102] Step 602: Determine target repair cost information corresponding to repair of the target vehicle within at least two different preset time periods according to the fault code.

[0103] Step 603: Output the target maintenance cost information to the user of the target vehicle.

[0104] Step 604: Determine corresponding precautions according to the fault code, and output the precautions to the user.

[0105] Precautions are used to remind users of what they need to pay attention to after a vehicle failure occurs. For example, precautions include at least one of dangerous driving environments, the latest repair time, the longest driving distance, and scrapping reminders. Precautions are used to help users avoid dangerous driving environments, such as unsuitable driving conditions such as rainy days or cold weather, not to miss the latest repair time, not to drive long distances, or if the vehicle is not followed, it may be directly scrapped.

[0106] Among them, the principles and implementation details of the above steps S601, S602 and S603 are the same as those of steps S201, S202, and S203 in Example 2. The specific implementation process can be found in the description of steps S201, S202, and S203, and will not be repeated here.

[0107] The embodiment of the present application not only outputs the target repair cost information to the user of the target vehicle, but also determines the corresponding precautions based on the fault code and outputs the precautions to the user, thereby providing the user with more complete vehicle fault information, allowing the user to choose an appropriate time to repair the vehicle, thereby helping to reduce the economic and safety problems that may be caused by vehicle failures.

[0108] Embodiment 7

[0109] See also Figure 7 A schematic flow chart of a vehicle fault reminder method provided by the seventh embodiment of the present application is shown, and the method may include the following steps:

[0110] Step 701: Obtain the fault code of the target vehicle.

[0111] Step 702: Determine whether the fault code is a preset serious fault code, if so, execute step 703.

[0112] In order to save system resources, a preset serious fault code that needs to be processed can be pre-set. If the acquired fault code belongs to the preset serious fault code, the subsequent step 703 is performed. If it does not belong to the preset serious fault code, it is processed according to the conventional method in the prior art. This application does not make specific limitations on this.

[0113] Step 703: Determine target repair cost information corresponding to repair of the target vehicle within at least two different preset time periods according to the fault code.

[0114] Step 704: Output the target maintenance cost information to the user of the target vehicle.

[0115] Among them, the principles and implementation details of the above steps S701, S703 and S704 are the same as those of steps S201, S202, and S203 in Example 2. The specific implementation process can be found in the description of steps S201, S202, and S203, and will not be repeated here.

[0116] The embodiment of the present application determines whether the fault code is a preset serious fault code after receiving it. If so, it executes the step of determining the target repair cost information corresponding to the repair of the target vehicle within at least two different preset time periods based on the fault code, thereby more effectively utilizing resources, reducing unnecessary waste of resources, and improving the overall efficiency of the system.

[0117] It should be noted that other sorting schemes that can be easily thought of by those skilled in the art within the technical scope disclosed in the present invention should also be within the protection scope of the present invention and will not be described in detail here.

[0118] Embodiment 8

[0119] See also Figure 8 , is a schematic diagram of a vehicle fault reminder platform provided in the eighth embodiment of the present application. For the sake of convenience, only the parts related to the embodiment of the present invention are shown, including:

[0120] The acquisition module 801 is used to acquire the fault code of the target vehicle;

[0121] The target maintenance cost information determination module 802 is used to determine the target maintenance cost information corresponding to the maintenance of the target vehicle within at least two different preset time periods according to the fault code;

[0122] The output module 803 is used to output the target maintenance cost information to the user of the target vehicle.

[0123] The target maintenance cost information determination module 802 further includes:

[0124] Determining, based on the fault code, an associated code corresponding to maintenance of the target vehicle within at least two different preset time periods;

[0125] Obtaining first maintenance cost information corresponding to maintenance performed on the fault code within at least two different preset time periods, and obtaining second maintenance cost information corresponding to maintenance performed on the association code within at least two different preset time periods;

[0126] Target maintenance cost information is determined according to the first maintenance cost information and the second maintenance cost information.

[0127] The target maintenance cost information includes at least one of maintenance cost, maintenance time, life data of the faulty component, and life data of the vehicle.

[0128] Optionally, the vehicle fault reminder platform provided in the embodiment of the present application also includes a precaution module, which is used to determine corresponding precautions based on the fault code; and output the precautions to the user; wherein the precautions include at least one of a dangerous driving environment, a latest maintenance time, a longest driving distance and a scrapping reminder.

[0129] The output module 803 is further used to visualize the target maintenance cost information and output it to the user of the target vehicle, for example, output the target maintenance cost information to the user in the form of a chart.

[0130] Optionally, the vehicle fault reminder platform provided in the embodiment of the present application also includes a judgment module for judging whether the fault code belongs to a preset serious fault code; if so, executing the target repair cost information corresponding to the target vehicle being repaired within at least two different preset time periods based on the fault code and subsequent steps; if not, not executing the target repair cost information corresponding to the target vehicle being repaired within at least two different preset time periods based on the fault code.

[0131] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example for illustration. In actual applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the mobile terminal can be divided into different functional units or modules to complete all or part of the functions described above. The functional modules in the embodiment can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the modules in the above-mentioned mobile terminal can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0132] Embodiment 9

[0133] Fig. 9 Schematic diagram of a terminal device provided by the ninth embodiment of the present invention. Fig. 9 As shown, the terminal device 9 of this embodiment includes: a processor 90, a memory 91, and a computer program 92 stored in the memory 91 and executable on the processor 90. When the processor 90 executes the computer program 92, the steps of the vehicle fault reminder method described above are implemented, for example Figure 2 Alternatively, when the processor 90 executes the computer program 92, the functions of each module / unit in the above-mentioned device embodiments are implemented, for example Figure 8 Functions of modules 801 to 803 are shown.

[0134] Exemplarily, the computer program 92 may be divided into one or more modules / units, one or more modules / units are stored in the memory 91, and are executed by the processor 90 to implement the present invention. One or more modules / units may be a series of computer program instruction segments capable of implementing specific functions, and the instruction segments are used to describe the execution process of the computer program 92 in the terminal device 9.

[0135] The terminal device 9 may be a computing device such as a desktop computer, a notebook, a palm computer, etc. The terminal device may include, but is not limited to, a processor 90 and a memory 91. Those skilled in the art will understand that Fig. 9 It is only an example of the terminal device 9 and does not constitute a limitation on the terminal device 9. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the terminal device may also include input and output devices, network access devices, buses, etc.

[0136] The processor 90 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0137] The memory 91 may be an internal storage unit of the terminal device 9, such as a hard disk or memory of the terminal device 9. The memory 91 may also be an external storage device of the terminal device 9, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal device 9. Further, the memory 91 may also include both an internal storage unit of the terminal device 9 and an external storage device. The memory 91 is used to store computer programs and other programs and data required by the terminal device. The memory 91 may also be used to temporarily store data that has been output or is to be output.

[0138] The embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0139] An embodiment of the present application provides a computer program product. When the computer program product runs on a mobile terminal, the mobile terminal can implement the steps in the above-mentioned method embodiments when executing the computer program product.

[0140] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0141] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0142] As used in the specification of this application and the appended claims, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting" depending on the context. Similarly, the phrase "if it is determined" or "if the described condition or event is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce the described condition or event is detected" or "in response to detecting the described condition or event" depending on the context.

[0143] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0144] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0145] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0146] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0147] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0148] In the embodiments provided by the present invention, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0150] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0151] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electric carrier signals and telecommunication signals.

[0152] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the protection scope of the present invention.

Claims

1. A vehicle fault reminder method, characterized in that: include: Get the fault code of the target vehicle; Collect data related to the fault code in advance, and then integrate and store the repair cost information of the fault code in different time periods according to the collected data; wherein the integration of the data includes deduplication, deletion of unreasonable data or merging of data; Determining target repair cost information corresponding to repairing the target vehicle within at least two different preset time periods according to the fault code includes: Determine, according to the fault code, an associated code corresponding to the target vehicle being repaired within at least two different preset time periods; wherein the preset time period is used to indicate the time for the user to perform repair processing after the vehicle fails; different fault codes correspond to different preset time periods; Obtaining first maintenance cost information corresponding to maintenance of the fault code within at least two different preset time periods, and obtaining second maintenance cost information corresponding to maintenance of the associated code within at least two different preset time periods; wherein the vehicle fault that occurred previously is referred to as the first fault, other faults that may be caused are referred to as associated faults, and the fault code corresponding to the associated fault is referred to as the associated code; the first maintenance cost information is used to describe the cost information corresponding to maintenance of the first fault within at least two different preset time periods, and the second maintenance cost information is used to describe the cost information corresponding to maintenance of the associated fault within at least two different preset time periods; Determine the target maintenance cost information according to the first maintenance cost information and the second maintenance cost information; The target maintenance cost information is used to describe the cost information corresponding to the maintenance of the target vehicle within at least two different preset time periods, and is used to reflect the economic and safety issues corresponding to the maintenance within at least two different preset time periods; the target maintenance cost information includes at least one of: maintenance cost, maintenance time, life data of the faulty component, and life data of the vehicle; The target maintenance cost information is output to a user of the target vehicle.

2. The vehicle fault reminder method according to claim 1, characterized in that: After the step of obtaining the fault code of the target vehicle, the method further includes: Determine corresponding precautions according to the fault code; Outputting the precautions to the user; The precautions include at least one of a dangerous driving environment, a latest maintenance time, a maximum driving distance and a scrapping reminder.

3. The vehicle fault reminder method according to claim 1, characterized in that: The step of outputting the target maintenance cost information to a user of the target vehicle includes: The target maintenance cost information is visualized and then output to a user of the target vehicle.

4. The vehicle fault reminder method according to claim 3, characterized in that: The step of visually processing the target maintenance cost information and outputting it to the user of the target vehicle includes: The target maintenance cost information is output to the user in the form of a chart.

5. The vehicle fault reminder method according to claim 1, characterized in that: After obtaining the fault code of the target vehicle, the method further includes: Determining whether the fault code belongs to a preset serious fault code; If yes, executing the steps of determining target repair cost information corresponding to repairing the target vehicle within at least two different preset time periods according to the fault code and the following steps; If not, the steps of determining target repair cost information corresponding to repairing the target vehicle within at least two different preset time periods according to the fault code and subsequent steps are not performed.

6. A vehicle fault reminder platform, characterized in that: include: An acquisition module, used to acquire the fault code of the target vehicle; A collection module is used to collect data related to the fault code in advance, and then integrate and store the maintenance cost information of the fault code in different time periods according to the collected data; wherein the integration of the data includes deduplication, deletion of unreasonable data or merging of data; A target maintenance cost information determination module is used to determine, according to the fault code, target maintenance cost information corresponding to maintenance of the target vehicle within at least two different preset time periods, including: Determine, according to the fault code, an associated code corresponding to the target vehicle being repaired within at least two different preset time periods; wherein the preset time period is used to indicate the time for the user to perform repair processing after the vehicle fails; different fault codes correspond to different preset time periods; Obtaining first maintenance cost information corresponding to maintenance of the fault code within at least two different preset time periods, and obtaining second maintenance cost information corresponding to maintenance of the associated code within at least two different preset time periods; wherein the vehicle fault that occurred previously is referred to as the first fault, other faults that may be caused are referred to as associated faults, and the fault code corresponding to the associated fault is referred to as the associated code; the first maintenance cost information is used to describe the cost information corresponding to maintenance of the first fault within at least two different preset time periods, and the second maintenance cost information is used to describe the cost information corresponding to maintenance of the associated fault within at least two different preset time periods; Determine the target maintenance cost information according to the first maintenance cost information and the second maintenance cost information; The target maintenance cost information is used to describe the cost information corresponding to the maintenance of the target vehicle within at least two different preset time periods, and is used to reflect the economic and safety issues corresponding to the maintenance within at least two different preset time periods; the target maintenance cost information includes at least one of: maintenance cost, maintenance time, life data of the faulty component, and life data of the vehicle; An output module is used to output the target maintenance cost information to a user of the target vehicle.

7. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the vehicle fault reminder method according to any one of claims 1 to 5 is implemented.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the vehicle fault reminder method according to any one of claims 1 to 5 is implemented.

Images