Automobile fault notification method, system, equipment and medium

Abstract

The invention relates to an automobile fault notification method, system and device and a medium, and the method comprises the steps: obtaining a fault information table of an automobile, the fault information table comprises a fault reporting interface function, an anti-shake time threshold value and an event sequence number; based on the report interface function, obtaining a calling code of the fault from a preset code management module; executing the calling code to obtain the occurrence condition of the fault; obtaining a confirmation code of the fault from a preset code management module based on the anti-shake time threshold value and the occurrence condition; executing the confirmation code to obtain the confirmation condition of the fault; and obtaining the notification code from the preset code management module, and transmitting the confirmation condition and the event sequence number to the terminal equipment by executing the notification code so as to notify the fault. The problems that in the prior art, different developers are different in familiarity with the architecture of the same software, programming styles are not uniform, the development efficiency is low, and the maintainability of the software is reduced are solved.

Description

Background Art

[0002] Most automotive electronic software is developed based on AUTOSAR (Automotive Open System Architecture). The DEM (Diagnostic Event Manager) module in AUTOSAR provides the concept of events to manage fault information. Developers need to implement software that collects fault information from various functional modules and notifies the DEM module to trigger events associated with the fault.

[0003] At present, most of the automobile fault information collection and notification software adopts a process-oriented programming paradigm, which is written by developers of various functional modules. Although this model can complete the software development work, it relies on the programming ability of each developer.

[0004] However, in the prior art, different developers have different degrees of familiarity with the architecture of the same software and their programming styles are not uniform, resulting in low development efficiency and reduced software maintainability. Summary of the invention

[0005] In order to overcome the problem in the prior art that different developers have different levels of familiarity with the architecture of the same software and have inconsistent programming styles, resulting in low development efficiency and reduced software maintainability, the present application provides a vehicle fault notification method, system, device and medium.

[0006] In a first aspect, in order to solve the above technical problems, the present application provides a method for notifying a vehicle fault, comprising:

[0007] Obtain the fault information table of the vehicle, which includes multiple fault information, including the fault reporting interface function, anti-shake time threshold and event sequence number;

[0008] Based on the reporting interface function, obtain the fault calling code from the preset code management module;

[0009] Execute the calling code to get the fault situation;

[0010] Based on the anti-shake time threshold and the occurrence situation, obtain the fault confirmation code from the preset code management module;

[0011] Execute the confirmation code to obtain the confirmation of the fault;

[0012] Obtain the notification code from the preset code management module, and transmit the confirmation status and event sequence number to the terminal device by executing the notification code to notify the fault.

[0013] In a second aspect, the present application also provides a vehicle fault notification system, comprising:

[0014] A first acquisition module is used to acquire a fault information table of a vehicle, wherein the fault information table includes multiple pieces of fault information, and the fault information includes a fault reporting interface function, an anti-shake time threshold, and an event sequence number;

[0015] A second acquisition module is used to acquire the calling code of the fault from the preset code management module based on the reporting interface function;

[0016] The first execution module is used to execute the calling code to obtain the occurrence of the fault;

[0017] A third acquisition module is used to obtain a confirmation code of the fault from the preset code management module based on the anti-shake time threshold and the occurrence situation;

[0018] The second execution module is used to execute the confirmation code to obtain the confirmation of the fault;

[0019] The notification module is used to obtain the notification code from the preset code management module, and transmit the confirmation situation and event sequence number to the terminal device by executing the notification code to notify the fault.

[0020] In a third aspect, the present application also provides a computing device, including a memory, a processor, and a program stored in the memory and running on the processor, and when the processor executes the program, the steps of a vehicle fault notification method as described above are implemented.

[0021] In a fourth aspect, the present application also provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed on a terminal device, the terminal device executes the steps of a vehicle fault notification method.

[0022] The beneficial effect of the present application is that the acquired fault information table of the automobile includes multiple fault information, each of which includes a fault reporting interface function, an anti-shake time threshold and an event sequence number. The preset code management module stores multiple call codes, multiple confirmation codes and notification codes, wherein each call code corresponds to a reporting interface function, and each confirmation code corresponds to an anti-shake time threshold and the occurrence of the fault. Then, the corresponding fault call code obtained from the preset code management module based on the reporting interface function is executed to obtain the occurrence of the fault, and the confirmation code of the fault obtained from the preset code management module based on the anti-shake time threshold and the occurrence of the fault is executed to obtain the confirmation of the fault, and then the confirmation and event sequence number are transmitted to the terminal device by executing the notification code obtained from the preset code management module to notify the fault. In this way, there is no need for different developers to participate in code development. Only one developer needs to collect the fault information of the car, and then he can directly call and execute the call code, confirmation code and notification code corresponding to the fault in sequence from the preset code management module through the fault information to realize the fault notification, thereby unifying the programming style of software development, facilitating the troubleshooting of problems that arise during the development process, and thus improving the maintainability of the software and reducing the maintenance cost of the software. At the same time, the automated development method of the present application can improve development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 A flowchart of a method for notifying a vehicle failure is shown as an exemplary embodiment of the present application;

[0024] Figure 2 This is a structural schematic diagram of a software script generation device for implementing a vehicle fault notification method in an exemplary embodiment of the present application;

[0025] Figure 3 This is a flowchart of an automobile fault notification method in an exemplary embodiment of the present application;

[0026] Figure 4 The present invention is a schematic structural diagram of a vehicle fault notification system according to an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0027] The following examples are provided to further explain and supplement the present application and do not constitute any limitation to the present application.

[0028] The following describes an automobile fault notification method, system, device and medium according to an embodiment of the present application in conjunction with the accompanying drawings.

[0029] A method for notifying a car fault in an embodiment of the present application is applied to a terminal device. In the present application scheme, the terminal device is used as the execution subject to illustrate the present application scheme. The terminal device is used to execute the steps of a method for notifying a car fault.

[0030] See also Figure 1 , Figure 1 A flow chart of a method for notifying a vehicle failure is provided in this application. Figure 1 As shown, the present application provides a method for notifying a vehicle fault, comprising:

[0031] Step S11, obtaining a fault information table of the vehicle, the fault information table including multiple fault information, the fault information including a fault reporting interface function, an anti-shake time threshold and an event sequence number;

[0032] Step S12, based on the reporting interface function, obtaining the fault calling code from the preset code management module;

[0033] Step S13, executing the calling code to obtain the occurrence of the fault;

[0034] Step S14, based on the anti-shake time threshold and the occurrence situation, obtaining the fault confirmation code from the preset code management module;

[0035] Step S15, executing the confirmation code to obtain the confirmation of the fault;

[0036] Step S16, obtaining a notification code from the preset code management module, and transmitting the confirmation status and event sequence number to the terminal device by executing the notification code to notify the fault.

[0037] In a method for notifying a car fault of the present embodiment, the fault information table of the car obtained includes multiple fault information, each of which includes a reporting interface function, an anti-shake time threshold and an event sequence number. The preset code management module stores multiple call codes, multiple confirmation codes and notification codes, wherein each call code corresponds to a reporting interface function, and each confirmation code corresponds to an anti-shake time threshold and the occurrence of the fault. Then, the corresponding fault call code obtained from the preset code management module based on the reporting interface function is executed to obtain the occurrence of the fault, and the confirmation code of the fault obtained from the preset code management module based on the anti-shake time threshold and the occurrence of the fault is executed to obtain the confirmation of the fault, and then the confirmation and event sequence number are transmitted to the terminal device by executing the notification code obtained from the preset code management module to notify the fault. In this way, there is no need for different developers to participate in code development. Only one developer needs to collect the fault information of the car, and then he can directly call and execute the call code, confirmation code and notification code corresponding to the fault in sequence from the preset code management module through the fault information to realize the fault notification, thereby unifying the programming style of software development, facilitating the troubleshooting of problems that arise during the development process, and thus improving the maintainability of the software and reducing the maintenance cost of the software. At the same time, the automated development method of the present application can improve development efficiency.

[0038] Optionally, obtain a fault information table of the vehicle, including:

[0039] Obtaining initial fault information of each of the multiple faults occurring in the vehicle;

[0040] Fill the initial fault information into the initial fault information table according to the preset format;

[0041] Perform format check on the initial fault information table and obtain the check result;

[0042] A fault information table is obtained based on the inspection results.

[0043] In this embodiment, the initial fault information of each of the multiple faults occurring in the automobile is generally a string of data, which is filled into the initial fault information table according to a preset format, and a format check is performed on each parameter in the initial fault information table to obtain a check result, and a fault information table is obtained based on the check result. In this way, each data in the fault information table is correct and independent, which can not only reduce the interference caused by irrelevant data when the various data in the fault information table are subsequently called, but also can directly use each data in the fault information table alone, thereby improving the accuracy of data calling.

[0044] In this embodiment, each data in the fault information table is the relevant information of the fault used by the developer during development, and the types of relevant information include fault determination, fault anti-shake and DEM events associated with the fault. Among them, when the type of relevant information is fault determination, the corresponding data is the fault reporting interface function, and each reporting interface function is associated with a fault detection rule; when the type of relevant information is fault anti-shake, the corresponding data is the fault anti-shake time threshold, and the anti-shake time threshold includes the fault confirmation time threshold and the fault recovery time threshold; when the type of relevant information is the DEM event associated with the fault, the corresponding data is the DEM event sequence number of the fault, and each DEM event sequence number is associated with a DTC (Diagnostic Trouble Code).

[0045] Optionally, a format check is performed on the initial fault information table to obtain a check result, including:

[0046] Determine whether the interface function type of the reported interface function in the initial fault information table is a preset type;

[0047] Determine whether the anti-shake time threshold and event sequence number in the initial fault information table are in digital format;

[0048] Obtaining a diagnostic trouble code associated with an event sequence number in an initial trouble information table;

[0049] Determine whether the diagnostic trouble code is consistent with the preset code corresponding to the event sequence number;

[0050] When the interface function type of the interface function reported in the initial fault information table is a preset type, the anti-shake time threshold and the event sequence number are both in digital format, and the diagnostic fault code is consistent with the corresponding preset code, the inspection result is determined to be passed; otherwise, the inspection result is failed.

[0051] In this embodiment, when the interface function type of the interface function reported in the initial fault information table is a preset type, and the anti-shake time threshold and the event sequence number are both in digital format, and the diagnostic fault code is consistent with the corresponding preset code, it means that each data in the initial fault information table is correctly filled in according to the required format. At this time, the inspection result is passed. Otherwise, it means that the data filled in the initial fault information table are incorrectly filled or missing. At this time, the inspection result is failed, which is convenient for subsequent acquisition of a fault information table that meets the accuracy requirements based on the inspection results.

[0052] In this embodiment, when the type of data in the initial fault information table is fault judgment, the corresponding data is the fault reporting interface function: S / R interface function, then the format check of the S / R interface function is: whether the function starts with the "RPort" type. When the type of data in the initial fault information table is fault anti-shake, the corresponding data is the fault anti-shake time threshold, and the anti-shake time threshold includes the anti-shake time threshold and the event sequence number, then the format check is: whether the anti-shake time threshold and the event sequence number are in digital format. When the type of data in the initial fault information table is the DEM event associated with the fault, the corresponding data is the DEM event sequence number of the fault, then the format check is: whether the diagnostic fault code is consistent with the preset code corresponding to the event sequence number.

[0053] Optionally, the inspection result includes inspection passed and inspection failed; and a fault information table is obtained based on the inspection result, including:

[0054] When the inspection result is that the inspection is passed, the initial fault information table is used as the fault information table;

[0055] When the test result is that the inspection fails, the corresponding failure reason is obtained;

[0056] The initial fault information table is updated based on the failure reason until the corresponding inspection result is inspection passed, and the initial fault information table at this time is used as the fault information table.

[0057] In this embodiment, when the inspection result is that the inspection is passed, it means that each data in the initial fault information table is correctly filled in according to the required format, that is, each data in the initial fault information table is data in the correct format, and the initial fault information table at this time is used as the fault information table. When the inspection result is that the inspection is not passed, it means that each data filled in the initial fault information table is filled in incorrectly or missingly, and the incorrectly filled or missing data cannot be correctly called later, resulting in an exception when calling the code corresponding to the incorrectly filled or missing data from the preset code management module, and the problem found during the format check is used as the reason for failure, and the initial fault information table is updated based on the reason for failure, so that the developer can troubleshoot the incorrectly filled and / or missing problems in the initial fault information table, so that each data in the updated initial fault information table is data in the correct format, and the initial fault information table at this time is used as the fault information table. In this way, it is ensured that each data in the fault information table is always data in the correct format, and the probability of an exception when calling the code corresponding to each data in the initial fault information table from the preset code management module later is reduced, thereby improving the accuracy of the final notification of the automobile fault.

[0058] Optionally, execute the calling code to obtain the occurrence of the fault, including:

[0059] Execute the calling code to obtain the fault detection rules associated with the reporting interface function;

[0060] Call the reporting interface function, and use the fault detection rules to obtain the fault type shaping data from the reporting interface function;

[0061] Based on the fault type shaping data, determine the occurrence of the fault.

[0062] In this embodiment, the calling code is executed to call the reporting interface function, and the fault type integer data is obtained from the reporting interface function using the fault detection rule associated with the reporting interface function. The bit of the fault type integer data represents a specific fault type. When the bit is 1, it indicates that the fault has occurred, and when the bit is 0, it indicates that the fault has not occurred. Based on whether the bit of the fault type integer data is 1 or 0, it is determined whether the fault has occurred or not, so as to facilitate the subsequent acquisition of the confirmation code based on the fault occurrence.

[0063] Optionally, the anti-shake time threshold includes a fault confirmation time threshold and a fault recovery time threshold, and the occurrence includes a fault occurrence; executing the confirmation code to obtain the confirmation of the fault includes:

[0064] Execute the confirmation code, start timing when a fault occurs, and obtain the fault time of the fault;

[0065] When the fault time is greater than the fault confirmation time threshold, the fault confirmation condition is determined to be the existence of the fault;

[0066] When the fault time is less than or equal to the fault confirmation time threshold, the time is counted from the end of the fault time to obtain the time when the fault disappears;

[0067] When the disappearance time is greater than the fault recovery time threshold, it is determined that the confirmation status of the fault is that the fault disappears.

[0068] In this embodiment, the confirmation code is executed, and the timing starts when the fault occurs, and the fault time of the fault is obtained. When the fault time is greater than the fault confirmation time threshold, the confirmation of the fault is determined to be the existence of the fault; and when the fault time is less than or equal to the fault confirmation time threshold, the timing starts from the end of the fault time to obtain the disappearance time of the fault, and when the disappearance time is greater than the fault recovery time threshold, the confirmation of the fault is determined to be the disappearance of the fault. In this way, according to the fault time after the fault occurs, it can be determined whether the confirmation of the fault is the existence of the fault or the disappearance of the fault, so as to notify the terminal device of the confirmation, so that the staff can timely understand the situation of the fault, so as to be able to provide a response plan in time, thereby improving the maintainability of the fault.

[0069] Optionally, the method further comprises:

[0070] Get the modification status of each code in the preset code management module;

[0071] When the modification status is modified, a corresponding modification log is generated for saving.

[0072] In this embodiment, each code in the preset code management module is a pre-set code based on the same software. If the code changes, it will affect the subsequent execution process and result errors. Therefore, it is necessary to monitor the modification status of each code in the preset code management module. When the modification status is modified, a corresponding modification log is generated and saved, so that developers can promptly understand whether each code in the preset code management module has been modified and the reasons for the modification, so as to promptly solve the problems caused by the code modification.

[0073] See also Figure 2 , Figure 2 This is a schematic diagram of a software script generation device for implementing a method for notifying a vehicle fault in an exemplary embodiment of the present application. The software script generation device is used to generate software codes for fault notification corresponding to each fault based on the reporting interface function, anti-shake time threshold and event sequence number of each fault in the fault information table after obtaining the fault information table of the vehicle. Figure 2 In this embodiment, the software script generation device includes an input content checking module, a preset code management module, a function code generation module and a code assembly module.

[0074] The input content checking module is used to perform format checking on each data in the initial fault information table containing initial fault information of each of the multiple faults.

[0075] The preset code management module stores multiple call codes, multiple confirmation codes and notification codes. The preset code management module is used to manage the stored fixed codes. Each code includes the necessary header files, macro definitions, and structure definitions. The module is also used to check whether the static files where each fixed code is located have been modified. When a modification occurs, a modification log will be generated to record the modification content and save the modification log.

[0076] The functional code generation module includes a fault judgment module, a fault anti-shake module, and a fault notification module; the fault judgment module is used to obtain the fault calling code from the preset code management module based on the reporting interface function, and execute the calling code to obtain the fault occurrence situation: if the occurrence situation is a fault, the global variable representing the current state of the fault is assigned to true, otherwise, it is assigned to false; the fault anti-shake module is used to obtain the fault confirmation code from the preset code management module based on the anti-shake time threshold and the occurrence situation, and execute the confirmation code to obtain the fault confirmation situation: read the global variable representing the current state of the fault, and execute the fault anti-shake process when it is true, and count the fault time (the duration after the fault occurs). After the duration exceeds the fault confirmation time threshold, the global variable representing the current state of the fault is assigned to true. The global variable representing the fault confirmation state is assigned a value of true. If the duration is less than or equal to the fault confirmation time threshold, the fault recovery process is executed, and the disappearance time (duration after the fault disappears) is counted. After the duration exceeds the fault recovery time threshold, the global variable representing the fault confirmation state is assigned a value of false. The fault notification module is used to obtain the notification code from the preset code management module, and pass the confirmation status and event sequence number to the terminal device by executing the notification code to notify the fault: read the global variable representing the fault confirmation state, call the DEM standard notification function, and pass the confirmation status corresponding to the fault confirmation state of each fault and the associated DEM event sequence number to the DEM function software for managing faults in AUTOSAR on the terminal device for notification display.

[0077] The code assembly module is used to assemble the call code, confirmation code and notification code obtained by the function code generation module in sequence, and generate the assembled long code in the .c file and .h file according to the preset position. The main function of the code assembly module is designed to be a fixed sequence of the call code corresponding to the fault judgment, the confirmation code corresponding to the fault anti-shake, and the notification code corresponding to the fault notification. It periodically calls the fault information table of the car and the fault judgment module, fault anti-shake module, and fault notification module in the function code generation module, thereby realizing the development of software for fault notification of various faults of the car.

[0078] See also Figure 3 , Figure 3 This is a flow chart of a method for notifying a vehicle failure in an exemplary embodiment of the present application, as shown in FIG. Figure 3As shown, the initial fault information table filled in and checked by the developer is obtained, and the initial fault information table and the function code generation module are used to generate the running script for fault notification of each fault in the initial fault information table. At the same time, the format of the initial fault information table is checked to obtain the inspection result. If the inspection result is that the inspection is passed, the running script for fault notification of each fault in the generated initial fault information table and the corresponding generation log are output; if the inspection result is that the inspection is not passed, the corresponding failure reason is obtained, and the initial fault information table is updated based on the failure reason until the corresponding inspection result is that the inspection is passed, and the running script for fault notification of each fault in the generated initial fault information table and the corresponding generation log are output.

[0079] See also Figure 4 , Figure 4 A structural diagram of a vehicle fault notification system is provided for this application. Figure 4 As shown, the present application provides a vehicle fault notification system, comprising:

[0080] A first acquisition module is used to acquire a fault information table of a vehicle, wherein the fault information table includes multiple pieces of fault information, and the fault information includes a fault reporting interface function, an anti-shake time threshold, and an event sequence number;

[0081] A second acquisition module is used to acquire the calling code of the fault from the preset code management module based on the reporting interface function;

[0082] The first execution module is used to execute the calling code to obtain the occurrence of the fault;

[0083] A third acquisition module is used to obtain a confirmation code of the fault from the preset code management module based on the anti-shake time threshold and the occurrence situation;

[0084] The second execution module is used to execute the confirmation code to obtain the confirmation of the fault;

[0085] The notification module is used to obtain the notification code from the preset code management module, and transmit the confirmation situation and event sequence number to the terminal device by executing the notification code to notify the fault.

[0086] In this embodiment, the fault information table of the automobile obtained by the first acquisition module includes multiple fault information, each of which includes a fault reporting interface function, an anti-shake time threshold and an event sequence number. The preset code management module stores multiple call codes, multiple confirmation codes and notification codes, wherein each call code corresponds to a reporting interface function, and each confirmation code corresponds to an anti-shake time threshold and the occurrence of the fault. Then, the first execution module is used to execute the corresponding fault call code obtained from the preset code management module based on the reporting interface function by the second acquisition module to obtain the occurrence of the fault, and the second execution module is used to execute the confirmation code of the fault obtained from the preset code management module based on the anti-shake time threshold and the occurrence of the fault by the Dongsan acquisition module to obtain the confirmation of the fault, and then the notification module is used to execute the notification code obtained from the preset code management module to transmit the confirmation and event sequence number to the terminal device to notify the fault. In this way, there is no need for different developers to participate in code development. Only one developer needs to collect the fault information of the car, and then he can directly call and execute the call code, confirmation code and notification code corresponding to the fault in sequence from the preset code management module through the fault information to realize the fault notification, thereby unifying the programming style of software development, facilitating the troubleshooting of problems that arise during the development process, and thus improving the maintainability of the software and reducing the maintenance cost of the software. At the same time, the automated development method of the present application can improve development efficiency.

[0087] Optionally, the first acquisition module is specifically used to:

[0088] Obtaining initial fault information of each of the multiple faults occurring in the vehicle;

[0089] Fill the initial fault information into the initial fault information table according to the preset format;

[0090] Perform format check on the initial fault information table and obtain the check result;

[0091] A fault information table is obtained based on the inspection results.

[0092] Optionally, the first acquisition module is specifically used to:

[0093] Determine whether the interface function type of the reported interface function in the initial fault information table is a preset type;

[0094] Determine whether the anti-shake time threshold and event sequence number in the initial fault information table are in digital format;

[0095] Obtaining a diagnostic trouble code associated with an event sequence number in an initial trouble information table;

[0096] Determine whether the diagnostic trouble code is consistent with the preset code corresponding to the event sequence number;

[0097] When the interface function type of the interface function reported in the initial fault information table is a preset type, the anti-shake time threshold and the event sequence number are both in digital format, and the diagnostic fault code is consistent with the corresponding preset code, the inspection result is determined to be passed; otherwise, the inspection result is failed.

[0098] Optionally, the inspection result includes inspection passed and inspection failed; the first acquisition module is specifically used to:

[0099] When the inspection result is that the inspection is passed, the initial fault information table is used as the fault information table;

[0100] When the test result is that the inspection fails, the corresponding failure reason is obtained;

[0101] The initial fault information table is updated based on the failure reason until the corresponding inspection result is inspection passed, and the initial fault information table at this time is used as the fault information table.

[0102] Optionally, the first execution module is specifically configured to:

[0103] Execute the calling code to obtain the fault detection rules associated with the reporting interface function;

[0104] Call the reporting interface function, and use the fault detection rules to obtain the fault type shaping data from the reporting interface function;

[0105] Based on the fault type shaping data, determine the occurrence of the fault.

[0106] Optionally, the anti-shake time threshold includes a fault confirmation time threshold and a fault recovery time threshold, and the occurrence includes a fault occurrence; the second execution module is specifically used to:

[0107] Execute the confirmation code, start timing when a fault occurs, and obtain the fault time of the fault;

[0108] When the fault time is greater than the fault confirmation time threshold, the fault confirmation condition is determined to be the existence of the fault;

[0109] When the fault time is less than or equal to the fault confirmation time threshold, the time is counted from the end of the fault time to obtain the time when the fault disappears;

[0110] When the disappearance time is greater than the fault recovery time threshold, it is determined that the confirmation status of the fault is that the fault disappears.

[0111] Optionally, the system further includes a log storage module, the log storage module being specifically used for:

[0112] Get the modification status of each code in the preset code management module;

[0113] When the modification status is modified, a corresponding modification log is generated for saving.

[0114] A computing device according to an embodiment of the present application includes a memory, a processor, and a program stored in the memory and running on the processor. When the processor executes the program, some or all steps of the above-mentioned automobile fault notification method are implemented.

[0115] Among them, the computing device can be a computer, and correspondingly, its program is computer software. The above-mentioned parameters and steps in a computing device of the present application can refer to the parameters and steps in an embodiment of a car fault notification method mentioned above, and will not be repeated here.

[0116] In an embodiment of the present application, a computer-readable storage medium is provided, in which instructions are stored. When the instructions are executed, the steps of the above-mentioned vehicle fault notification method are executed.

[0117] The computer-readable storage medium may be a transient computer-readable storage medium or a non-transitory computer-readable storage medium.

[0118] The technical solution of the embodiment of the present disclosure can be embodied in the form of a software product, which is stored in a storage medium and includes one or more instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method of the embodiment of the present disclosure. The aforementioned computer-readable storage medium may be a non-transitory computer-readable storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a disk or an optical disk, and other media that can store program codes, or a transient computer-readable storage medium.

[0119] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0120] Those skilled in the art know that the present application can be implemented as a system, method or computer program product. Therefore, the present disclosure can be specifically implemented in the following forms, namely: it can be complete hardware, it can be complete software (including firmware, resident software, microcode, etc.), or it can be a combination of hardware and software, generally referred to as "module" or "system" herein. In addition, in some embodiments, the present application can also be implemented in the form of a computer program product in one or more computer-readable media, and the computer-readable medium contains computer-readable program code. Computer-readable storage media can be, for example, but not limited to - electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above.

[0121] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0122] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limitations on the present application. Ordinary technicians in this field can change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A method for notifying a vehicle failure, characterized in that: include: Obtaining a fault information table of the vehicle, the fault information table including multiple pieces of fault information, the fault information including a fault reporting interface function, an anti-shake time threshold, and an event sequence number; Based on the reporting interface function, obtaining the calling code of the fault from the preset code management module; Execute the calling code to obtain the occurrence of the fault; Based on the anti-shake time threshold and the occurrence situation, obtaining a confirmation code of the fault from the preset code management module; Execute the confirmation code to obtain confirmation of the fault; A notification code is obtained from the preset code management module, and the confirmation status and the event sequence number are transmitted to the terminal device by executing the notification code to notify the fault.

2. The method according to claim 1, characterized in that The step of obtaining the fault information table of the vehicle includes: Obtaining initial fault information of each of the multiple faults occurring in the vehicle; Filling the initial fault information into the initial fault information table according to a preset format; Performing a format check on the initial fault information table to obtain a check result; A fault information table is obtained based on the inspection result.

3. The method according to claim 2, characterized in that The format check of the initial fault information table is performed to obtain the check result, including: Determine whether the interface function type of the reporting interface function in the initial fault information table is a preset type; Determine whether the anti-shake time threshold and the event sequence number in the initial fault information table are in digital format; Obtaining a diagnostic fault code associated with the event sequence number in the initial fault information table; Determining whether the diagnostic fault code is consistent with a preset code corresponding to the event sequence number; When the interface function type of the reporting interface function in the initial fault information table is a preset type, and the anti-shake time threshold and the event sequence number are both in digital format, and the diagnostic fault code is consistent with the corresponding preset code, the inspection result is determined to be passed; otherwise, the inspection result is failed.

4. The method according to claim 2, characterized in that: The inspection result includes inspection pass and inspection fail; the fault information table obtained based on the inspection result includes: When the inspection result is that the inspection is passed, the initial fault information table is used as the fault information table; When the detection result is that the inspection fails, obtain the corresponding reason for failure; The initial fault information table is updated based on the failure reason until the corresponding inspection result is inspection passed, and the initial fault information table at this time is used as the fault information table.

5. The method according to claim 1, characterized in that The executing the calling code to obtain the occurrence of the fault includes: Execute the calling code to obtain the fault detection rule associated with the reporting interface function; Calling the reporting interface function, and obtaining fault type shaping data from the reporting interface function using the fault detection rule; Based on the fault type shaping data, the occurrence of the fault is determined.

6. The method according to any one of claims 1 to 5, characterized in that: The anti-shake time threshold includes a fault confirmation time threshold and a fault recovery time threshold, and the occurrence includes a fault occurrence; and executing the confirmation code to obtain the confirmation of the fault includes: Execute the confirmation code, start timing when the occurrence is a fault, and obtain the fault time of the fault; When the fault time is greater than the fault confirmation time threshold, determining that the confirmation status of the fault is that the fault exists; When the fault time is less than or equal to the fault confirmation time threshold, timing is started from the end time of the fault time to obtain the disappearance time of the fault; When the disappearance time is greater than the fault recovery time threshold, it is determined that the confirmation status of the fault is that the fault disappears.

7. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Obtaining the modification status of each code in the preset code management module; When the modification status is modified, a corresponding modification log is generated and saved.

8. A vehicle fault notification system, characterized in that: include: A first acquisition module is used to acquire a fault information table of a vehicle, wherein the fault information table includes multiple pieces of fault information, and the fault information includes a reporting interface function of the fault, an anti-shake time threshold, and an event sequence number; A second acquisition module, configured to acquire the calling code of the fault from a preset code management module based on the reporting interface function; A first execution module, used for executing the calling code to obtain the occurrence of the fault; A third acquisition module, configured to acquire a confirmation code of the fault from the preset code management module based on the anti-shake time threshold and the occurrence situation; A second execution module is used to execute the confirmation code to obtain the confirmation status of the fault; The notification module is used to obtain the notification code from the preset code management module, and transmit the confirmation status and the event sequence number to the terminal device by executing the notification code to notify the fault.

9. A computing device comprising a memory, a processor, and a program stored in the memory and running on the processor, characterized in that: When the processor executes the program, the steps of the automobile fault notification method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on the terminal device, the terminal device executes the steps of the automobile fault notification method according to any one of claims 1 to 7.

Images