Method, device and equipment for repairing abnormity of in-vehicle infotainment system, and storage medium

Abstract

The invention relates to the technical field of in-vehicle infotainment systems, and discloses an in-vehicle infotainment exception repairing method, device and equipment and a storage medium, and the method comprises the following steps: determining an exception associated file and an exception identification code according to an application exception log; acquiring a collection position corresponding to the application exception log; determining an exception type according to the exception association file, the collection position and the exception identification code; and on the basis of the file information of the exception associated file, calling an exception repair interface corresponding to the exception type to carry out vehicle-machine exception repair. Whether the abnormity occurs can be quickly determined through the burying point collection data and the vehicle machine system log, when the abnormity occurs, the abnormity type is quickly determined according to the abnormity association file, the abnormity identification code and the collection position of the application abnormity log, and then the corresponding abnormity repair interface is searched in the repair knowledge base according to the abnormity type and is called. The user is guided to exclude the vehicle-mounted terminal abnormity, so that after-sales engineers do not need to intervene every time the vehicle-mounted terminal abnormity occurs, and the actual use experience of the user is improved.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle computer systems, and in particular to a method, device, equipment and storage medium for repairing abnormalities in a vehicle computer. Background Art

[0002] Nowadays, vehicle manufacturers generally provide continuous services for vehicles through software upgrades and other means, and are responsible for the upgrade and maintenance of the vehicle's on-board system. In the scenario of software upgrade, there are many scenarios where the software can only be used normally after the file is successfully copied, such as: copying files (such as voice resources, etc.) from the system upgrade package to the sdcard directory, or copying database resources from the software upgrade package (apk) to the local path, etc. In general, in such copying scenarios, corresponding verification mechanisms are added during design to ensure the integrity of the file copy. Once the file is incomplete, the copy will be retried. However, even after multiple attempts, it is still difficult to completely avoid abnormal missing. Once the file is abnormally missing, it may cause the system or vehicle application to fail to start, or crash during operation.

[0003] Currently, there is a lack of safety design to guide repairs for these abnormal situations. After an abnormality occurs, users generally need to contact the manufacturer's franchise store, and the after-sales engineering personnel of the franchise store will intervene to carry out repairs. The overall actual time consumption is relatively long and the user experience is poor. Summary of the invention

[0004] The main purpose of this application is to provide a method, device, equipment and storage medium for repairing vehicle computer abnormalities, aiming to solve the technical problem that the vehicle computer system in the related technology lacks guidance for repairing abnormal situations caused by incomplete file copying, resulting in the need for manual intervention and poor user experience.

[0005] To achieve the above objectives, the present application proposes a vehicle computer abnormality repair method, the method comprising:

[0006] Determine the abnormality-related file and the abnormality identification code according to the application abnormality log, wherein the application abnormality log includes the vehicle system log and the embedded point collection data, wherein the embedded point collection data is the data set for embedded point collection in the vehicle standardized function interface;

[0007] Obtaining the collection location corresponding to the application exception log;

[0008] Determine the type of anomaly according to the anomaly-associated file, the collection location, and the anomaly identification code;

[0009] Based on the file information of the exception-related file, the exception repair interface corresponding to the exception type is called to repair the vehicle computer exception.

[0010] Optionally, the calling of an abnormality repair interface corresponding to the abnormality type to repair the vehicle computer abnormality based on the file information of the abnormality-related file includes:

[0011] Obtain application information corresponding to the application exception log;

[0012] Searching for a corresponding abnormal count value and an abnormal determination threshold value according to the application information and the abnormal type;

[0013] Updating the abnormal count value;

[0014] If the updated exception count value is greater than or equal to the exception determination threshold, the exception repair interface corresponding to the exception type is called based on the file information of the exception-related file to perform vehicle computer exception repair.

[0015] Optionally, after updating the abnormal count value, the method further includes:

[0016] If the updated exception count value is less than the exception determination threshold, obtaining the call information of the abnormal application before collecting the application exception log, the call information including the called function, calling method and calling file corresponding to the abnormal application;

[0017] Generate an application calling script based on the calling information;

[0018] Execute the application call script and monitor whether an application exception log is generated;

[0019] When it is monitored that an application exception log corresponding to the abnormal application is generated, the abnormal application and the abnormal identification code determined according to the application exception log are returned.

[0020] Optionally, if the updated exception count value is less than the exception determination threshold, obtaining the call information of the abnormal application before collecting the application exception log includes:

[0021] If the updated exception count value is less than the exception determination threshold, obtaining the generation time corresponding to the application exception log;

[0022] Determine a data acquisition period based on the generation time corresponding to the application exception log and a preset duration;

[0023] Read the application call log whose corresponding generation time is within the data acquisition period, wherein the application call log is the log data collected by setting the embedding point in the vehicle computer standardized function interface that needs to be triggered when calling the application, or the log related to the calling application printed by calling the log function in the vehicle computer system;

[0024] Searching the application call log for a log related to the abnormal application to obtain an application-related log;

[0025] The application-related log is analyzed to determine the call information of the abnormal application.

[0026] Optionally, the calling of an abnormality repair interface corresponding to the abnormality type to repair the vehicle computer abnormality based on the file information of the abnormality-related file includes:

[0027] Searching for interface information of an exception repair interface corresponding to the exception type in a repair knowledge base;

[0028] Based on the file information of the exception-related file and the interface information, the exception repair interface corresponding to the exception type is called through the reflection mechanism to repair the vehicle computer exception.

[0029] Optionally, the interface information includes an identifier of the class to which the interface belongs, an interface name, an interface access path, and a call parameter rule;

[0030] The method of calling the abnormality repair interface corresponding to the abnormality type through a reflection mechanism based on the file information of the abnormality-related file and the interface information to repair the abnormality of the vehicle computer includes:

[0031] Extracting the interface class identifier, interface name, interface access path and call parameter rules from the interface information;

[0032] Using the reflection mechanism, the interface implementation instance corresponding to the abnormal repair interface is obtained according to the class identifier to which the interface belongs and the interface access path;

[0033] Constructing interface call parameters according to the file information of the abnormal associated file and the call parameter rule;

[0034] The interface implementation instance is accessed according to the interface name and the interface calling parameters to call the exception repair interface corresponding to the exception type to repair the vehicle computer exception.

[0035] Optionally, determining the exception type according to the exception-related file, the collection location, and the exception identification code includes:

[0036] Determine a suspected category according to the abnormality-related file, the collection location, and the abnormality identification code;

[0037] Find the auxiliary judgment interface corresponding to the suspected category;

[0038] Calling the auxiliary judgment interface to obtain auxiliary judgment information;

[0039] The abnormality type is determined based on the auxiliary judgment information and the suspected category.

[0040] In addition, to achieve the above-mentioned purpose, the present application also provides a vehicle abnormality repair device, the device comprising:

[0041] A determination module, used to determine the abnormality-related file and the abnormality identification code according to the application abnormality log, wherein the application abnormality log includes the vehicle system log and the buried point collection data, wherein the buried point collection data is the data set for buried point collection in the vehicle standardized function interface;

[0042] An extraction module, used to obtain a collection location corresponding to the application exception log;

[0043] A classification module, used to determine the abnormality type according to the abnormality associated file, the collection location and the abnormality identification code;

[0044] The repair module is used to call the abnormality repair interface corresponding to the abnormality type to repair the vehicle computer abnormality based on the file information of the abnormality-related file.

[0045] In addition, to achieve the above-mentioned purpose, the present application also provides a vehicle-machine abnormality repair device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the vehicle-machine abnormality repair method as described above.

[0046] In addition, to achieve the above-mentioned purpose, the present application also provides a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the vehicle machine abnormality repair method as described above are implemented.

[0047] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the vehicle computer abnormality repair method as described above are implemented.

[0048] One or more technical solutions proposed in this application have at least the following technical effects:

[0049] Since it is possible to quickly determine whether an abnormality occurs through data collection at the embedded points and the vehicle system log, and when an abnormality occurs, quickly determine the type of abnormality based on the abnormality-related files, abnormality identification codes, and the collection location of the application abnormality log, then find the corresponding abnormality repair interface in the repair knowledge base and call it based on the abnormality type, guiding the user to eliminate the vehicle abnormality, eliminating the need for manual intervention every time a vehicle abnormality occurs, thereby improving the user's actual usage experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0052] Figure 1 A flowchart of the first embodiment of the vehicle computer abnormality repair method of the present application is provided;

[0053] Figure 2 A flow chart of the second embodiment of the vehicle abnormality repair method of the present application;

[0054] Figure 3 A schematic diagram of a software architecture for implementing and executing an exception repair in an embodiment of the present application;

[0055] Figure 4 This is a schematic diagram of the module structure of the vehicle abnormality repair device according to an embodiment of the present application;

[0056] Figure 5 Schematic diagram of the equipment structure of the hardware operating environment involved in the vehicle computer abnormality repair method in the embodiment of the present application.

[0057] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0058] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0059] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0060] Based on this, the embodiment of the present application provides a method for repairing abnormality of a vehicle computer, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the vehicle computer abnormality repair method of the present application.

[0061] In this embodiment, the vehicle computer abnormality repair method includes steps S10 to S40:

[0062] Step S10: Determine the abnormality-related file and the abnormality identification code according to the application abnormality log.

[0063] It should be noted that the execution subject of this embodiment can be the vehicle itself, or a vehicle abnormality repair device that is set in the vehicle and can control the vehicle system of the vehicle. The vehicle abnormality repair device can be a controller set in the vehicle, such as an ECU controller, or other devices that can achieve the same or similar functions. This embodiment does not limit this. In this embodiment and the following embodiments, the vehicle abnormality repair method of the present invention is described by taking the vehicle abnormality repair device as an example.

[0064] It should be noted that the application exception log may include the vehicle system log and the tracking point collection data, wherein the vehicle system log may be the log data generated by the vehicle system's own log system when an abnormality is detected; the tracking point collection data may be the data set for tracking point collection in the vehicle standardized function interface, and the vehicle standardized function interface may be a standardized interface for process communication in the vehicle system defined by the vehicle manufacturer. When developing each vehicle application, it is necessary to implement the vehicle standardized function interface. Based on this, each vehicle application developer may set tracking point / notification running status information based on the vehicle standardized function interface. After the subsequent vehicle application implements the vehicle standardized function interface, the vehicle system level can obtain and collect the overall tracking point data and interface call data. When an application exception occurs, the application exception log and application call log can be obtained through the corresponding interface / tracking point information / log information perception, etc.

[0065] In actual use, the application exception log generally includes information such as the time when the exception occurred, an exception identification code used to identify the situation of the exception, and exception-related files related to the exception.

[0066] In order to ensure that the exception can be repaired automatically, it is necessary to first determine the specific cause of the exception. Based on this, the application exception log can be parsed first to extract information such as exception-related files and exception identification codes.

[0067] Step S20: Obtain the collection location corresponding to the application exception log.

[0068] It should be noted that the application exception log generally includes the location where the exception is thrown, that is, the location of the relevant code that generates the application exception log. Based on the collection location, the location of the specific associated code can be located.

[0069] Among them, if the application exception log is a vehicle system log, the collection location at this time is the code location that calls the log system that comes with the vehicle system; and if the application exception log is a point-in-time data collection, the collection location obtained at this time is the location set for the point-in-time data.

[0070] Step S30: determining the abnormality type according to the abnormality-related file, the collection location and the abnormality identification code.

[0071] It should be noted that, based on the collection location, the location of the relevant code when the exception occurs can be determined, and then, combined with the exception identification code and the exception-related file, the exception category of the exception that occurred can be determined.

[0072] In actual use, the exception categories may include: initialization exceptions caused by incomplete resource file copying, operation exceptions caused by incomplete resource file copying, resource file download failures caused by insufficient space, resource file reading errors, conflicts between cached files and new resource files, etc.

[0073] For example: assuming that the exception-associated file is a voice resource file in the APK file, the exception identification code is an initialization exception, and the collection location is the application installation initialization interface code location, then the exception category can be determined as a read initialization exception caused by incomplete resource files or lost resource files.

[0074] In a specific implementation, in order to ensure that the abnormality type can be determined as accurately as possible, step S30 in this embodiment may include:

[0075] Determine a suspected category according to the abnormality-related file, the collection location, and the abnormality identification code;

[0076] Find the auxiliary judgment interface corresponding to the suspected category;

[0077] Calling the auxiliary judgment interface to obtain auxiliary judgment information;

[0078] The abnormality type is determined based on the auxiliary judgment information and the suspected category.

[0079] It should be noted that the suspected category may be a possible abnormal category determined based on the abnormal associated file, the collection location and the abnormal identification code. The auxiliary judgment interface may be an interface for obtaining further auxiliary judgment of the abnormal category.

[0080] In actual use, the auxiliary judgment interface can be called to obtain auxiliary judgment information, and the suspected category can be further checked based on the auxiliary judgment information, and finally, the real abnormal type can be determined.

[0081] For example: assuming that the suspected category is determined to be the application initialization exception caused by the missing resource file, or the application initialization exception caused by the missing SDK file based on the exception-related file, the collection location and the exception identification code, then the auxiliary judgment interface can be the SDK detection interface and the resource file detection interface, and the auxiliary judgment information obtained can be the SDK file detection result and the resource file integrity detection result;

[0082] Assuming that the suspected category is determined to be incomplete voice resources in the resource file according to the abnormal associated file, the collection location and the abnormal identification code, resulting in a loading failure and an application crash, or a file I / O conflict causing a voice resource reading error and an application crash, then the auxiliary judgment interface can be a resource file integrity detection interface and an I / O verification interface, and the auxiliary judgment information can be a voice resource detection result and an I / O conflict verification result;

[0083] Assuming that the suspected category is determined based on the abnormal associated files, collection location and abnormal identification code that the system upgrade package is incomplete, resulting in the failure of the online upgrade of the vehicle system, or that the system upgrade package decompression fails due to insufficient storage space in the vehicle system, then the auxiliary judgment interface can be the system upgrade package verification interface on the server side and the vehicle system remaining space detection interface, and the auxiliary judgment information can be the system upgrade package integrity verification machine result, the space required for decompression of the system upgrade package, and the remaining space of the vehicle system.

[0084] Step S40: Based on the file information of the abnormality-related file, call the abnormality repair interface corresponding to the abnormality type to repair the vehicle computer abnormality.

[0085] In actual use, a repair knowledge base can be set up in the vehicle computer abnormality repair device. After determining the abnormality type, the corresponding abnormality repair interface can be found in the repair knowledge base according to the abnormality type. Then, the abnormality repair interface is called based on the file information of the abnormality-related file to perform the corresponding vehicle computer abnormality repair.

[0086] Among them, the repair knowledge base can be pre-set by the manager of the vehicle-mounted abnormality repair equipment. The repair knowledge base can include a variety of different abnormality repair interfaces. Each abnormality repair interface can implement different repair processing logic when executed, for example: process cache clearing, application call reset, deletion of data under the specified path, re-download of resources and other processing logic.

[0087] In a specific implementation, in order to ensure that the abnormality repair interface can be called quickly and easily, step S40 in this embodiment may include:

[0088] Searching for interface information of an exception repair interface corresponding to the exception type in a repair knowledge base;

[0089] Based on the file information of the exception-related file and the interface information, the exception repair interface corresponding to the exception type is called through the reflection mechanism to repair the vehicle computer exception.

[0090] It should be noted that the interface information may include the class identifier to which the interface belongs, the interface name, the interface access path, and the call parameter rules. There may be many exception repair interfaces, and with the development of technology, new exception repair interfaces may be added at any time. If corresponding calling codes or scripts are set for each different exception repair interface, the workload will be very large, and subsequent changes will be very inconvenient. In order to avoid this situation, the reflection mechanism can be used to call the exception repair interface corresponding to the exception type.

[0091] Among them, the reflection mechanism is a way to write general methods to implement any interface instance and call the interface in the instance.

[0092] It can be understood that by utilizing the reflection mechanism, a set of calling codes can be written that can universally call the exception repair interface corresponding to the exception type according to the file information of the exception-associated file and the interface information. When the exception repair interface needs to be called thereafter, it is only necessary to obtain the corresponding interface information and the file information of the exception-associated file to implement the call, which greatly reduces the workload. Moreover, if a new exception repair interface needs to be added thereafter, it is only necessary to use the previous format to set the interface information, and the modification is very convenient.

[0093] In a specific implementation, in order to ensure the universality of calling the exception repair interface, the step of calling the exception repair interface corresponding to the exception type through a reflection mechanism based on the file information of the exception-related file and the interface information in this embodiment to repair the vehicle computer exception may include:

[0094] Extracting the interface class identifier, interface name, interface access path and call parameter rules from the interface information;

[0095] Using the reflection mechanism, the interface implementation instance corresponding to the abnormal repair interface is obtained according to the class identifier to which the interface belongs and the interface access path;

[0096] Constructing interface call parameters according to the file information of the abnormal associated file and the call parameter rule;

[0097] The interface implementation instance is accessed according to the interface name and the interface calling parameters to call the exception repair interface corresponding to the exception type to repair the vehicle computer exception.

[0098] It should be noted that the location of the code compilation file corresponding to the exception repair interface can be obtained according to the class identifier of the interface and the interface access path. Afterwards, the code compilation file corresponding to the exception repair interface can be accessed using the reflection mechanism to create an interface implementation instance corresponding to the exception repair interface. Afterwards, in order to correctly call the exception repair interface, the file information of the exception-related file can be formatted and assembled based on the calling parameter rules, and the interface calling parameters for calling the exception repair interface can be constructed. Afterwards, the interface implementation instance can be accessed based on the interface name and the interface calling parameters, and the exception repair interface corresponding to the exception type in the interface implementation instance can be called, thereby realizing the vehicle computer exception repair.

[0099] Among them, the exception repair interface can be a cross-process communication interface such as Intent / broadcast / AIDL.

[0100] The present embodiment provides a method for repairing vehicle computer abnormalities. Since it is possible to quickly determine whether an abnormality occurs through data collection at embedded points and vehicle computer system logs, and when an abnormality occurs, quickly determine the abnormality type based on the abnormality-related file, the abnormality identification code, and the collection location of the application abnormality log, then find the corresponding abnormality repair interface in the repair knowledge base and call it based on the abnormality type, guiding the user to eliminate the vehicle computer abnormality, eliminating the need for manual intervention every time a vehicle computer abnormality occurs, thereby improving the user's actual usage experience.

[0101] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 2 , step S40 may include steps S401 to S404:

[0102] Step S401: Obtain application information corresponding to the application exception log.

[0103] It should be noted that the application exception log can generally also record the process information of the process that generates the exception log, such as the process number, process name, process ownership, etc. Based on the process information, the application to which the process that generates the application exception log belongs can be determined. After that, the application information of the application can be obtained, thereby obtaining the application information corresponding to the application exception log.

[0104] The application information may be information related to the vehicle-mounted application, and may include information such as the application name, application type, application installation location, and application occupied space.

[0105] Step S402: searching for a corresponding abnormality count value and an abnormality determination threshold value according to the application information and the abnormality type.

[0106] It should be noted that the abnormality count value may be the number of times the abnormality type has been detected continuously as previously recorded, and the abnormality determination threshold may be the number of times that continuous detection is required to determine that an abnormality actually occurs.

[0107] In actual use, the anomaly count value and the anomaly determination threshold are uniquely determined by the anomaly type combined with the application, that is, for the same anomaly type Y1, the anomaly count values ​​of application A and application B can be independent of each other; at the same time, for the same application, different anomaly types may have different corresponding anomaly determination thresholds.

[0108] Among them, the exception judgment threshold corresponding to the more serious or easier to verify exception type can be lower, otherwise, it can be set higher. For example, the exception caused by the failure to decompress the resource file due to insufficient space is easier to verify. It only needs to detect whether the memory space required for decompressing the resource file is greater than the remaining memory space of the vehicle system. In this case, there is no need to repeat the verification multiple times. Therefore, the exception judgment threshold corresponding to this type of exception type can be set to 1.

[0109] In actual application, if it is detected that a certain in-vehicle application can be run normally, all abnormal count values ​​corresponding to the in-vehicle application can be cleared.

[0110] Step S403: Update the abnormal count value.

[0111] In actual use, the acquired exception count value may be incremented by 1, thereby updating the exception count value.

[0112] Step S404: If the updated abnormality count value is greater than or equal to the abnormality determination threshold, based on the file information of the abnormality-related file, the abnormality repair interface corresponding to the abnormality type is called to perform vehicle computer abnormality repair.

[0113] It should be noted that if the updated exception count value is greater than or equal to the exception judgment threshold, it means that for the application corresponding to the application information, the exception corresponding to the exception type has been continuously detected in the application. At this time, it can be determined that repair is really needed. Therefore, based on the file information of the exception-associated file, the exception repair interface corresponding to the exception type can be called to repair the vehicle computer exception.

[0114] In a specific implementation, in order to ensure that it is possible to quickly determine whether an abnormality actually occurs, after step S403 in this embodiment, the following may also be included:

[0115] If the updated exception count value is less than the exception determination threshold, obtaining the call information of the abnormal application before collecting the application exception log;

[0116] Generate an application calling script based on the calling information;

[0117] Execute the application call script and monitor whether an application exception log is generated;

[0118] When it is monitored that an application exception log corresponding to the abnormal application is generated, the abnormal application and the abnormal identification code determined according to the application exception log are returned.

[0119] It should be noted that the calling information of the abnormal application may include the called function, calling method and calling file corresponding to the abnormal application, wherein the called function may be the functional interface accessed in the abnormal application when an abnormality occurs in the abnormal application, the calling method may be the triggering method when accessing the functional interface, and the calling file may be the file accessed, generated or modified after the functional interface is called and executed.

[0120] In actual use, occasional exceptions may occur in some cases due to network fluctuations, process occupation, etc. At this time, there may be no real exception and no need to repair it. In order to eliminate such occasional situations, an application call script can be generated according to the call information. Then, the application call script is executed to simulate the occurrence of an application exception log. The abnormal application is called in the same triggering manner. Then, it can be monitored whether an application exception log is generated. If an application exception log corresponding to the abnormal application is generated, it means that the exception is reproduced at this time. However, it is actually impossible to determine whether it is reproduced multiple times in a row. Therefore, it is possible to return to step S10 and continue to detect.

[0121] In a specific implementation, in order to ensure that the call information of the abnormal application can be obtained, if the updated abnormal count value is less than the abnormal determination threshold, the step of obtaining the call information of the abnormal application before collecting the application abnormal log may include:

[0122] If the updated exception count value is less than the exception determination threshold, obtaining the generation time corresponding to the application exception log;

[0123] Determine a data acquisition period based on the generation time corresponding to the application exception log and a preset duration;

[0124] Read the application call log whose corresponding generation time is within the data acquisition period;

[0125] Searching the application call log for a log related to the abnormal application to obtain an application-related log;

[0126] The application-related log is analyzed to determine the call information of the abnormal application.

[0127] It should be noted that the application call log is the log data collected by setting the embedding point in the standardized function interface of the vehicle computer that is triggered when calling the application, or the log related to the calling application is printed by calling the log function in the vehicle computer system.

[0128] In actual use, the time when the abnormal application is called and the time when the corresponding application abnormal log is generated are generally close. However, in some cases, the vehicle system may be busy due to process occupation and other reasons, resulting in freezes. At this time, the time when the abnormal application is called and the time when the application abnormal log is generated will be separated by a certain time.

[0129] Based on this, in order to ensure that the call information of the abnormal application can be obtained, the generation time corresponding to the application abnormal log can be obtained first, and then the generation time is added to the preset duration to obtain the end time. Then, the generation time is used as the starting time, and it is combined with the end time to determine the data acquisition period. Then, all application call logs whose corresponding generation time is within the data acquisition period are obtained, and then the application call logs are filtered according to the application information, and the logs related to the abnormal application are found, and other irrelevant logs are filtered out to obtain application-related logs. Finally, the application-related logs are parsed to obtain the call information of the abnormal application.

[0130] For ease of understanding, now combined Figure 3 This is for illustration only, but not for limitation. Figure 3 A schematic diagram of the software architecture for implementing the abnormality repair in this embodiment.

[0131] like Figure 3As shown, in order to implement the vehicle abnormality repair method of the present embodiment, the vehicle system in the vehicle can set a standardized interface management layer in the vehicle system, wherein the vehicle standardized function interface (CustomAPI) may have multiple CustomAPIs according to different functions (such as application initialization, application resource loading, etc. may correspond to different standardized interfaces), and a buried point can be set in the CustomAPI. When the developer of the vehicle-mounted application develops the vehicle-mounted application (such as associated application 1 and associated application 2), it is necessary to implement the vehicle-mounted standardized function interface. In this case, the vehicle-mounted application developed is provided with an implementation instance of the vehicle-mounted standardized function interface. At the same time, there will be corresponding tracking points in this instance. Through this tracking point, the corresponding data can be collected and logs (such as application exception logs and application call logs, etc.) can be generated. The data analysis module in the fault reasoning and repair base can analyze the application exception logs. After that, the fault reasoning module can infer whether there is an exception based on the analysis results of the data analysis module and determine the type of exception. After that, according to the exception type, the corresponding exception repair interface is searched in the repair knowledge base, and a prompt module is used to prompt the user to confirm whether to repair the vehicle computer exception. After the user confirms, the exception repair interface corresponding to the exception type is called to repair the vehicle computer exception.

[0132] This embodiment provides a method for repairing vehicle computer abnormalities. Since repair is not performed every time an abnormality is detected, it is determined whether an abnormality actually occurs by combining the abnormality category and the abnormality count value corresponding to the application information and the abnormality judgment threshold. Only when an abnormality actually occurs will the abnormality repair be guided, thereby reducing meaningless abnormality repairs.

[0133] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the vehicle computer abnormality repair method of the present application. More simple transformations based on this technical concept are all within the protection scope of the present application.

[0134] This application also provides a vehicle abnormality repair device, please refer to Figure 4 , the vehicle abnormality repair device comprises:

[0135] A determination module 10 is used to determine an abnormality-related file and an abnormality identification code according to an application abnormality log, wherein the application abnormality log includes a vehicle system log and embedded point collection data, wherein the embedded point collection data is data set for embedded point collection in a vehicle standardized function interface;

[0136] An extraction module 20 is used to obtain a collection location corresponding to the application exception log;

[0137] A classification module 30, configured to determine an abnormality type according to the abnormality-related file, the collection location, and the abnormality identification code;

[0138] The repair module 40 is used to call the abnormality repair interface corresponding to the abnormality type to repair the vehicle computer abnormality based on the file information of the abnormality-related file.

[0139] The vehicle abnormality repair device provided by the present application adopts the vehicle abnormality repair method in the above embodiment, which can solve the technical problem that the vehicle system in the related technology lacks guidance to repair abnormal situations caused by incomplete file copying, resulting in the need for manual intervention and poor user experience. Compared with the prior art, the beneficial effects of the vehicle abnormality repair device provided by the present application are the same as the beneficial effects of the vehicle abnormality repair method provided by the above embodiment, and the other technical features of the vehicle abnormality repair device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0140] The present application provides a vehicle-machine abnormality repairing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the vehicle-machine abnormality repairing method in the above-mentioned embodiment one.

[0141] Reference below Figure 5 , which shows a schematic diagram of the structure of a vehicle abnormality repair device suitable for implementing the embodiment of the present application. The vehicle abnormality repair device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The vehicle abnormality repair device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0142] like Figure 5As shown, the vehicle abnormality repair device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the vehicle abnormality repair device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the vehicle abnormality repair device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a vehicle abnormality repair device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0143] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0144] The vehicle abnormality repair device provided by the present application adopts the vehicle abnormality repair method in the above embodiment, which can solve the technical problem that the vehicle system in the related technology lacks guidance to repair abnormal situations caused by incomplete file copying, resulting in the need for manual intervention and poor user experience. Compared with the prior art, the beneficial effects of the vehicle abnormality repair device provided by the present application are the same as the beneficial effects of the vehicle abnormality repair method provided by the above embodiment, and the other technical features of the vehicle abnormality repair device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0145] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0146] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0147] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the vehicle computer abnormality repair method in the above-mentioned embodiment.

[0148] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0149] The above-mentioned computer-readable storage medium may be included in the vehicle-machine abnormality repairing device; or may exist independently without being assembled into the vehicle-machine abnormality repairing device.

[0150] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the vehicle-computer abnormality repairing device, the vehicle-computer abnormality repairing device: determines the abnormality-related file and the abnormality identification code according to the application abnormality log, wherein the application abnormality log includes the vehicle-computer system log and the embedded point collection data, and the embedded point collection data is the data set for embedded point collection in the vehicle-computer standardized function interface; obtains the collection location corresponding to the application abnormality log; determines the abnormality type according to the abnormality-related file, the collection location and the abnormality identification code; and based on the file information of the abnormality-related file, calls the abnormality repair interface corresponding to the abnormality type to perform vehicle-computer abnormality repair.

[0151] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0152] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the 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 square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square 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 square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart 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.

[0153] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0154] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle abnormality repair method, and can solve the technical problem that the vehicle system of the related technology lacks guidance to repair abnormal situations caused by incomplete file copying, resulting in the need for manual intervention and poor user experience. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the vehicle abnormality repair method provided by the above-mentioned embodiment, and will not be repeated here.

[0155] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned vehicle computer abnormality repair method when executed by a processor.

[0156] The computer program product provided by this application can solve the technical problem that the related technical vehicle system lacks guidance to repair abnormal situations caused by incomplete file copying, resulting in the need for manual intervention and poor user experience. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the vehicle abnormality repair method provided by the above embodiment, and will not be repeated here.

[0157] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A method for repairing abnormality of a vehicle computer, characterized in that: The method comprises: Determine the abnormality-related file and the abnormality identification code according to the application abnormality log, wherein the application abnormality log includes the vehicle system log and the embedded point collection data, wherein the embedded point collection data is the data set for embedded point collection in the vehicle standardized function interface; Obtaining the collection location corresponding to the application exception log; Determine the type of anomaly according to the anomaly-associated file, the collection location, and the anomaly identification code; Based on the file information of the exception-related file, the exception repair interface corresponding to the exception type is called to repair the vehicle computer exception.

2. The vehicle computer abnormality repair method according to claim 1, characterized in that: The calling of the abnormality repair interface corresponding to the abnormality type to repair the vehicle computer abnormality based on the file information of the abnormality-related file includes: Obtain application information corresponding to the application exception log; Searching for a corresponding abnormal count value and an abnormal determination threshold value according to the application information and the abnormal type; Updating the abnormal count value; If the updated exception count value is greater than or equal to the exception determination threshold, the exception repair interface corresponding to the exception type is called based on the file information of the exception-related file to perform vehicle computer exception repair.

3. The vehicle computer abnormality repair method according to claim 2, characterized in that: After the abnormal count value is updated, the method further includes: If the updated exception count value is less than the exception determination threshold, obtaining the call information of the abnormal application before collecting the application exception log, the call information including the called function, calling method and calling file corresponding to the abnormal application; Generate an application calling script based on the calling information; Execute the application call script and monitor whether an application exception log is generated; When it is monitored that an application exception log corresponding to the abnormal application is generated, the abnormal application and the abnormal identification code determined according to the application exception log are returned.

4. The vehicle computer abnormality repair method according to claim 2, characterized in that: If the updated exception count value is less than the exception determination threshold, obtaining the call information of the abnormal application before collecting the application exception log includes: If the updated exception count value is less than the exception determination threshold, obtaining the generation time corresponding to the application exception log; Determine a data acquisition period based on the generation time corresponding to the application exception log and a preset duration; Read the application call log whose corresponding generation time is within the data acquisition period, wherein the application call log is the log data collected by setting the embedding point in the vehicle computer standardized function interface that needs to be triggered when calling the application, or the log related to the calling application printed by calling the log function in the vehicle computer system; Searching the application call log for a log related to the abnormal application to obtain an application-related log; The application-related log is analyzed to determine the call information of the abnormal application.

5. The vehicle computer abnormality repair method according to claim 1, characterized in that: The calling of the abnormality repair interface corresponding to the abnormality type to repair the vehicle computer abnormality based on the file information of the abnormality-related file includes: Searching for interface information of an exception repair interface corresponding to the exception type in a repair knowledge base; Based on the file information of the exception-related file and the interface information, the exception repair interface corresponding to the exception type is called through the reflection mechanism to repair the vehicle computer exception.

6. The vehicle computer abnormality repair method according to claim 5, characterized in that: The interface information includes the class identifier of the interface, the interface name, the interface access path and the call parameter rules; The method of calling the abnormality repair interface corresponding to the abnormality type through a reflection mechanism based on the file information of the abnormality-related file and the interface information to repair the abnormality of the vehicle computer includes: Extracting the interface class identifier, interface name, interface access path and call parameter rules from the interface information; Using the reflection mechanism, the interface implementation instance corresponding to the abnormal repair interface is obtained according to the class identifier to which the interface belongs and the interface access path; Constructing interface call parameters according to the file information of the abnormal associated file and the call parameter rule; The interface implementation instance is accessed according to the interface name and the interface calling parameters to call the exception repair interface corresponding to the exception type to repair the vehicle computer exception.

7. The vehicle computer abnormality repair method according to any one of claims 1 to 6, characterized in that: The determining the exception type according to the exception associated file, the collection location and the exception identification code includes: Determine a suspected category according to the abnormality-related file, the collection location, and the abnormality identification code; Find the auxiliary judgment interface corresponding to the suspected category; Calling the auxiliary judgment interface to obtain auxiliary judgment information; The abnormality type is determined based on the auxiliary judgment information and the suspected category.

8. A vehicle computer abnormality repair device, characterized in that: The device comprises: A determination module, used to determine the abnormality-related file and the abnormality identification code according to the application abnormality log, wherein the application abnormality log includes the vehicle system log and the buried point collection data, wherein the buried point collection data is the data set for buried point collection in the vehicle standardized function interface; An extraction module, used to obtain a collection location corresponding to the application exception log; A classification module, used to determine the abnormality type according to the abnormality associated file, the collection location and the abnormality identification code; The repair module is used to call the abnormality repair interface corresponding to the abnormality type to repair the vehicle computer abnormality based on the file information of the abnormality-related file.

9. A vehicle abnormality repair device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the vehicle computer abnormality repair method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the vehicle computer abnormality repair method according to any one of claims 1 to 7 are implemented.

Images