Vehicle fault diagnosis method, electronic equipment and storage medium

Abstract

The invention discloses a vehicle fault diagnosis method, electronic equipment and a storage medium, and relates to the technical field of vehicle detection. Receiving a target vehicle fault diagnosis task which carries target fault diagnosis data and is fed back by the server side based on preset vehicle attribute information of different vehicle types and preset vehicle historical fault diagnosis data of different vehicle types, the target vehicle fault diagnosis task is used for representing a task for diagnosing a target fault component or a target fault environment in the vehicle end, and the target fault diagnosis data is used for representing an encrypted target fault diagnosis file; and in response to a target vehicle fault diagnosis task from the server side, performing fault diagnosis on the vehicle side based on a target fault diagnosis strategy in the target fault diagnosis data, determining a target fault diagnosis result, and feeding back the target fault diagnosis result to the server side. According to the embodiment of the invention, the method can meet the fault diagnosis demands of various different vehicle types, and improves the fault diagnosis flexibility.

Description

Technical Field

[0001] The present application relates to the field of vehicle detection technology, and in particular to a vehicle fault diagnosis method, electronic equipment and storage medium. Background Art

[0002] At present, with the development of society and the advancement of science and technology, the need for vehicle intelligence is becoming more and more widespread. Therefore, remote fault diagnosis of vehicles is becoming more and more important.

[0003] However, the remote fault diagnosis of traditional vehicles is mostly designed based on traditional architecture, which is mainly passive fault diagnosis based on solidified fault content. The fault diagnosis content is single and there are fewer active diagnosis states. Therefore, the single fault diagnosis content may not meet or be applicable to the special fault diagnosis needs of the vehicle. In the process of fault diagnosis, the diagnosis of some faults requires the help of diagnostic equipment, which leads to poor flexibility in fault diagnosis. Summary of the invention

[0004] The embodiments of the present application provide a vehicle fault diagnosis method, an electronic device and a storage medium. The embodiments provided by the present application solve the technical problem in the prior art that a single fault diagnosis content may not meet or be applicable to the special fault diagnosis needs of a vehicle and leads to poor flexibility in fault diagnosis. The embodiments provided by the present application can adapt to the fault diagnosis needs of a variety of different vehicle models while improving the flexibility of fault diagnosis.

[0005] In a first aspect of the embodiments of the present application, the embodiments of the present application provide a vehicle fault diagnosis method, which is applied to a vehicle side. The vehicle fault diagnosis method includes:

[0006] The target vehicle fault diagnosis task carrying the target fault diagnosis data is fed back by the receiving server based on the vehicle attribute information preset by different vehicle models and the vehicle historical fault diagnosis data preset by different vehicle models, wherein the target vehicle fault diagnosis task is used to characterize the task of diagnosing the target fault component or target fault environment in the vehicle end, and the target fault diagnosis data is used to characterize the target fault diagnosis file after encryption processing;

[0007] In response to the target vehicle fault diagnosis task from the server, the vehicle is diagnosed with a fault based on a target fault diagnosis strategy in the target fault diagnosis data, a target fault diagnosis result is determined, and the target fault diagnosis result is fed back to the server.

[0008] In a feasible implementation manner, in response to the target vehicle fault diagnosis task from the server, performing fault diagnosis on the vehicle based on the target fault diagnosis strategy in the target fault diagnosis data, determining a target fault diagnosis result, and feeding back the target fault diagnosis result to the server, includes:

[0009] Based on the current driving state of the vehicle end, determining whether there is a task being executed in the vehicle end;

[0010] If there is no task being executed in the vehicle end, the target vehicle fault diagnosis task from the server end is responded to, and the vehicle end is diagnosed with a fault based on the target fault diagnosis strategy in the target fault diagnosis data, a target fault diagnosis result is determined, and the target fault diagnosis result is fed back to the server end.

[0011] In a feasible implementation manner, the type of the target vehicle fault diagnosis task includes a target non-silent task, and if there is no task being executed in the vehicle end, responding to the target vehicle fault diagnosis task from the server end, and performing fault diagnosis on the vehicle end based on the target fault diagnosis strategy in the target fault diagnosis data, determining a target fault diagnosis result, and feeding back the target fault diagnosis result to the server end, includes:

[0012] If there is no task being executed in the vehicle end, in response to the target non-silent task from the server end, receiving authorization information sent by the target user;

[0013] After the authorization information is verified, determining whether various vehicle state parameters of the vehicle end under the current driving state meet the fault diagnosis conditions in the target fault diagnosis data;

[0014] If satisfied, then performing fault diagnosis on the vehicle end based on the target fault diagnosis strategy to determine a target fault diagnosis result;

[0015] The target fault diagnosis result is fed back to the service end.

[0016] In a feasible implementation manner, if the above conditions are met, then based on the target fault diagnosis strategy, a fault diagnosis is performed on the vehicle end to determine a target fault diagnosis result, including:

[0017] If the conditions are met, the target fault diagnosis data is decrypted based on a preset secret key rule to determine a target fault diagnosis file after decryption;

[0018] Perform fault diagnosis on the vehicle side according to the target fault diagnosis strategy and the target fault diagnosis file to determine a target fault diagnosis result.

[0019] In a feasible implementation manner, the target fault diagnosis strategy includes a preset electrical parameter threshold rule, and the fault diagnosis of the vehicle end is performed according to the target fault diagnosis strategy and the target fault diagnosis file to determine the target fault diagnosis result, including:

[0020] Based on the target fault diagnosis file, determining the electrical parameters collected by the vehicle end at each preset sensor;

[0021] Determining whether each of the electrical parameters satisfies the preset electrical parameter threshold rule, wherein the preset electrical parameter threshold rule is used to characterize the parameter range specified for each of the electrical parameters under a normal state;

[0022] If each of the electrical parameters satisfies the preset electrical parameter threshold rule, determining that the target fault diagnosis result of the vehicle end is that there is no fault;

[0023] If any of the electrical parameters does not satisfy the preset electrical parameter threshold rule, the target fault diagnosis result on the vehicle side is determined to be that the electrical parameter is faulty.

[0024] In a feasible implementation manner, after the authorization information is verified, after determining whether various vehicle state parameters of the vehicle end in the current driving state meet the target fault diagnosis strategy in the target fault diagnosis data, the vehicle diagnosis determination method further includes:

[0025] If the various vehicle state parameters of the vehicle end under the current driving state do not meet the fault diagnosis conditions in the target fault diagnosis data, determine whether the execution time of the target vehicle fault diagnosis task is greater than or equal to the preset task duration;

[0026] If not, re-determine whether various vehicle state parameters of the vehicle end under the current driving state meet the fault diagnosis conditions in the target fault diagnosis data;

[0027] If so, it is determined that the target vehicle fault diagnosis task on the vehicle side has failed to execute.

[0028] In a second aspect of the embodiment of the present application, the embodiment of the present application provides a vehicle fault diagnosis method, which is applied to a server, and the vehicle fault diagnosis method includes:

[0029] Receiving preset vehicle attribute information of different vehicle models and preset vehicle historical fault diagnosis data of the different vehicle models, wherein the vehicle historical fault diagnosis data includes vehicle historical fault diagnosis tasks and historical fault diagnosis strategies corresponding to the vehicle historical fault diagnosis tasks;

[0030] Based on the historical fault diagnosis strategies of the different vehicle models, the historical fault diagnosis tasks of the vehicles, and the vehicle attribute information, determine a target vehicle fault diagnosis task carrying target fault diagnosis data to be sent to the vehicle end, wherein the target fault diagnosis data includes a target fault diagnosis strategy corresponding to the target vehicle fault diagnosis task;

[0031] The target fault diagnosis result obtained based on the target fault diagnosis strategy is received after the vehicle side executes the target vehicle fault diagnosis task.

[0032] In a feasible implementation manner, the determining, based on the historical fault diagnosis strategies of the different vehicle models, the vehicle historical fault diagnosis tasks and the vehicle attribute information, the target vehicle fault diagnosis task carrying the target fault diagnosis data to be sent to the vehicle end includes:

[0033] Based on the historical fault diagnosis strategies of different vehicle models and the historical fault diagnosis tasks of the vehicles, determining the faulty components and fault environments of the vehicles of the different vehicle models;

[0034] The vehicles with the same faulty component or the same faulty environment are divided into a group, and the fault diagnosis types corresponding to the vehicles of different models are determined;

[0035] Based on each of the fault diagnosis types and the vehicle attribute information, a target vehicle fault diagnosis task carrying target fault diagnosis data is determined and sent to the vehicle end.

[0036] According to a third aspect of an embodiment of the present application, an embodiment of the present application provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor communicates with the memory through the bus, and the machine-readable instructions are executed by the processor as the vehicle fault diagnosis method described in the first aspect or the steps of the vehicle fault diagnosis method described in the first aspect.

[0037] In a fourth aspect of an embodiment of the present application, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the vehicle fault diagnosis method described in the first aspect or the steps of the vehicle fault diagnosis method described in the first aspect are executed.

[0038] The vehicle fault diagnosis method, electronic device and storage medium provided in the embodiments of the present application, compared with the prior art, the embodiments provided by the present application receive vehicle attribute information preset by the server based on different vehicle models and vehicle historical fault diagnosis data preset by different vehicle models, and feedback the target vehicle fault diagnosis task carrying the target fault diagnosis data and the corresponding target fault diagnosis data, and respond to the target vehicle fault diagnosis task from the server, and then perform fault diagnosis on the vehicle side based on the target fault diagnosis strategy in the target fault diagnosis data, determine the target fault diagnosis result, and feed back the target fault diagnosis result to the server. The embodiments provided by the present application determine the target vehicle fault diagnosis task based on the vehicle historical fault diagnosis data, which can adapt to the fault diagnosis needs of a variety of different vehicle models while improving the flexibility of fault diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A second flowchart of a vehicle fault diagnosis method provided in an embodiment of the present application;

[0040] Figure 2 A structural block diagram of a vehicle end provided in an embodiment of the present application;

[0041] Figure 3 A second flowchart of a vehicle fault diagnosis method provided in an embodiment of the present application;

[0042] Figure 4 A structural block diagram of a server provided in an embodiment of the present application;

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

[0044] Figure 2 and Figures 4 to 5 The corresponding relationship between the reference numerals and the names of the drawings is as follows:

[0045] 200 vehicle side; 210 diagnostic task management unit; 220 diagnostic task execution unit; 230 interface interaction unit; 240 decryption and signature verification unit; 250 diagnostic file download unit; 260 vehicle-cloud communication unit; 270 vehicle mode management unit; 400 server side; 410 vehicle management unit; 420 data management unit; 430 diagnostic sequence management unit; 440 diagnostic task management unit; 500 vehicle fault determination device; 510 determination module; 500 electronic device; 510 processor; 520 memory; 530 bus. DETAILED DESCRIPTION

[0046] In order to better understand the technical solutions provided by the embodiments of this specification, the technical solutions of the embodiments of this specification are described in detail below through the accompanying drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. In the absence of conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.

[0047] In this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of more restrictions, the elements limited by the statement "comprise one..." do not exclude the existence of other identical elements in the process, method, article or equipment including the elements. The term "more than two" includes two or more than two situations.

[0048] First, the applicable application scenarios of the present application are introduced. The embodiments provided in the present application are applicable to the field of vehicle detection technology.

[0049] At present, the remote fault diagnosis of traditional vehicles is mostly designed based on traditional architecture, which is mainly passive fault diagnosis based on solidified fault content. The fault diagnosis content is single, and there are fewer active diagnosis states. Therefore, the single fault diagnosis content may not meet or be applicable to the special fault diagnosis needs of the vehicle. In the process of fault diagnosis, the diagnosis of some faults requires the help of diagnostic equipment, which leads to poor flexibility in fault diagnosis.

[0050] Based on this, the embodiments of the present application provide a vehicle fault diagnosis method, an electronic device and a storage medium. The embodiments provided by the present application solve the technical problem in the prior art that a single fault diagnosis content may not be able to meet or be applicable to the special fault diagnosis needs of the vehicle and leads to poor flexibility in fault diagnosis. The embodiments provided by the present application can adapt to the fault diagnosis needs of a variety of different types of vehicles while improving the flexibility of fault diagnosis.

[0051] Figure 1 This is one of the flowcharts of a vehicle fault diagnosis method provided in an embodiment of the present application. Figure 1 As shown, the vehicle fault diagnosis method, applied to the vehicle side, includes the following steps:

[0052] S101. Receive a target vehicle fault diagnosis task carrying target fault diagnosis data fed back by a server based on preset vehicle attribute information of different vehicle models and preset vehicle historical fault diagnosis data of different vehicle models, wherein the target vehicle fault diagnosis task is used to characterize the task of diagnosing a target fault component or a target fault environment in the vehicle, and the target fault diagnosis data is used to characterize the target fault diagnosis file after encryption.

[0053] In this step, after sending the vehicle attribute information and the vehicle historical fault diagnosis data, the vehicle end in the embodiment provided by the present application receives the target vehicle fault diagnosis task and the corresponding target fault diagnosis data fed back by the server based on the vehicle attribute information and the vehicle historical fault diagnosis data, and determines whether the target vehicle fault diagnosis task conflicts with other tasks being performed by the retaining wall vehicle. If there is no conflict, the target vehicle fault diagnosis task for diagnosing the target fault component or target fault environment in the vehicle end is started.

[0054] It should be noted that the vehicle attribute information of different models in the embodiments provided in the present application includes but is not limited to the vehicle model information, the vehicle driving information and the management information of the electronic control unit (ECU) in vehicles of different models; the historical fault diagnosis data includes the historical fault diagnosis tasks of the vehicle and the historical fault diagnosis strategies corresponding to the historical fault diagnosis tasks of the vehicle, as well as the configuration field information of the vehicle fault diagnosis data and the preset key rules, that is, the preset security algorithm.

[0055] S102, in response to the target vehicle fault diagnosis task from the server, perform fault diagnosis on the vehicle based on the target fault diagnosis strategy in the target fault diagnosis data, determine the target fault diagnosis result, and feed back the target fault diagnosis result to the server.

[0056] In this step, after determining that the above-mentioned target vehicle fault diagnosis task can be executed (or executed preferentially), the corresponding target fault diagnosis data is downloaded from the server and the file integrity of the above-mentioned target fault diagnosis data is verified. When it is determined that the file of the above-mentioned target fault diagnosis data is complete, the vehicle side is diagnosed with faults based on the target fault diagnosis strategy in the above-mentioned target fault diagnosis data, and the corresponding fault diagnosis result of the vehicle side is determined. The target fault diagnosis result is then fed back to the server side or the user's mobile terminal, etc., to facilitate operation managers or users to view the corresponding fault-specific information in real time, thereby meeting the remote fault diagnosis needs of different architecture vehicles.

[0057] Exemplarily, step S102 includes the following sub-steps:

[0058] Sub-step 1021: Based on the current driving status of the vehicle, determine whether there is a task being executed in the vehicle.

[0059] In this step, after responding to the target vehicle fault diagnosis task from the service end, it is first necessary to determine whether there is a task being executed on the vehicle end. Specifically, it can be determined whether there is a task being executed based on data such as the current driving status of the vehicle end and the vehicle status of the vehicle end under the current driving status.

[0060] It should be noted that, in addition to the target vehicle fault diagnosis task, the tasks being executed in the embodiments provided in this application include but are not limited to audio and video entertainment tasks in the vehicle, the vehicle's Bluetooth connection tasks, and the vehicle's intelligent driving cruise tasks, etc.

[0061] Sub-step 1022: If there is no task being executed on the vehicle side, respond to the target vehicle fault diagnosis task from the server side, and perform fault diagnosis on the vehicle side based on the target fault diagnosis strategy in the target fault diagnosis data, determine the target fault diagnosis result, and feed back the target fault diagnosis result to the server side.

[0062] In this step, if there is an ongoing task on the vehicle side, the vehicle side needs to ignore the target vehicle fault diagnosis task and continue to complete the task being executed by the retaining wall; if there is no ongoing task on the vehicle side, the vehicle side determines to start executing the above-mentioned target vehicle fault diagnosis task. At this time, it is necessary to determine whether it is necessary to obtain the authorization of the target user driving the above-mentioned vehicle side according to the type of the target vehicle fault diagnosis task, and determine different fault diagnosis execution permissions according to different target vehicle fault diagnosis task types, and perform fault diagnosis on the vehicle side according to different fault diagnosis execution permissions and the target fault diagnosis strategy in the target fault diagnosis data, determine the target fault diagnosis result, and feed back the target fault diagnosis result to the server side.

[0063] It should be noted that the types of target vehicle fault diagnosis tasks in the embodiments provided in the present application include silent tasks and non-silent tasks.

[0064] Exemplarily, silent tasks and non-silent tasks are two different types of task processing methods in computer systems, operating systems, and applications. The main difference between them lies in whether they interact with users or produce visible user interface changes during execution. Silent tasks refer to tasks that are executed in the background without directly interacting with users. Such tasks usually do not attract the user's attention and do not change the current working environment or displayed content; while non-silent tasks refer to tasks that require interaction with users or produce significant user interface changes. Such tasks usually provide some form of feedback to users during execution and may require user input to continue.

[0065] Exemplarily, the type of the target vehicle fault diagnosis task includes a target non-silent task. If there is no task being executed in the vehicle end, responding to the target vehicle fault diagnosis task from the server end and performing fault diagnosis on the vehicle end based on the target fault diagnosis strategy in the target fault diagnosis data, determining the target fault diagnosis result, and feeding back the target fault diagnosis result to the server end, includes the following sub-steps:

[0066] Sub-step 1: If there is no task being executed in the vehicle side, then in response to the target non-silent task from the server side, receive the authorization information sent by the target user.

[0067] In this step, after determining that there is no task being executed on the vehicle side, the type of the above-mentioned target vehicle fault diagnosis task is judged. If the target vehicle fault diagnosis task is a target non-silent task, the vehicle side needs to send an authorization request to the user and receive the authorization information fed back by the user; if the type of the target vehicle fault diagnosis task is a target silent task, there is no need to send an authorization request to the user, and the conditional judgment of the target silent task will be directly entered.

[0068] In the above description, the target silent task in the embodiments provided by the present application may be specifically but not limited to a software upgrade task.

[0069] It should be noted that the user authorization information in the embodiment provided in the present application means that the user can be authorized to access and perform the target vehicle fault diagnosis task. The purpose of sending the authorization request is to make sensitive data open only to authorized personnel through a reasonable authorization mechanism. Specific user authorization refers to the process of granting specific permissions to the user based on the confirmation of the user's identity and according to preset rules.

[0070] It should be noted that the vehicle end in the embodiment provided in the present application is the vehicle to which the server sends the diagnostic data request.

[0071] Sub-step 2: After the authorization information is verified, determine whether various vehicle status parameters at the vehicle end under the current driving state meet the fault diagnosis conditions in the target fault diagnosis data.

[0072] In this step, the embodiment provided in the present application determines whether various vehicle status parameters on the vehicle side meet the fault diagnosis conditions under the current driving state after determining that the user's authorization information has been verified.

[0073] It should be noted that the fault diagnosis conditions in the embodiments provided in the present application can be customized and used according to different application scenarios and usage environments. Here, the fault diagnosis conditions in the embodiments provided in the present application can be specifically but not limited to being set as a vehicle speed limit threshold and a vehicle driving mode, etc. It is assumed that the vehicle speed limit threshold in the preset fault diagnosis conditions in the embodiments provided in the present application is 10km / h.

[0074] Sub-step 3: If the conditions are met, the target fault diagnosis data is decrypted based on the preset secret key rule to determine the target fault diagnosis file after decryption.

[0075] In this step, when it is determined that various vehicle status parameters of the vehicle end under the current driving state meet the fault diagnosis conditions preset in the target fault diagnosis strategy in the target fault diagnosis data, such as: the vehicle speed is less than the speed limit threshold of 10km / h, or the vehicle is in non-driving mode, the vehicle end is switched to the vehicle fault diagnosis mode, and the target vehicle fault diagnosis task is started. Before using the target fault diagnosis data, the target fault diagnosis data must be decrypted according to the preset secret key rules to generate a decrypted target fault diagnosis file.

[0076] Sub-step 4: perform fault diagnosis on the vehicle side according to the target fault diagnosis strategy and the target fault diagnosis file, determine the target fault diagnosis result, and feed back the target fault diagnosis result to the server side.

[0077] In this step, the target fault diagnosis strategy in the embodiment provided by the present application includes a preset electrical parameter threshold rule. Therefore, the embodiment provided by the present application first determines the electrical parameters collected by the vehicle end at each preset sensor in the target fault diagnosis file, and then compares each electrical parameter with the preset electrical parameter threshold rule of the corresponding parameter type to determine whether each electrical parameter satisfies the preset electrical parameter threshold rule, that is, whether each electrical parameter is within the parameter range specified by the preset electrical parameter threshold rule. If each of the electrical parameters satisfies the corresponding preset electrical parameter threshold rule, that is, whether each electrical parameter is within the parameter range specified by the preset electrical parameter threshold rule, then the target fault diagnosis result of the vehicle end is determined to be that there is no fault; if there is any electrical parameter on the vehicle end that does not satisfy the corresponding preset electrical parameter threshold rule, then the target fault diagnosis result of the vehicle end is determined to be that there is a fault in the electrical parameter.

[0078] In the above, the electrical parameters include but are not limited to electrical parameters such as temperature, pressure and rotation speed; and the preset electrical parameter threshold rules corresponding to different types of electrical parameters can be customized according to different application scenarios and requirements.

[0079] It should be noted that when performing fault diagnosis on the vehicle side according to the target fault diagnosis strategy, it is necessary to parse the open diagnostic data exchange format file (Open Diagnostic Data Exchange Format, ODX) and the open task exchange format file (Open Test Sequence Exchange Format, OTX) in the target fault diagnosis file, and perform fault diagnosis on the vehicle side according to the parsing results, and determine whether the fault diagnosis is successful. After the fault diagnosis is successful, determine the target fault diagnosis result and feed back the target fault diagnosis result to the server side; after the fault diagnosis fails, feed back the fault diagnosis failure information to the server side and the vehicle side so that the user can view it.

[0080] Sub-step 5: If various vehicle status parameters under the current driving state of the vehicle end do not satisfy the target fault diagnosis strategy in the target fault diagnosis data, determine whether the execution time of the target vehicle fault diagnosis task is greater than or equal to the preset task duration.

[0081] In this step, when it is determined that various vehicle state parameters at the vehicle end in the current driving state do not meet any preset fault diagnosis conditions in the target fault diagnosis strategy, such as: the vehicle speed is greater than or equal to the speed limit threshold of 10km / h, or the vehicle is in driving mode, it is necessary to determine whether the vehicle end can continue to perform fault diagnosis based on the execution time of the target vehicle fault diagnosis task. Specifically, it can be: determine whether the execution time of the target vehicle fault diagnosis task is greater than or equal to the preset task duration.

[0082] Sub-step 6: If not, re-determine whether various vehicle status parameters at the vehicle end under the current driving state meet the fault diagnosis conditions in the target fault diagnosis data.

[0083] In this step, when it is determined that the execution time of the target vehicle fault diagnosis task is less than the preset task duration, the fault diagnosis safety condition is re-determined.

[0084] Sub-step 7: If yes, it is determined that the target vehicle fault diagnosis task on the vehicle side has failed to execute.

[0085] Figure 2 This is a structural block diagram of a vehicle end provided by an embodiment of the present application. Figure 2 As shown, the vehicle end 200 includes: a diagnostic task management unit 210, a diagnostic task execution unit 220, an interface interaction unit 230, a decryption and signature verification unit 240, a diagnostic file download unit 250, a vehicle-cloud communication unit 260 and a vehicle mode management unit 270. The diagnostic task execution unit 220, the interface interaction unit 230, the diagnostic file download unit 250, the vehicle-cloud communication unit 260 and the vehicle mode management unit 270 are all communicatively connected to the diagnostic task management unit 210, and the decryption and signature verification unit 240 is communicatively connected to the diagnostic task execution unit 220.

[0086] Here, the vehicle-side terminal will execute at least one target vehicle fault diagnosis task in sequence according to a preset execution order.

[0087] It should be noted that the vehicle-cloud communication unit 260 can specifically be: receiving diagnostic data requests from the server and sending the above diagnostic data requests to the diagnostic task management unit 210; and reporting fault diagnosis results, etc., to achieve interaction between the vehicle 200 and the server.

[0088] Exemplarily, the diagnostic file download unit 250 is specifically used to receive the file download instruction sent by the diagnostic task management unit 210 after the diagnostic task management unit 210 receives the target vehicle fault diagnosis task fed back by the server and the diagnostic task management unit 210 determines that there is no task being executed on the vehicle side, start downloading the target fault diagnosis data sent by the server, and feed back the corresponding download progress to the feedback end, and after the download is completed, send a download completion instruction to the diagnostic task management unit 210.

[0089] The target fault diagnosis data downloaded by the diagnosis file download unit 250 includes various types of files such as diagnosis description files, flashing software, OTX, ODX, and Process Description eXchange format (PDX).

[0090] In the above, the diagnostic task management unit 210, as the core unit of the vehicle end 200, is mainly responsible for the management of the target fault diagnosis task, which specifically includes control functions such as starting and scheduling the task and interacting with the interface interaction unit 230.

[0091] The diagnostic task management unit 210 is specifically used to, in response to a diagnostic data request from a server, send vehicle attribute information of different vehicle models and vehicle historical fault diagnosis data of different vehicle models to the server, and receive a target vehicle fault diagnosis task and corresponding target fault diagnosis data fed back by the server based on the vehicle attribute information and the vehicle historical fault diagnosis data, wherein the target vehicle fault diagnosis task is used to characterize the task of diagnosing a target fault component or a target fault environment in the vehicle; in response to a target vehicle fault diagnosis task from the server, perform fault diagnosis on the vehicle based on a target fault diagnosis strategy in the target fault diagnosis data, determine a target fault diagnosis result, and feed back the target fault diagnosis result to the server.

[0092] Exemplarily, the interface interaction unit 230 is used to receive a user authorization request sent by the diagnostic task management unit 210 after the diagnostic task management unit 210 determines that the type of the target vehicle fault diagnosis task is a non-silent task, and according to the above user authorization request, send the user's authorization permission or authorization disapproval information to the diagnostic task management unit 210, so as to obtain non-silent task permissions.

[0093] The vehicle mode management unit 270 is specifically used to receive the fault diagnosis condition judgment request sent by the diagnostic task management unit 210 after receiving the authorization information sent by the target user, and based on the above fault diagnosis condition judgment request, determine whether various vehicle state parameters under the current driving state of the vehicle side meet the target fault diagnosis strategy in the target fault diagnosis data, so as to realize the management of the vehicle's fault diagnosis mode and ensure that the vehicle enters the diagnostic state in a safe mode.

[0094] In the above, the diagnostic task execution unit 220 in the embodiment provided by the present application is specifically used to determine in the vehicle mode management unit 270 whether various vehicle status parameters on the vehicle side under the current driving state satisfy the target fault diagnosis strategy in the target fault diagnosis data, determine to execute the target vehicle fault diagnosis task on the vehicle side, and parse the ODX file and the OTX file to realize the diagnosis of the controller area network controller and the Ethernet intelligent electronic control unit (Electronic Control Unit, electronic control unit, ECU).

[0095] The decryption and signature verification unit 240 is used to receive the decryption and verification operation sent by the diagnostic task execution unit 220 before executing the target vehicle fault diagnosis task on the vehicle side to ensure the information security of the fault diagnosis data.

[0096] Here, the communication between the various units in the embodiments provided in the present application is not affected by the deployment, so decoupling between the various units can be achieved.

[0097] Compared with the prior art, the vehicle end 200 provided in the embodiment of the present application is applicable to the electrical architecture platforms of different vehicle models and can execute the target vehicle fault diagnosis tasks issued by the server.

[0098] The vehicle fault diagnosis method provided in the embodiment of the present application is applied to the vehicle side 200. Compared with the prior art, the embodiment provided in the present application receives the target vehicle fault diagnosis task and the corresponding target fault diagnosis data fed back by the server side based on the vehicle attribute information and the vehicle's historical fault diagnosis data, and responds to the target vehicle fault diagnosis task from the server side, and then performs fault diagnosis on the vehicle side based on the target fault diagnosis strategy in the target fault diagnosis data, determines the target fault diagnosis result, and feeds back the target fault diagnosis result to the server side. The embodiment provided in the present application determines the target vehicle fault diagnosis task based on the vehicle's historical fault diagnosis data, which improves the flexibility of fault diagnosis while being able to adapt to the fault diagnosis needs of a variety of different vehicle models.

[0099] Figure 3 This is a flowchart of a vehicle fault diagnosis method provided in an embodiment of the present application. Figure 3 As shown, the vehicle fault diagnosis method, applied to the server, includes the following steps:

[0100] S301. Receive preset vehicle attribute information of different vehicle models and preset vehicle historical fault diagnosis data of different vehicle models, wherein the vehicle historical fault diagnosis data includes vehicle historical fault diagnosis tasks and historical fault diagnosis strategies corresponding to the vehicle historical fault diagnosis tasks.

[0101] Exemplarily, the server provided in the present application receives vehicle attribute information of different vehicle models and vehicle historical fault diagnosis data of different vehicle models sent by the vehicle end.

[0102] It should be noted that the vehicle attribute information of different models in this embodiment includes but is not limited to the vehicle model information, the vehicle driving information and the management information of the Electronic Control Unit (ECU) in vehicles of different models; the historical fault diagnosis data includes the historical fault diagnosis tasks of the vehicle and the historical fault diagnosis strategies corresponding to the historical fault diagnosis tasks of the vehicle, as well as the configuration field information of the vehicle fault diagnosis data and the preset key rules, that is, the preset security algorithm.

[0103] S302. Based on the historical fault diagnosis strategies of different vehicle models, the historical fault diagnosis tasks of the vehicle and the vehicle attribute information, determine the target vehicle fault diagnosis task carrying the target fault diagnosis data to be sent to the vehicle end, wherein the target fault diagnosis data includes the target fault diagnosis strategy corresponding to the target vehicle fault diagnosis task.

[0104] Exemplarily, the embodiment provided by the present application uses historical fault diagnosis strategies and vehicle historical fault diagnosis tasks of different vehicle models sent from the vehicle end to determine the faulty components and fault environments of vehicles under different vehicle models, and then divides the vehicles with the same faulty components or the same fault environment into a group, determines the fault diagnosis types corresponding to the vehicles under different vehicle models, and regroups the fault diagnosis types of the vehicles. Then, based on each fault diagnosis type and vehicle attribute information, determines the target vehicle fault diagnosis task carrying the target fault diagnosis data to be sent to the vehicle end.

[0105] It should be noted that the embodiment provided in the present application specifically divides vehicles of different models that have the same temperature fault into a group. At this time, although the vehicles with temperature faults may include vehicles of multiple different models, they still belong to the same target vehicle fault diagnosis task.

[0106] S303, after the receiving vehicle performs the target vehicle fault diagnosis task, the target fault diagnosis result obtained based on the target fault diagnosis strategy is sent.

[0107] Figure 4 This is a structural block diagram of a server 400 provided in an embodiment of the present application. Figure 4 As shown, the server 400 includes: a vehicle management unit 410 , a data management unit 420 , a diagnostic sequence management unit 430 and a diagnostic task management unit 440 .

[0108] The vehicle management unit 410 is used to receive preset vehicle attribute information of different vehicle models and preset vehicle historical fault diagnosis data of different vehicle models, wherein the vehicle historical fault diagnosis data includes vehicle historical fault diagnosis tasks and historical fault diagnosis strategies corresponding to the vehicle historical fault diagnosis tasks.

[0109] It should be noted that the vehicle management unit 410 is specifically responsible for managing the model, vehicle attribute information, safety algorithm and configuration word information of the connected vehicles, as well as the historical fault diagnosis data of vehicles of different models, and determining the faulty components and fault environments of vehicles of different models, and then dividing the vehicles with the same faulty components or the same fault environment into a group to group the vehicles by task type.

[0110] The data management unit 420 is responsible for managing database files in PDX, ODX and other formats for use in compiling diagnostic sequences.

[0111] The diagnostic sequence management unit 430 is used to determine the target vehicle fault diagnosis task carrying the target fault diagnosis data to be sent to the vehicle end based on the historical fault diagnosis strategies of different vehicle models, the historical fault diagnosis tasks of the vehicle and the vehicle attribute information, wherein the target fault diagnosis data includes the target fault diagnosis strategy corresponding to the target vehicle fault diagnosis task.

[0112] It should be noted that the diagnostic sequence management unit 430 is specifically used to determine the vehicle diagnostic sequence and corresponding diagnostic files of different vehicles based on the needs of vehicle services, wherein the diagnostic sequence includes a conventional diagnostic sequence and a software upgrade sequence.

[0113] The diagnostic task management unit 440 receives a target fault diagnosis result obtained based on a target fault diagnosis strategy and sent by the vehicle end after executing the target vehicle fault diagnosis task.

[0114] It should be noted that the diagnostic task management unit 440 is specifically responsible for issuing and managing the target vehicle diagnostic tasks and the diagnostic files corresponding to the target vehicle diagnostic tasks to achieve fault diagnosis on the vehicle side.

[0115] Here, the number of vehicle ends in the embodiment provided in this application is at least one.

[0116] Compared with the prior art, the server 400 provided in the embodiment of the present application can meet the fault diagnosis needs of different target vehicles, and the present application can be applied to different types of fault diagnosis files, thereby realizing remote fault diagnosis matching a variety of different vehicle models, greatly improving the flexibility of fault diagnosis, and meeting the remote fault diagnosis business scenario requirements in various scenarios.

[0117] The server 400 provided in the embodiment of the present application is compared with the prior art. After sending a diagnostic data request to the vehicle side, the embodiment provided by the present application receives vehicle attribute information of different vehicle models and vehicle historical fault diagnosis data of different vehicle models sent by the vehicle side, and determines the target vehicle fault diagnosis task and the corresponding target fault diagnosis data to be sent to the vehicle side based on the historical fault diagnosis strategy of different vehicle models, the vehicle historical fault diagnosis task and the vehicle attribute information sent by the vehicle side, and then receives the target fault diagnosis result obtained based on the target fault diagnosis strategy sent by the vehicle side after executing the target vehicle fault diagnosis task. The embodiment provided by the present application determines the target vehicle fault diagnosis task based on the vehicle historical fault diagnosis data, which can adapt to the fault diagnosis needs of various different vehicle models while improving the flexibility of fault diagnosis.

[0118] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, the electronic device 500 includes a processor 510 , a memory 520 , and a bus 530 .

[0119] The memory 520 stores machine-readable instructions executable by the processor 510. When the electronic device 500 is running, the processor 510 communicates with the memory 520 via the bus 530. When the machine-readable instructions are executed by the processor 510, the above-mentioned Figure 1 The vehicle fault diagnosis method in the method embodiment shown or Figure 3 The specific implementation of the steps of the vehicle fault diagnosis method in the method embodiment shown can be found in the method embodiment, and will not be repeated here.

[0120] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 The vehicle fault diagnosis method in the method embodiment shown or Figure 3 The specific implementation of the steps of the vehicle fault diagnosis method in the method embodiment shown can be found in the method embodiment, which will not be repeated here.

[0121] The present application also provides a computer program product, including a computer program, which can be executed by a processor as described above. Figure 1 The vehicle fault diagnosis method in the method embodiment shown or Figure 3 The specific implementation of the steps of the vehicle fault diagnosis method in the method embodiment shown can be found in the method embodiment, which will not be repeated here.

[0122] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0123] It should be noted that in the above embodiments, the description of each embodiment has its own emphasis, and for parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0124] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-readable program code.

[0125] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0126] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0127] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0128] An embodiment of the present application also provides a computer program product, which includes computer software instructions. When the computer software instructions are executed on a processing device, the processing device executes the process of the vehicle fault diagnosis method.

[0129] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integration. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.

[0130] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

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

[0134] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

[0135] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

[0136] Although the preferred embodiments of this specification have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of this specification.

[0137] Obviously, those skilled in the art can make various changes and modifications to this specification without departing from the spirit and scope of this specification. Thus, if these modifications and variations of this specification fall within the scope of the claims of this specification and their equivalents, this specification is also intended to include these modifications and variations.

Claims

1. A vehicle fault diagnosis method, characterized in that: Applied to the vehicle side, the vehicle fault diagnosis method includes: The target vehicle fault diagnosis task carrying the target fault diagnosis data is fed back by the receiving server based on the vehicle attribute information preset by different vehicle models and the vehicle historical fault diagnosis data preset by different vehicle models, wherein the target vehicle fault diagnosis task is used to characterize the task of diagnosing the target fault component or target fault environment in the vehicle end, and the target fault diagnosis data is used to characterize the target fault diagnosis file after encryption processing; In response to the target vehicle fault diagnosis task from the server, the vehicle is diagnosed with a fault based on a target fault diagnosis strategy in the target fault diagnosis data, a target fault diagnosis result is determined, and the target fault diagnosis result is fed back to the server.

2. The vehicle fault diagnosis method according to claim 1, characterized in that: The method of responding to the target vehicle fault diagnosis task from the server, performing fault diagnosis on the vehicle based on the target fault diagnosis strategy in the target fault diagnosis data, determining a target fault diagnosis result, and feeding back the target fault diagnosis result to the server includes: Based on the current driving state of the vehicle end, determining whether there is a task being executed in the vehicle end; If there is no task being executed in the vehicle end, the target vehicle fault diagnosis task from the server end is responded to, and the vehicle end is diagnosed with a fault based on the target fault diagnosis strategy in the target fault diagnosis data, a target fault diagnosis result is determined, and the target fault diagnosis result is fed back to the server end.

3. The vehicle fault diagnosis method according to claim 2, characterized in that: The type of the target vehicle fault diagnosis task includes a target non-silent task. If there is no task being executed in the vehicle end, responding to the target vehicle fault diagnosis task from the server end and performing fault diagnosis on the vehicle end based on a target fault diagnosis strategy in the target fault diagnosis data, determining a target fault diagnosis result, and feeding back the target fault diagnosis result to the server end, includes: If there is no task being executed in the vehicle end, in response to the target non-silent task from the server end, receiving authorization information sent by the target user; After the authorization information is verified, determining whether various vehicle state parameters of the vehicle end under the current driving state meet the fault diagnosis conditions in the target fault diagnosis data; If satisfied, then performing fault diagnosis on the vehicle end based on the target fault diagnosis strategy to determine a target fault diagnosis result; The target fault diagnosis result is fed back to the service end.

4. The vehicle fault diagnosis method according to claim 3, characterized in that: If the above conditions are met, the vehicle-side fault diagnosis is performed based on the target fault diagnosis strategy to determine the target fault diagnosis result, including: If the conditions are met, the target fault diagnosis data is decrypted based on a preset secret key rule to determine a target fault diagnosis file after decryption; Perform fault diagnosis on the vehicle end according to the target fault diagnosis strategy and the target fault diagnosis file to determine a target fault diagnosis result.

5. The vehicle fault diagnosis method according to claim 4, characterized in that: The target fault diagnosis strategy includes a preset electrical parameter threshold rule, and the fault diagnosis of the vehicle end is performed according to the target fault diagnosis strategy and the target fault diagnosis file to determine the target fault diagnosis result, including: Based on the target fault diagnosis file, determining the electrical parameters collected by the vehicle end at each preset sensor; Determining whether each of the electrical parameters satisfies the preset electrical parameter threshold rule, wherein the preset electrical parameter threshold rule is used to characterize the parameter range specified for each of the electrical parameters under a normal state; If each of the electrical parameters satisfies the preset electrical parameter threshold rule, determining that the target fault diagnosis result of the vehicle end is that there is no fault; If any of the electrical parameters does not satisfy the preset electrical parameter threshold rule, the target fault diagnosis result on the vehicle side is determined to be that the electrical parameter is faulty.

6. The method for determining vehicle diagnosis according to claim 3, characterized in that: After the authorization information is verified, after determining whether various vehicle state parameters of the vehicle end in the current driving state meet the target fault diagnosis strategy in the target fault diagnosis data, the vehicle diagnosis determination method further includes: If the various vehicle state parameters of the vehicle end under the current driving state do not meet the fault diagnosis conditions in the target fault diagnosis data, determine whether the execution time of the target vehicle fault diagnosis task is greater than or equal to the preset task duration; If not, re-determine whether various vehicle state parameters of the vehicle end under the current driving state meet the fault diagnosis conditions in the target fault diagnosis data; If so, it is determined that the target vehicle fault diagnosis task on the vehicle side has failed to execute.

7. A vehicle fault diagnosis method, characterized in that: Applied to the server, the vehicle fault diagnosis method includes: Receiving preset vehicle attribute information of different vehicle models and preset vehicle historical fault diagnosis data of the different vehicle models, wherein the vehicle historical fault diagnosis data includes vehicle historical fault diagnosis tasks and historical fault diagnosis strategies corresponding to the vehicle historical fault diagnosis tasks; Based on the historical fault diagnosis strategies of the different vehicle models, the historical fault diagnosis tasks of the vehicles, and the vehicle attribute information, determine a target vehicle fault diagnosis task carrying target fault diagnosis data to be sent to the vehicle end, wherein the target fault diagnosis data includes a target fault diagnosis strategy corresponding to the target vehicle fault diagnosis task; The target fault diagnosis result obtained based on the target fault diagnosis strategy is received after the vehicle side executes the target vehicle fault diagnosis task.

8. The vehicle fault diagnosis method according to claim 7, characterized in that: The determining, based on the historical fault diagnosis strategies of the different vehicle models, the vehicle historical fault diagnosis tasks and the vehicle attribute information, of a target vehicle fault diagnosis task carrying target fault diagnosis data to be sent to the vehicle end includes: Based on the historical fault diagnosis strategies of different vehicle models and the historical fault diagnosis tasks of the vehicles, determining the faulty components and fault environments of the vehicles of the different vehicle models; The vehicles with the same faulty component or the same faulty environment are divided into a group, and the fault diagnosis types corresponding to the vehicles of different models are determined; Based on each of the fault diagnosis types and the vehicle attribute information, a target vehicle fault diagnosis task carrying target fault diagnosis data is determined and sent to the vehicle end.

9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and the machine-readable instructions are executed by the processor to perform the steps of the vehicle fault diagnosis method described in any one of claims 1 to 6 or the vehicle fault diagnosis method described in any one of claims 7 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the vehicle fault diagnosis method as described in any one of claims 1 to 6 or the vehicle fault diagnosis method as described in any one of claims 7 to 8 are executed.

Images