Vehicle fault detection method, device, equipment and storage medium

Abstract

The application relates to a vehicle fault detection method, device and equipment and a storage medium, and relates to the technical field of fault detection. The method comprises the following steps: obtaining the device identifier of a to-be-detected vehicle-mounted device in a target vehicle. According to the device identifier of the to-be-detected vehicle-mounted device, the first twin device and the second twin device corresponding to the to-be-detected vehicle-mounted device are determined. The node type of the first twin device in a preset digital twin system model is determined. According to the node type, the first parameter information of the first twin device and the second parameter information of the second twin device are obtained. If the first parameter information is different from the second parameter information, target detection information is generated, and the target detection information is used for indicating that the to-be-detected vehicle-mounted device has a fault hidden danger. Therefore, the fault detection efficiency of the vehicle-mounted device in the vehicle can be improved.

Description

Technical Field

[0001] This application relates to the field of fault detection technology, specifically to a vehicle fault detection method, apparatus, equipment, and storage medium. Background Technology

[0002] As an indispensable means of transportation in people's daily lives, vehicles are equipped with various onboard devices (such as radar, cameras, and audio systems) to meet users' driving needs. However, with the increasing number of onboard devices, their operating states differ, leading to higher demands for their management. For example, fault detection of onboard devices in vehicles is crucial.

[0003] Currently, fault detection of on-board equipment in vehicles typically requires an offline testing process. This involves vehicle repair personnel identifying potentially faulty on-board equipment based on user descriptions of the malfunction and their own experience. The faulty equipment is then verified through a substitution method (replacing potentially faulty equipment with known working equipment). After multiple verifications, the faulty equipment is finally identified. However, this approach requires manual intervention, resulting in low efficiency. Therefore, improving the efficiency of fault detection for on-board equipment in vehicles is a pressing technical challenge. Summary of the Invention

[0004] This application provides a vehicle fault detection method, apparatus, device, and storage medium to at least solve the technical problem in the related art of how to improve the efficiency of fault detection for on-board equipment in vehicles. The technical solution of this application is as follows:

[0005] According to the first aspect of this application, a vehicle fault detection method is provided, comprising: a vehicle fault detection device (hereinafter referred to as "fault detection device") acquiring the device identifier of an on-board device to be detected in a target vehicle.

[0006] The fault detection device identifies a first twin device and a second twin device corresponding to the on-board unit under test based on the device identifier. The first twin device is the digital twin device corresponding to the on-board unit under test in a preset digital twin system model, and the second twin device is the digital twin device constructed based on the initial data of the on-board unit under test. The preset digital twin system model includes digital twin devices corresponding to any on-board unit in the target vehicle. The fault detection device determines the node type of the first twin device in the preset digital twin system model. Based on the node type, the fault detection device obtains the first parameter information of the first twin device and the second parameter information of the second twin device. If the first parameter information and the second parameter information are different, the fault detection device generates target detection information, which is used to indicate that there is a potential fault in the on-board unit under test.

[0007] Based on the aforementioned technical means, the fault detection device can determine a first twin device that maintains data synchronization with the on-board equipment under test within a preset digital twin system model corresponding to the target vehicle, and obtain the first parameter information of the first twin device in the test state. Next, the fault detection device can construct a second twin device corresponding to the on-board equipment under test based on the initial data of the on-board equipment under test, and substitute the second twin device into the preset digital twin system model corresponding to the target vehicle to obtain the second parameter information of the second twin device in the normal state. Then, the fault detection device can determine whether there is a potential fault in the on-board equipment under test based on the comparison result between the first and second parameter information. If the first and second parameter information are different, the fault detection device generates target detection information to indicate that there is a potential fault in the on-board equipment under test. In other words, when a fault occurs, such as a fault symptom or a fault code is detected, a digital twin of the vehicle component can be used to replace the physical entity for troubleshooting and locating the faulty component. This component is usually an electrical component capable of generating or processing digital signals. Thus, the replacement of physical components can be avoided, improving the efficiency of fault detection. Furthermore, during the acquisition of the first and second parameter information, the fault detection device can determine the acquisition strategy for the first and second parameter information by identifying the node type of the first twin device in the preset digital twin system model. In other words, because the node types of different devices in the data transmission link of the digital twin system model may differ, the fault detection standards between devices will also differ; that is, devices with different node types will refer to different parameter information during fault detection. Therefore, by determining the node type of the device, suitable reference data can be provided for device fault detection, improving the accuracy of the fault detection results.

[0008] In one possible implementation, both the first parameter information and the second parameter information include sub-parameter information corresponding to multiple preset times within a preset time period. The method further includes: if the first parameter information and the second parameter information are different, and the first quantity is less than a first preset quantity threshold, then for each preset time, the fault detection device determines a first difference based on the preset time, the first parameter information, and the second parameter information to obtain multiple first differences. The first difference is the difference between two sub-parameter information corresponding to the same preset time in the first parameter information and the second parameter information. One first difference corresponds to one preset time, and the first quantity is the number of preset times within the preset time period. The fault detection device sums the multiple first differences to determine the target deviation value between the first parameter information and the second parameter information. The above-mentioned method of "generating target detection information by the fault detection device" includes: if the target deviation value is greater than or equal to a preset deviation threshold, the fault detection device generates target detection information.

[0009] Based on the aforementioned technical methods, since random parameters may be generated during actual operation, the parameters of the equipment may differ even under two identical operating environments. Therefore, when it is determined that the first parameter information and the second parameter information are different, the fault detection device can determine the degree of deviation between the first and second parameter information by accumulating the differences between the sub-parameter information corresponding to each preset time in the first and second parameter information. Furthermore, by comparing the degree of deviation between the first and second parameter information with a threshold, it can determine whether there is a potential fault in the on-board equipment under test. This improves the accuracy of fault detection results.

[0010] In one possible implementation, both the first parameter information and the second parameter information include sub-parameter information corresponding to multiple preset times within a preset time period. The method further includes: if the first parameter information and the second parameter information are different, and the first quantity is greater than or equal to a first preset quantity threshold, then the fault detection device obtains a target time from the multiple preset times, where the target time is the last time among the multiple preset times, and the first quantity is the number of preset times within the preset time period. The fault detection device determines a second difference based on the target time, the first parameter information, and the second parameter information, where the second difference is the difference between the two sub-parameter information corresponding to the target time in the first parameter information and the second parameter information. The above-mentioned method of "generating target detection information by the fault detection device" includes: if the second difference is greater than or equal to a preset difference threshold, then the fault detection device generates target detection information.

[0011] Based on the aforementioned technical means, the fault detection device can determine whether the vehicle-mounted equipment under test has a potential fault when the first parameter information and the second parameter information are different, and when there are a large number of preset time points. This is achieved by comparing the difference between the sub-parameter information corresponding to any preset time point in the first and second parameter information using a threshold comparison. This reduces the amount of information processed and improves fault detection efficiency. Furthermore, the fault detection device can also determine whether the vehicle-mounted equipment under test has a potential fault by comparing the difference between the sub-parameter information corresponding to the last preset time point in the first and second parameter information using a threshold comparison. In other words, the fault detection device can determine whether the equipment has a potential fault based on parameter information after the equipment has been running for a period of time. This improves fault detection efficiency while ensuring the accuracy of the fault detection results.

[0012] In one possible implementation, the method of "the fault detection device obtaining first parameter information of the first twin device and second parameter information of the second twin device according to the node type" includes: if the node type is the starting node, the fault detection device obtains first parameter information and second parameter information based on a preset time period, wherein the first parameter information is parameter information generated by the first twin device within the preset time period, and the second parameter information is parameter information generated by the second twin device within the preset time period.

[0013] Based on the aforementioned technical means, the parameter information referenced by the device with node type "starting node" during fault detection is the parameter information it generates itself. The fault detection device can obtain first and second parameter information by collecting parameter information generated by the first twin device within a preset time period and parameter information generated by the second twin device within the same preset time period. This provides a suitable data foundation for subsequent fault detection of the on-board equipment under test, improving the accuracy of the fault detection results.

[0014] In one possible implementation, the method described above, which involves "the fault detection device acquiring first parameter information of the first twin device and second parameter information of the second twin device based on the node type," includes: if the node type is an end node, the fault detection device determines the upstream twin device of the first twin device in a preset digital twin system model. The fault detection device acquires third parameter information based on a preset time period, where the third parameter information is the parameter information sent by the upstream twin device to the first twin device within the preset time period. The fault detection device inputs the third parameter information into the first twin device to acquire first parameter information, where the first parameter information is the parameter information generated by the first twin device based on the third parameter information. The fault detection device inputs the third parameter information into the second twin device to acquire second parameter information, where the second parameter information is the parameter information generated by the second twin device based on the third parameter information.

[0015] According to the aforementioned technical means, the parameter information referenced by a device with a node type of "end node" during fault detection is the parameter information generated by itself in response to the upstream device. The fault detection device can identify the upstream twin device adjacent to the first twin device in the target data transmission link of the preset digital twin system model, and collect the third parameter information sent by the upstream twin device to the first twin device within a preset time period. Then, the fault detection device can input the third parameter information into both the first and second twin devices, collecting the parameter information generated by the first and second twin devices based on the third parameter information, to obtain the first and second parameter information. This provides a suitable data foundation for subsequent fault detection of the on-board equipment under test, improving the accuracy of the fault detection results.

[0016] In one possible implementation, the method described above, which involves "the fault detection device acquiring first parameter information of the first twin device and second parameter information of the second twin device based on the node type," includes: if the node type is a relay node, the fault detection device determines the upstream and downstream twin devices of the first twin device in a preset digital twin system model. The fault detection device acquires third parameter information based on a preset time period, whereby the third parameter information is the parameter information sent by the upstream twin device to the first twin device within the preset time period. The fault detection device inputs the third parameter information into the first twin device to acquire first parameter information, whereby the first twin device sends parameter information to the downstream twin device based on the third parameter information. The fault detection device inputs the third parameter information into the second twin device to acquire second parameter information, whereby the second twin device sends parameter information to the downstream twin device based on the third parameter information.

[0017] According to the aforementioned technical means, the parameter information referenced by a device with a node type of relay node during fault detection is the parameter information it sends to the downstream device in response to the upstream device. The fault detection device can identify the upstream and downstream twin devices adjacent to the first twin device in the target data transmission link of the preset digital twin system model, and collect the third parameter information sent by the upstream twin device to the first twin device within a preset time period. Then, the fault detection device can input the third parameter information into the first and second twin devices respectively, and collect the parameter information sent by the first twin device to the downstream twin device based on the third parameter information and the parameter information sent by the second twin device to the downstream twin device based on the third parameter information, thereby obtaining the first and second parameter information. This provides a suitable data foundation for subsequent fault detection of the on-board equipment under test, improving the accuracy of the fault detection results.

[0018] In one possible implementation, the method further includes: the fault detection device acquiring a first fault code set, the first fault code set including multiple first fault codes of the target vehicle in a state to be detected. The fault detection device determines a second number of first fault codes in the first fault code set. The method described above, "the fault detection device determining the node type of the first twin device in a preset digital twin system model," includes: if the second number is less than a second preset number threshold, then the fault detection device determines the node type of the first twin device in the preset digital twin system model.

[0019] Based on the aforementioned technical methods, when a vehicle malfunctions, it generates multiple fault codes to detect equipment failures. However, with a large number of fault codes, it is necessary to perform fault detection on multiple devices sequentially. Therefore, the fault detection device can perform fault detection on multiple devices sequentially when there are fewer fault codes. This ensures efficient fault detection for each device in the vehicle.

[0020] In one possible implementation, the method further includes: if the second quantity is greater than or equal to a second preset quantity threshold, the fault detection device acquires target state parameters of the preset digital twin system model in the state to be detected. The fault detection device updates the first twin device in the preset digital twin system model to a second twin device, obtaining an updated preset digital twin system model. Based on the target state parameters, the fault detection device adjusts the updated preset digital twin system model to the state to be detected, and acquires multiple second fault codes of the updated preset digital twin system model in the state to be detected, to obtain a second fault code set. The above-mentioned method of "generating target detection information by the fault detection device" includes: if the second fault code set is a proper subset of the first fault code set, the fault detection device generates target detection information.

[0021] Based on the aforementioned technical methods, the fault detection device can, when faced with a large number of fault codes, determine whether the number of fault codes generated during the replacement of the first twin device with the second twin device in the preset digital twin system model has decreased through a replacement verification method. This allows for the assessment of whether the vehicle-mounted equipment under test has potential faults. In this way, even with a large number of devices under test, fault detection for each device can be achieved by analyzing the overall change in the number of fault codes in the digital twin system model, avoiding the need to collect and verify the parameter information of each twin device individually. Therefore, this improves the operability and efficiency of fault detection.

[0022] In one possible implementation, the method further includes: the fault detection device acquiring a first device identifier set, a second device identifier set, and a third device identifier set. The first device identifier set includes device identifiers of multiple vehicle-mounted devices determined based on fault phenomenon description information. The second device identifier set includes device identifiers of vehicle-mounted devices corresponding to multiple first fault codes in the target vehicle under test conditions. The third device identifier set includes device identifiers of multiple vehicle-mounted devices specified by the user in the target vehicle. The fault phenomenon description information is used to indicate the fault condition of the target vehicle. The fault detection device determines a device identifier set to be tested based on the first device identifier set, the second device identifier set, and the third device identifier set. The device identifier set to be tested is the union of the first device identifier set, the second device identifier set, and the third device identifier set. The above-mentioned method of "the fault detection device acquiring the device identifier of the vehicle-mounted device to be tested in the target vehicle" includes: the fault detection device acquiring the device identifier of the vehicle-mounted device to be tested from the device identifier set to be tested. The device identifier of the vehicle-mounted device to be tested is the device identifier of any vehicle-mounted device in the device identifier set to be tested.

[0023] Based on the aforementioned technical means, the fault detection device can acquire multiple onboard devices requiring fault detection by obtaining fault codes and contents reported by the vehicle, user descriptions of the vehicle's fault symptoms, and devices specified by the user based on personal experience. This enriches the information on the source of the fault and improves the comprehensiveness of vehicle fault detection.

[0024] In one possible implementation, all device identifiers of vehicle-mounted devices in the first device identifier set correspond to a first priority level, all device identifiers of vehicle-mounted devices in the second device identifier set correspond to a second priority level, and all device identifiers of vehicle-mounted devices in the third device identifier set correspond to a third priority level. The method further includes: a fault detection device determining at least one device identifier of a first vehicle-mounted device based on the first, second, and third device identifier sets, wherein the device identifier of the first vehicle-mounted device is a device identifier of a vehicle-mounted device that is repeated across at least two of the first, second, and third device identifier sets. For each device identifier of a first vehicle-mounted device, the fault detection device sums the at least two initial priority levels corresponding to the device identifier of the first vehicle-mounted device to determine a target priority level corresponding to the device identifier of the first vehicle-mounted device, thereby obtaining multiple target priority levels. One device identifier of a first vehicle-mounted device corresponds to one target priority level, and the initial priority level is any one of the first, second, and third priority levels. The fault detection device determines the priority level corresponding to the device identifier of each vehicle-mounted device in the device identifier set to be detected based on the multiple target priority levels, the first priority level, the second priority level, and the third priority level. The above-mentioned method of "the fault detection device obtaining the device identifier of the vehicle-mounted device to be tested from the set of device identifiers to be tested" includes: the fault detection device obtaining the device identifier of the vehicle-mounted device to be tested from the set of device identifiers to be tested according to the priority level corresponding to the device identifier of each vehicle-mounted device in the set of device identifiers to be tested, wherein the priority level corresponding to the device identifier of the vehicle-mounted device to be tested is greater than the priority level corresponding to the device identifier of any other vehicle-mounted device in the set of device identifiers to be tested.

[0025] Based on the aforementioned technical methods, since fault information from different sources corresponds to varying degrees of urgency, the fault detection device can determine the corresponding priority levels based on the fault information from different sources and prioritize the detection of on-board equipment with higher priority levels during subsequent fault detection. This improves the efficiency of fault detection.

[0026] In one possible implementation, the method further includes: a fault detection device acquiring fault phenomenon description information. The fault detection device performs natural language processing on the fault phenomenon description information to obtain the device identifier of the second vehicle-mounted device and the target fault manifestation of the second vehicle-mounted device. Based on the device identifier of the second vehicle-mounted device and the target fault manifestation, the fault detection device determines the target fault cause in a preset fault knowledge graph. The target fault cause is the reason that causes the second vehicle-mounted device to exhibit the target fault manifestation. The preset fault knowledge graph includes multiple preset device identifiers of vehicle-mounted devices, multiple preset fault manifestations, and multiple preset fault causes. The above-mentioned method of "the fault detection device acquiring a first set of device identifiers" includes: the fault detection device acquiring the device identifiers of multiple third vehicle-mounted devices corresponding to the target fault cause in the preset fault knowledge graph to obtain a first set of device identifiers.

[0027] Based on the aforementioned technical means, the fault detection device can, using a pre-defined fault knowledge graph that includes device identifiers of multiple pre-defined vehicle-mounted devices, correspondences between multiple pre-defined fault manifestations and multiple pre-defined fault causes, associate the faulty devices and fault manifestations parsed from the fault phenomenon description information to determine the cause of the fault. Based on this cause, it can then extend to other vehicle-mounted devices affected by the fault, thereby identifying multiple vehicle-mounted devices that require fault detection. This improves the comprehensiveness of vehicle fault detection.

[0028] According to a second aspect provided in this application, a vehicle fault detection device is provided, the device comprising: an acquisition module and a processing module.

[0029] The module includes an acquisition module for acquiring the device identifier of the on-board device to be tested in the target vehicle. A processing module is used to determine the first and second twin devices corresponding to the on-board device to be tested based on the device identifier. The first twin device is a digital twin device corresponding to the on-board device to be tested in a preset digital twin system model, and the second twin device is a digital twin device constructed based on the initial data of the on-board device to be tested. The preset digital twin system model includes digital twin devices corresponding to any on-board device in the target vehicle. The processing module is also used to determine the node type of the first twin device in the preset digital twin system model. The acquisition module is also used to acquire first parameter information of the first twin device and second parameter information of the second twin device based on the node type. If the first parameter information and the second parameter information are different, the processing module generates target detection information, which indicates a potential fault in the on-board device to be tested.

[0030] In one possible implementation, both the first parameter information and the second parameter information include sub-parameter information corresponding to multiple preset times within a preset time period. The processing module is further configured to, if the first parameter information and the second parameter information are different, and the first quantity is less than a first preset quantity threshold, determine a first difference for each preset time based on the preset time, the first parameter information, and the second parameter information, to obtain multiple first differences. The first difference is the difference between two sub-parameter information corresponding to the same preset time in the first parameter information and the second parameter information. One first difference corresponds to one preset time, and the first quantity is the number of preset times within the preset time period. The processing module is further configured to sum the multiple first differences to determine a target deviation value between the first parameter information and the second parameter information. Specifically, if the target deviation value is greater than or equal to a preset deviation threshold, the processing module generates target detection information.

[0031] In one possible implementation, both the first parameter information and the second parameter information include sub-parameter information corresponding to multiple preset times within a preset time period. The acquisition module is further configured to, if the first parameter information and the second parameter information are different, and the first quantity is greater than or equal to a first preset quantity threshold, acquire a target time from the multiple preset times, where the target time is the last time among the multiple preset times, and the first quantity is the number of preset times within the preset time period. The processing module is further configured to, based on the target time, the first parameter information, and the second parameter information, determine a second difference, where the second difference is the difference between the two sub-parameter information corresponding to the target time in the first parameter information and the second parameter information. Specifically, the processing module is configured to, if the second difference is greater than or equal to a preset difference threshold, generate target detection information.

[0032] In one possible implementation, the acquisition module is specifically used to acquire first parameter information and second parameter information based on a preset time period if the node type is a starting node. The first parameter information is the parameter information generated by the first twin device within the preset time period, and the second parameter information is the parameter information generated by the second twin device within the preset time period.

[0033] In one possible implementation, the processing module is further configured to, if the node type is an end node, determine the upstream twin device of the first twin device in the preset digital twin system model. The acquisition module is specifically configured to acquire third parameter information based on a preset time period, wherein the third parameter information is parameter information sent by the upstream twin device to the first twin device within the preset time period. The processing module is further configured to input the third parameter information into the first twin device to acquire first parameter information, wherein the first parameter information is parameter information generated by the first twin device based on the third parameter information. The processing module is further configured to input the third parameter information into the second twin device to acquire second parameter information, wherein the second parameter information is parameter information generated by the second twin device based on the third parameter information.

[0034] In one possible implementation, the processing module is further configured to, if the node type is a relay node, determine the upstream and downstream twin devices of the first twin device in the preset digital twin system model. The acquisition module is specifically configured to acquire third parameter information based on a preset time period, wherein the third parameter information is the parameter information sent by the upstream twin device to the first twin device within the preset time period. The processing module is further configured to input the third parameter information into the first twin device to acquire first parameter information, wherein the first parameter information is the parameter information sent by the first twin device to the downstream twin device based on the third parameter information. The processing module is further configured to input the third parameter information into the second twin device to acquire second parameter information, wherein the second parameter information is the parameter information sent by the second twin device to the downstream twin device based on the third parameter information.

[0035] In one possible implementation, the acquisition module is further configured to acquire a first fault code set, the first fault code set including multiple first fault codes of the target vehicle in the state to be tested. The processing module is further configured to determine a second number of first fault codes in the first fault code set. Specifically, if the second number is less than a second preset number threshold, the processing module is configured to determine the node type of the first twin device in a preset digital twin system model.

[0036] In one possible implementation, the acquisition module is further configured to acquire target state parameters of the preset digital twin system model in the state to be detected if the second quantity is greater than or equal to a second preset quantity threshold. The processing module is further configured to update the first twin device in the preset digital twin system model to a second twin device, obtaining an updated preset digital twin system model. The processing module is further configured to adjust the updated preset digital twin system model to the state to be detected according to the target state parameters, and acquire multiple second fault codes of the updated preset digital twin system model in the state to be detected, to obtain a second fault code set. Specifically, the processing module is configured to generate target detection information if the second fault code set is a proper subset of the first fault code set.

[0037] In one possible implementation, the acquisition module is further configured to acquire a first device identifier set, a second device identifier set, and a third device identifier set. The first device identifier set includes device identifiers of multiple vehicle-mounted devices determined based on fault phenomenon description information. The second device identifier set includes device identifiers of vehicle-mounted devices corresponding to multiple first fault codes of the target vehicle in the test state. The third device identifier set includes device identifiers of multiple vehicle-mounted devices specified by the user in the target vehicle. The fault phenomenon description information is used to indicate the fault condition of the target vehicle. The processing module is further configured to determine a device identifier set to be tested based on the first device identifier set, the second device identifier set, and the third device identifier set. The device identifier set to be tested is the union of the first device identifier set, the second device identifier set, and the third device identifier set. Specifically, the acquisition module is configured to acquire the device identifier of the vehicle-mounted device to be tested from the device identifier set to be tested. The device identifier of the vehicle-mounted device to be tested is the device identifier of any vehicle-mounted device in the device identifier set to be tested.

[0038] In one possible implementation, all device identifiers of vehicle-mounted devices in the first device identifier set correspond to a first priority level, all device identifiers of vehicle-mounted devices in the second device identifier set correspond to a second priority level, and all device identifiers of vehicle-mounted devices in the third device identifier set correspond to a third priority level. The processing module is further configured to determine at least one device identifier of a first vehicle-mounted device based on the first device identifier set, the second device identifier set, and the third device identifier set. The device identifier of the first vehicle-mounted device is a device identifier of a vehicle-mounted device that is repeated across at least two of the first, second, and third device identifier sets. The processing module is further configured to, for each device identifier of a first vehicle-mounted device, sum the at least two initial priority levels corresponding to the device identifier of the first vehicle-mounted device to determine a target priority level corresponding to the device identifier of the first vehicle-mounted device, thereby obtaining multiple target priority levels. One device identifier of a first vehicle-mounted device corresponds to one target priority level, and the initial priority level is any one of the first, second, and third priority levels. The processing module is further configured to determine the priority level corresponding to the device identifier of each vehicle-mounted device in the device identifier set to be detected based on the multiple target priority levels, the first priority level, the second priority level, and the third priority level. The acquisition module is specifically used to obtain the device identifier of the vehicle device to be tested from the device identifier set according to the priority level corresponding to the device identifier of each vehicle device in the device identifier set to be tested. The priority level corresponding to the device identifier of the vehicle device to be tested is higher than the priority level corresponding to the device identifier of any other vehicle device in the device identifier set to be tested.

[0039] In one possible implementation, the acquisition module is further configured to acquire fault phenomenon description information. The processing module is further configured to perform natural language processing on the fault phenomenon description information to obtain the device identifier of the second vehicle-mounted device and the target fault manifestation of the second vehicle-mounted device. The processing module is further configured to determine the target fault cause in a preset fault knowledge graph based on the device identifier of the second vehicle-mounted device and the target fault manifestation. The target fault cause is the reason that causes the second vehicle-mounted device to be in the target fault manifestation. The preset fault knowledge graph includes the correspondence between multiple preset vehicle-mounted device identifiers, multiple preset fault manifestations, and multiple preset fault causes. The acquisition module is specifically configured to acquire the device identifiers of multiple third vehicle-mounted devices corresponding to the target fault cause in the preset fault knowledge graph to obtain a first device identifier set.

[0040] According to a third aspect provided in this application, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions. The processor is configured to execute instructions to implement the methods described in the first aspect and any possible implementation thereof.

[0041] According to a fourth aspect provided in this application, a computer-readable storage medium is provided that, when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to perform the methods described in the first aspect and any possible implementation thereof.

[0042] According to the fifth aspect provided in this application, a computer program product is provided, the computer program product including computer instructions, which, when executed on an electronic device, cause the electronic device to perform the method described in the first aspect and any possible implementation thereof.

[0043] Therefore, the above-mentioned technical features of this application have the following beneficial effects:

[0044] (1) The fault detection device can determine a first twin device that maintains data synchronization with the on-board equipment under test in a preset digital twin system model corresponding to the target vehicle, and obtain the first parameter information of the first twin device in the test state. Then, the fault detection device can construct a second twin device corresponding to the on-board equipment under test based on the initial data of the on-board equipment under test, and substitute the second twin device into the preset digital twin system model corresponding to the target vehicle to obtain the second parameter information of the second twin device in the normal state. Afterwards, the fault detection device can determine whether there is a potential fault in the on-board equipment under test based on the comparison result between the first parameter information and the second parameter information. If the first parameter information and the second parameter information are different, the fault detection device generates target detection information to indicate that there is a potential fault in the on-board equipment under test. In other words, when a fault occurs, such as a fault phenomenon or a fault code is detected, a digital twin of the vehicle component can be used to replace the physical entity for troubleshooting and locating the faulty component. These components are usually electrical components capable of generating or processing digital signals. This avoids the need to replace physical components and improves the efficiency of fault detection. Furthermore, during the acquisition of the first and second parameter information, the fault detection device can determine the acquisition strategy for the first and second parameter information by identifying the node type of the first twin device in the preset digital twin system model. In other words, because the node types of different devices in the data transmission link of the digital twin system model may differ, the fault detection standards between devices will also differ; that is, devices with different node types will refer to different parameter information during fault detection. Therefore, by determining the node type of the device, suitable reference data can be provided for device fault detection, improving the accuracy of the fault detection results.

[0045] (2) Because random parameters may be generated during actual operation, the parameters of the equipment may differ even under two identical operating environments. Therefore, when the first parameter information and the second parameter information are determined to be different, the fault detection device can determine the degree of deviation between the first parameter information and the second parameter information by accumulating the differences between the sub-parameter information corresponding to each preset time in the first parameter information and the second parameter information, and determine whether there is a potential fault in the on-board equipment under test by comparing the degree of deviation between the first parameter information and the second parameter information with a threshold. In this way, the accuracy of the fault detection results can be improved.

[0046] (3) When the first parameter information and the second parameter information are different, and there are a large number of preset time points, the fault detection device can determine whether there is a potential fault in the vehicle-mounted equipment under test by comparing the difference between the sub-parameter information corresponding to any preset time point in the first and second parameter information using a threshold comparison. This reduces the amount of information processed and improves fault detection efficiency. Furthermore, the fault detection device can determine whether there is a potential fault in the vehicle-mounted equipment under test by comparing the difference between the sub-parameter information corresponding to the last preset time point in the first and second parameter information using a threshold comparison. In other words, the fault detection device can determine whether there is a potential fault in the equipment based on the parameter information after the equipment has been running for a period of time. This improves fault detection efficiency while ensuring the accuracy of the fault detection results.

[0047] (4) When a device with a node type of starting node is fault detection, the parameter information referenced is the parameter information generated by itself. The fault detection device can obtain the first parameter information and the second parameter information by collecting the parameter information generated by the first twin device within a preset time period and the parameter information generated by the second twin device within a preset time period. This provides a suitable data basis for subsequent fault detection of the on-board equipment under test and improves the accuracy of the fault detection results of the on-board equipment under test.

[0048] (5) When a device with a node type of "end node" is fault detection, the parameter information referenced is the parameter information generated by itself in response to the upstream device. The fault detection device can identify the upstream twin device adjacent to the first twin device in the target data transmission link of the preset digital twin system model, and collect the third parameter information sent by the upstream twin device to the first twin device within a preset time period. Then, the fault detection device can input the third parameter information into the first twin device and the second twin device respectively, and collect the parameter information generated by the first twin device based on the third parameter information and the parameter information generated by the second twin device based on the third parameter information, to obtain the first parameter information and the second parameter information, providing a suitable data foundation for subsequent fault detection of the on-board equipment under test, and improving the accuracy of the fault detection results of the on-board equipment under test.

[0049] (6) When a device with a node type of relay node is used for fault detection, the parameter information referenced is the parameter information it sends to the downstream device in response to the upstream device. The fault detection device can identify the upstream and downstream twin devices adjacent to the first twin device in the target data transmission link of the preset digital twin system model, and collect the third parameter information sent by the upstream twin device to the first twin device within a preset time period. Then, the fault detection device can input the third parameter information into the first twin device and the second twin device respectively, and collect the parameter information sent by the first twin device to the downstream twin device based on the third parameter information and the parameter information sent by the second twin device to the downstream twin device based on the third parameter information, so as to obtain the first parameter information and the second parameter information, providing a suitable data foundation for the subsequent fault detection of the on-board equipment under test, and improving the accuracy of the fault detection results of the on-board equipment under test.

[0050] (7) When a vehicle malfunctions, it generates multiple fault codes to detect equipment malfunctions. However, with a large number of fault codes, multiple devices need to be detected sequentially. Therefore, the fault detection device can detect multiple devices sequentially when there are fewer fault codes. This ensures efficient fault detection for each device in the vehicle.

[0051] (8) When there are many fault codes, the fault detection device can determine whether the number of fault codes generated during the replacement of the first twin device with the second twin device in the preset digital twin system model has decreased, thereby judging whether there are potential faults in the on-board equipment under test. In this way, when there are many devices under test, fault detection of each device can be achieved by changing the number of fault codes of the overall digital twin system model, avoiding the need to collect and verify the parameter information of each twin device. Therefore, the operability and efficiency of fault detection can be improved.

[0052] (9) The fault detection device can acquire multiple on-board devices that need to be detected by obtaining the fault codes and contents reported by the vehicle, the user's description of the vehicle's fault phenomena, and the devices specified by the user based on personal experience. In this way, the fault source information can be enriched and the comprehensiveness of vehicle fault detection can be improved.

[0053] (10) Since fault information from different sources corresponds to different levels of urgency, the fault detection device can determine the corresponding priority level based on the fault information from different sources, and prioritize the detection of on-board equipment with higher priority levels during subsequent fault detection. This can improve the efficiency of fault detection.

[0054] (11) The fault detection device can, based on a preset fault knowledge graph that includes the correspondence between multiple preset vehicle-mounted device identifiers, multiple preset fault manifestations, and multiple preset fault causes, associate the faulty devices and fault manifestations parsed from the fault phenomenon description information, determine the cause of the fault, and extend other vehicle-mounted devices affected by the cause, thereby obtaining multiple vehicle-mounted devices that need to be fault detected. In this way, the comprehensiveness of vehicle fault detection can be improved.

[0055] It should be noted that the technical effects of any of the implementation methods in aspects two through five can be found in the technical effects of the corresponding implementation methods in aspect one, and will not be repeated here.

[0056] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0057] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application, and do not constitute an undue limitation of this application.

[0058] Figure 1 This is a schematic diagram of a communication system according to an exemplary embodiment;

[0059] Figure 2 This is a flowchart illustrating a vehicle fault detection method according to an exemplary embodiment;

[0060] Figure 3 This is a schematic diagram illustrating an example of a data transmission link according to an exemplary embodiment;

[0061] Figure 4 This is a flowchart illustrating another vehicle fault detection method according to an exemplary embodiment;

[0062] Figure 5 This is a flowchart illustrating another vehicle fault detection method according to an exemplary embodiment;

[0063] Figure 6 This is a flowchart illustrating another vehicle fault detection method according to an exemplary embodiment;

[0064] Figure 7 This is a flowchart illustrating another vehicle fault detection method according to an exemplary embodiment;

[0065] Figure 8 This is an example schematic diagram illustrating an updated digital twin system model according to an exemplary embodiment;

[0066] Figure 9 This is a flowchart illustrating another vehicle fault detection method according to an exemplary embodiment;

[0067] Figure 10 This is an example diagram of a knowledge graph according to an exemplary embodiment;

[0068] Figure 11 This is a flowchart illustrating another vehicle fault detection method according to an exemplary embodiment;

[0069] Figure 12 This is a schematic diagram of the system architecture of a fault detection device according to an exemplary embodiment;

[0070] Figure 13 This is a schematic diagram of the system architecture of another fault detection device according to an exemplary embodiment;

[0071] Figure 14 This is a block diagram illustrating a vehicle fault detection device according to an exemplary embodiment;

[0072] Figure 15 This is a block diagram illustrating an electronic device according to an exemplary embodiment. Detailed Implementation

[0073] To enable those skilled in the art to better understand the technical solutions of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0074] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0075] Before providing a detailed description of the vehicle fault detection method according to the embodiments of this application, the implementation environment and application scenarios of the embodiments of this application will be introduced first.

[0076] As an indispensable means of transportation in people's daily lives, vehicles are equipped with various onboard devices (such as radar, cameras, and audio systems) to meet users' driving needs. However, with the increasing number of onboard devices, their operating states differ, leading to higher demands for their management. For example, fault detection of onboard devices in vehicles is crucial.

[0077] Currently, when performing fault detection on-board equipment in vehicles, it is usually necessary to perform an offline testing process. This involves vehicle maintenance personnel identifying potentially faulty on-board equipment based on the user's description of the fault and their own past work experience. The on-board equipment is then verified using a replacement method (that is, replacing potentially faulty on-board equipment with normal on-board equipment). Finally, after multiple verifications, the faulty on-board equipment is confirmed.

[0078] In other words, the traditional offline diagnostic process is usually as follows: When a car breaks down and comes to the shop for repair, the repair personnel will first ask in detail about the fault symptoms, judge which parts may be causing the fault based on historical experience, and then read the fault code data from the vehicle through a diagnostic tool for analysis. At the same time, the faulty parts are verified by the replacement method. After multiple verifications and analyses, the faulty parts are identified and maintenance records are generated.

[0079] In summary, the aforementioned technical solutions require manual intervention for fault detection of onboard equipment in vehicles. The entire diagnostic process is inefficient and suffers from inaccurate fault component location, resulting in low efficiency in fault detection of onboard equipment. Therefore, improving the efficiency of fault detection for onboard equipment in vehicles has become an urgent technical problem to be solved.

[0080] In the existing field of automotive fault diagnosis, based on real-time data, potential faults can be detected in digital twin systems, such as temperature changes in a component. This can lead to early warnings, prompting the replacement of relevant parts and preventing the fault from occurring. Furthermore, when a fault does occur, digital twin technology enables rapid system-level analysis, allowing for quick fault localization.

[0081] Existing digital twin-based automotive fault diagnosis methods mainly focus on powertrain system fault diagnosis, with two main approaches: one is to use digital twin technology to display the status of automotive components in real time, and display the fault status based on fault codes when a fault occurs; the other approach is to use the full lifecycle data of components to model twin components for fault diagnosis.

[0082] In other words, all the above technical solutions diagnose automotive components by comparing the synchronization results of digital twin technology using thresholds. However, the threshold comparison results of the synchronization results of digital twin technology may not reflect the actual operating status of the components, thus reducing the accuracy of fault diagnosis.

[0083] To address the aforementioned issues, this application provides a vehicle fault detection method. The method includes: a fault detection device determining a current twin device that maintains data synchronization with the on-board equipment within a digital twin system model corresponding to the vehicle, and obtaining first parameter information of the current twin device in its current state. Next, the fault detection device constructs an initial twin device corresponding to the on-board equipment based on the initial data of the on-board equipment, and substitutes the initial twin device into the digital twin system model corresponding to the vehicle to obtain second parameter information of the initial twin device in its normal state. Then, the fault detection device determines whether there is a potential fault in the on-board equipment based on the comparison between the first and second parameter information. If the first and second parameter information are different, the fault detection device generates detection information indicating a potential fault in the on-board equipment. In other words, when a fault occurs, such as a fault symptom or a fault code, a digital twin of the vehicle component can be used to replace the physical entity for troubleshooting and locating the faulty component. This component is typically an electrical component capable of generating or processing digital signals. This avoids replacing the physical component and improves the efficiency of fault detection. Furthermore, during the acquisition of the first and second parameter information, the fault detection device can determine the node type of the current twin device in the digital twin system model, and thus determine the acquisition strategy for the parameter information of the current twin device and the initial twin device. In other words, because the node types corresponding to different devices in the data transmission link of the digital twin system model may differ, the fault detection standards between devices will also differ; that is, devices with different node types will refer to different parameter information during fault detection. Therefore, by determining the node type of the device, suitable reference data can be provided for device fault detection, improving the accuracy of the fault detection results.

[0084] The implementation environment of the embodiments of this application is described below.

[0085] Figure 1 This is a schematic diagram of a communication system according to an exemplary embodiment, such as... Figure 1As shown, the communication system includes: a vehicle-mounted device 101 to be tested, a fault detection device (such as a server 102), and user equipment (such as a terminal 103). The vehicle-mounted device 101 is deployed in the target vehicle 104, and the server 102 is equipped with a pre-defined digital twin system model 105 built based on the target vehicle 104. The server 102 can communicate with the vehicle-mounted device 101 and the terminal 103 via wired / wireless communication.

[0086] Specifically, server 102 can receive the device identifier reported by the vehicle-mounted device 101 under test, and determine the first twin device corresponding to the vehicle-mounted device 101 under test in the preset digital twin system model 105 based on the device identifier. Simultaneously, server 102 can construct a second twin device based on the initial data of the vehicle-mounted device 101 under test. Next, server 102 can determine the node type of the first twin device in the preset digital twin system model 105, and obtain the first parameter information of the first twin device and the second parameter information of the second twin device based on the node type. Afterwards, server 102 can perform fault detection on the vehicle-mounted device 101 under test based on the comparison result between the first parameter information and the second parameter information. If server 102 determines that the first parameter information and the second parameter information are different, it generates detection information indicating that the vehicle-mounted device 101 under test has a potential fault and sends the detection information to terminal 103.

[0087] In the embodiments of this application, the node type can be any of the following: start node, end node, and transit node.

[0088] It should be noted that the embodiments of this application do not limit the vehicle-mounted device 101 to be tested. For example, the vehicle-mounted device 101 to be tested can be a distance sensor. Another example is that the vehicle-mounted device 101 to be tested can be a vehicle-mounted switch. Yet another example is that the vehicle-mounted device 101 to be tested can be a vehicle-mounted audio system.

[0089] For example, if the vehicle-mounted device 101 to be tested is a distance sensor, the first parameter information and the second parameter information can be the resistance value of the distance sensor. If the vehicle-mounted device 101 to be tested is a vehicle-mounted switch, the first parameter information and the second parameter information can be the digital signals (such as 0 and 1) output by the vehicle-mounted switch. If the vehicle-mounted device 101 to be tested is a vehicle audio system, the first parameter information and the second parameter information can be the playback volume of the vehicle audio system.

[0090] The terminal (such as terminal 103) can be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, or other device with sending and receiving functions. This application does not impose any special restrictions on the specific form of the terminal. It can interact with the user through one or more methods such as keyboard, touchpad, touch screen, remote control, voice interaction, or handwriting device.

[0091] The server (such as server 102) can be a single physical server, or it can be a server cluster consisting of multiple servers. Alternatively, the server cluster can be a distributed cluster. Or, the server can be a cloud server. This application does not limit the specific implementation of the server.

[0092] For ease of understanding, the vehicle fault detection method provided in this application will be described in detail below with reference to the accompanying drawings. Figure 2 This is a flowchart illustrating a vehicle fault detection method according to an exemplary embodiment, such as... Figure 2 As shown, the method includes the following steps:

[0093] S201. The fault detection device acquires the device identifier of the on-board equipment to be tested in the target vehicle.

[0094] It should be noted that the device identifier of the vehicle-mounted device to be tested in this application embodiment is not limited. For example, the device identifier of the vehicle-mounted device to be tested can be the device name of the vehicle-mounted device to be tested. Another example is that the device identifier of the vehicle-mounted device to be tested can be the device type of the vehicle-mounted device to be tested. Yet another example is that the device identifier of the vehicle-mounted device to be tested can be the device number. Yet another example is that the device identifier of the vehicle-mounted device to be tested can be composed of the device name, device type, and device number of the vehicle-mounted device to be tested.

[0095] For example, the device identifier of the vehicle distance sensor can be "vehicle distance sensor (i.e., device name) + sensor (i.e., device type) + F21E05c (i.e., device number)".

[0096] In one possible implementation, the fault detection device can receive a first fault code reported by the target vehicle and obtain the device identifier of the on-board equipment to be tested based on the first fault code. The first fault code is the fault code of the target vehicle in the state to be tested.

[0097] In another possible implementation, the fault detection device can receive the device identifier of the on-board device to be detected in the target vehicle input by the user in order to obtain the device identifier of the on-board device to be detected.

[0098] S202. The fault detection device determines the first twin device and the second twin device corresponding to the on-board equipment to be tested based on the equipment identifier of the on-board equipment to be tested.

[0099] The first twin device is the digital twin device corresponding to the vehicle-mounted device to be tested in the preset digital twin system model, and the second twin device is the digital twin device constructed based on the initial data of the vehicle-mounted device to be tested. The preset digital twin system model includes the digital twin device corresponding to any vehicle-mounted device in the target vehicle, and the digital twin device in the preset digital twin system model keeps the data synchronized with the corresponding vehicle-mounted device in the target vehicle.

[0100] In other words, the first twin device keeps data synchronized with the on-board equipment of the target vehicle in the test state, and the second twin device keeps data synchronized with the on-board equipment of the target vehicle in the normal operation state.

[0101] It should be noted that the difference between the first and second twin devices is that the first twin device is a historical digital twin device (i.e., a twin component) of the on-board device under test, which records the entire lifecycle data of the on-board device under test, while the second twin device is a twin component with no data records. Another important difference is that their functions may be different. The component function of the first twin device is mainly to complete the state synchronization and data recording of the on-board device under test, while the second twin device used for verification will change its function in combination with the verification method (i.e., S204 below) and the component role (i.e., node type). For example, when the component role of the on-board device under test is a data producer, the first twin device is only responsible for recording the data produced by the on-board device under test and the state of the on-board device under test, without data processing or simulation functions, while the second twin device turns off the data recording function and turns on the data simulation or processing function. Its simulated processing function is completely consistent with that of the vehicle-end component. For example, it can simulate and generate the same digital signal as the vehicle-end sensor, or for the same digital signal input, it can produce the same processing result as the vehicle end.

[0102] In one possible implementation, when the fault detection device constructs the second twin device, the corresponding data functions of the second twin device are configured according to the component roles of the first twin device.

[0103] S203. The fault detection device determines the node type of the first twin device in the preset digital twin system model.

[0104] In one possible implementation, the fault detection device stores multiple preset data transmission links in a preset digital twin system model, each preset data transmission link consisting of multiple digital twin devices. The fault detection device can determine a target data transmission link from these preset data transmission links; the target data transmission link is the data transmission link that includes a first twin device. Then, based on the position of the first twin device in the target data transmission link, the fault detection device can determine the node type of the first twin device in the preset digital twin system model.

[0105] It should be noted that existing component twins (i.e., digital twin devices) are usually isolated in the twin environment (i.e., digital twin system model), with no connection between the components. This application proposes to establish the connection between the twin components in order to locate the faulty component.

[0106] In this embodiment, the data link is abstracted based on the communication relationship between automotive components, and is not a real physical link. Figure 3 As shown, each node represents a twin component, and the connection between twin components indicates a data transfer relationship between the physical components. For example, twin component A → twin component B means that the output data of twin component A is used as the input data of twin component B.

[0107] For example, the target data transmission link can be data transmission link A used for managing (such as real-time temperature display and high-temperature warning broadcast) the outside temperature of the vehicle. Data transmission link A consists of an outside temperature sensor, an analog-to-digital converter, an onboard host, and an onboard audio system.

[0108] Therefore, the data link defined in this application is applicable to both bus networks and service-oriented architecture (SOA) communication scenarios.

[0109] In one possible design, the node type can be any of the following: start node, end node, and transit node.

[0110] For example, in the above example, in data transmission link A, the node type of the vehicle exterior temperature sensor is the starting node, the node types of the analog-to-digital converter and the vehicle host are both relay nodes, and the node type of the vehicle audio system is the ending node.

[0111] It should be noted that the embodiments of this application do not limit the digital twin device with node type as the starting node. For example, a digital twin device with node type as the starting node can be a digital twin device corresponding to a sensor. Another example is a digital twin device with node type as the starting node that can be a digital twin device corresponding to a timer. Yet another example is a digital twin device with node type as the starting node that can be a digital twin device corresponding to a battery.

[0112] Similarly, this application does not limit the type of digital twin device as an end node. For example, a digital twin device with an end node as its node type can be a digital twin device corresponding to an in-vehicle head unit. Another example is a digital twin device with an end node as its node type, which can be a digital twin device corresponding to an in-vehicle audio system. Yet another example is a digital twin device with an end node as its node type, which can be a digital twin device corresponding to in-vehicle ambient lighting.

[0113] This application does not limit the type of digital twin device as a relay node. For example, a digital twin device as a relay node can be a digital twin device corresponding to a switch. Another example is a digital twin device as a relay node that can be a digital twin device corresponding to a controller. Yet another example is a digital twin device as a relay node that can be a digital twin device corresponding to a central processing unit.

[0114] For example, in combination Figure 3 In the data link shown, the node types of twin components A and E are both start nodes, the node types of twin components B and C are relay nodes, and the node types of twin components D and F are both end nodes.

[0115] In other words, the starting node (i.e., the data producer), such as Figure 3 Twin components A and E, as shown in the diagram, are typically sensors or similar physical entities. These components are at the very top of the data link and often only have outputs, no inputs. Their twin components must be able to simulate the data flow generated when the original component is operating normally. End nodes (i.e., data consumers), such as twin components D and F, are typically area controllers or command execution units. These components are usually at the very bottom of the data link and are responsible for receiving the final processing results (such as fault codes) or executing a command. These twin components must be able to receive upstream data and respond accordingly. Intermediate nodes (data transmitters), such as twin components B and C, are typically assemblies or similar physical entities. They receive upstream data, process it, and then transmit it to downstream components. These twin components must be able to accept input data, process it according to the component's normal processing logic, and output the result.

[0116] In one possible implementation, the target data transmission link may include multiple sub-data transmission links, and the node types of the first twin devices in different sub-data transmission links may also differ.

[0117] For example, in conjunction with the above example, data transmission link A for managing the outside temperature can include: a sub-data transmission link A for displaying the outside temperature and a sub-data transmission link B for broadcasting high-temperature warnings. Sub-data transmission link A consists of an outside temperature sensor, an analog-to-digital converter, and an on-board unit; sub-data transmission link B consists of the on-board unit and an on-board audio system. In sub-data transmission link A, the outside temperature sensor is the starting node, the analog-to-digital converter is the intermediate node, and the on-board unit is the ending node. In sub-data transmission link B, the on-board unit is the starting node, and the on-board audio system is the ending node.

[0118] The following embodiments use any sub-data transmission link in the target data transmission link as an example to illustrate the vehicle fault detection method provided in this application.

[0119] S204. The fault detection device obtains the first parameter information of the first twin device and the second parameter information of the second twin device according to the node type.

[0120] The first parameter information is the operating parameter information of the on-board device under test synchronized by the first twin device in the state under test, and the second parameter information is the operating parameter information of the second twin device in the state under test.

[0121] For example, taking the vehicle-mounted device to be tested as a car temperature sensor, the first parameter information can be the resistance value of the car temperature sensor in the vehicle when it is in motion, which is 12 ohms, and the second parameter information can be the resistance value of the digital twin device (i.e., the second twin device) constructed based on the initial data of the car temperature sensor in the digital twin system model (i.e., the preset digital twin system model) when it is in motion, which is 11.5 ohms.

[0122] In one possible implementation, if the node type is a starting node, the fault detection device can acquire first parameter information and second parameter information based on a preset time period. The first parameter information is the parameter information generated by the first twin device within the preset time period, and the second parameter information is the parameter information generated by the second twin device within the preset time period.

[0123] In other words, the parameter information referenced by a device with node type "starting node" during fault detection is the parameter information it generates itself. The fault detection device can obtain first parameter information and second parameter information by collecting parameter information generated by the first twin device within a preset time period and the second twin device within a preset time period. This provides a suitable data foundation for subsequent fault detection of the on-board equipment under test, thereby improving the accuracy of the fault detection results.

[0124] In another possible implementation, if the node type is an end node, the fault detection device can identify the upstream twin device of the first twin device in the preset digital twin system model and obtain third parameter information based on a preset time period. Here, the upstream twin device is the digital twin device adjacent to the first twin device in the target data transmission link, and the third parameter information is the parameter information sent by the upstream twin device to the first twin device within the preset time period. Then, the fault detection device can input the third parameter information into the first twin device to obtain first parameter information, which is the parameter information generated by the first twin device based on the third parameter information. Similarly, the fault detection device can input the third parameter information into the second twin device to obtain second parameter information, which is the parameter information generated by the second twin device based on the third parameter information.

[0125] In other words, devices with a node type of "end node" refer to the parameter information they generate in response to upstream devices during fault detection. The fault detection device can identify the upstream twin device adjacent to the first twin device in the target data transmission link of the preset digital twin system model, and collect the third parameter information sent by the upstream twin device to the first twin device within a preset time period. Then, the fault detection device can input the third parameter information into both the first and second twin devices, collecting the parameter information generated by the first and second twin devices based on the third parameter information, to obtain both the first and second parameter information. This provides a suitable data foundation for subsequent fault detection of the on-board equipment under test, improving the accuracy of the fault detection results.

[0126] Optionally, if the node type is a relay node, the fault detection device can identify the upstream and downstream twin devices of the first twin device in the preset digital twin system model, and obtain third parameter information based on a preset time period. Here, the upstream and downstream twin devices are both digital twin devices adjacent to the first twin device in the target data transmission link, and the third parameter information is the parameter information sent by the upstream twin device to the first twin device within the preset time period. Then, the fault detection device can input the third parameter information into the first twin device to obtain first parameter information, which is the parameter information sent by the first twin device to the downstream twin device based on the third parameter information. Similarly, the fault detection device can input the third parameter information into the second twin device to obtain second parameter information, which is the parameter information sent by the second twin device to the downstream twin device based on the third parameter information.

[0127] In other words, devices with a node type of relay node refer to the parameter information they send to downstream devices in response to upstream devices during fault detection. The fault detection device can identify upstream and downstream twin devices adjacent to the first twin device in the target data transmission link of the preset digital twin system model, and collect the third parameter information sent by the upstream twin device to the first twin device within a preset time period. Then, the fault detection device can input the third parameter information into the first and second twin devices respectively, and collect the parameter information sent by the first twin device to the downstream twin device based on the third parameter information and the parameter information sent by the second twin device to the downstream twin device based on the third parameter information, thereby obtaining the first and second parameter information. This provides a suitable data foundation for subsequent fault detection of the on-board equipment under test, improving the accuracy of the fault detection results.

[0128] S205. The fault detection device determines whether the first parameter information and the second parameter information are the same.

[0129] For example, taking a car temperature sensor as the in-vehicle device to be tested, if the first parameter is a resistance value of 12 ohms and the second parameter is a resistance value of 11.5 ohms, the fault detection device determines that the first parameter and the second parameter are different. Similarly, if the first parameter is a resistance value of 8 ohms and the second parameter is a resistance value of 8 ohms, the fault detection device determines that the first parameter and the second parameter are the same.

[0130] In one possible implementation, both the first parameter information and the second parameter information include sub-parameter information corresponding to multiple preset times within a preset time period, and the number of preset times within the preset time period is a first quantity. During the process of the fault detection device determining whether the first parameter information and the second parameter information are the same, the fault detection device can determine whether the first parameter information and the second parameter information are the same by comparing the sub-parameter information corresponding to the same preset time in the first parameter information and the second parameter information.

[0131] In one possible design, if the fault detection device determines that the sub-parameter information corresponding to each preset time in the first parameter information and the second parameter information are the same, then the fault detection device determines that the first parameter information and the second parameter information are the same.

[0132] In another possible design, if the fault detection device determines that the sub-parameter information corresponding to any preset time in the first parameter information and the second parameter information is different, then the fault detection device determines that the first parameter information and the second parameter information are different.

[0133] For example, taking the vehicle-mounted device to be tested as a car temperature sensor, and the preset time period as 8:00 AM to 9:00 AM, if the first parameter information includes: a resistance value of 12 ohms at 8:00 AM (i.e., sub-parameter information), a resistance value of 10 ohms at 8:30 AM, and a resistance value of 11.3 ohms at 9:00 AM, and the second parameter information includes: a resistance value of 12 ohms at 8:00 AM (i.e., sub-parameter information), a resistance value of 10 ohms at 8:30 AM, and a resistance value of 11.3 ohms at 9:00 AM, then the fault detection device determines that the first parameter information and the second parameter information are the same. Similarly, if the first parameter information includes: a resistance value of 12 ohms at 8:00 AM (i.e., sub-parameter information), a resistance value of 10 ohms at 8:30 AM, and a resistance value of 11.3 ohms at 9:00 AM, and the second parameter information includes: a resistance value of 12 ohms at 8:00 AM (i.e., sub-parameter information), a resistance value of 10 ohms at 8:30 AM, and a resistance value of 11.4 ohms at 9:00 AM, then the fault detection device determines that the first parameter information and the second parameter information are different.

[0134] In some embodiments, if the fault detection device determines that the first parameter information is the same as the second parameter information, the fault detection device generates target prompt information, which is used to indicate that there is no potential fault in the on-board equipment to be tested.

[0135] In some other embodiments, if the fault detection device determines that the first parameter information is different from the second parameter information, the fault detection device may execute S206.

[0136] S206. The fault detection device generates target detection information.

[0137] Among them, the target detection information is used to indicate potential faults in the on-board equipment to be detected.

[0138] The technical solution provided by the above embodiments brings at least the following beneficial effects: The fault detection device can determine a first twin device that maintains data synchronization with the on-board equipment under test in a preset digital twin system model corresponding to the target vehicle, and obtain the first parameter information of the first twin device in the test state. Then, the fault detection device can construct a second twin device corresponding to the on-board equipment under test based on the initial data of the on-board equipment under test, and substitute the second twin device into the preset digital twin system model corresponding to the target vehicle to obtain the second parameter information of the second twin device in the normal state. Afterwards, the fault detection device can determine whether there is a potential fault in the on-board equipment under test based on the comparison result between the first parameter information and the second parameter information. If the first parameter information and the second parameter information are different, the fault detection device generates target detection information to indicate that there is a potential fault in the on-board equipment under test. That is to say, when a fault occurs, such as a fault phenomenon or a fault code is detected, a digital twin of the vehicle component can be used to replace the physical entity for troubleshooting and locating the faulty component. These components are usually electrical components capable of generating or processing digital signals. This avoids the need to replace physical components and improves the efficiency of fault detection. Furthermore, during the acquisition of the first and second parameter information, the fault detection device can determine the acquisition strategy for the first and second parameter information by identifying the node type of the first twin device in the preset digital twin system model. In other words, because the node types of different devices in the data transmission link of the digital twin system model may differ, the fault detection standards between devices will also differ; that is, devices with different node types will refer to different parameter information during fault detection. Therefore, by determining the node type of the device, suitable reference data can be provided for device fault detection, improving the accuracy of the fault detection results.

[0139] In some embodiments, since random parameters may be generated during actual operation, the parameters of the device may differ even under two identical operating environments. To avoid this difference and improve the accuracy of fault detection results, such as... Figure 4 As shown, after S205, if the fault detection device determines that the first parameter information and the second parameter information are different, the vehicle fault detection method provided in this application embodiment further includes the following steps:

[0140] S401, The fault detection device determines whether the first quantity is less than the first preset quantity threshold.

[0141] In one possible implementation, the fault detection device stores a first preset quantity threshold. The fault detection device can compare the first quantity with the first preset quantity threshold to determine whether the first quantity is less than the first preset quantity threshold.

[0142] In some embodiments, if the fault detection device determines that the first quantity is less than the first preset quantity threshold, the fault detection device may execute S402.

[0143] S402. For each preset time, the fault detection device determines a first difference based on the preset time, the first parameter information, and the second parameter information, so as to obtain multiple first differences.

[0144] The first difference is the difference between two sub-parameters corresponding to the same preset time in the first parameter information and the second parameter information, and one first difference corresponds to one preset time.

[0145] For example, if the preset time period includes: preset time A, preset time B and preset time C, and the first parameter information includes: sub-parameter information 1.1 corresponding to preset time A, sub-parameter information 3.7 corresponding to preset time B and sub-parameter information 0.8 corresponding to preset time C, and the second parameter information includes: sub-parameter information 2.3 corresponding to preset time A, sub-parameter information 1.9 corresponding to preset time B and sub-parameter information 0.5 corresponding to preset time C, then the first difference corresponding to preset time A is 1.2, the first difference corresponding to preset time B is 1.8, and the first difference corresponding to preset time C is 0.3.

[0146] S403. The fault detection device sums up multiple first differences to determine the target deviation value between the first parameter information and the second parameter information.

[0147] The target deviation value is used to indicate the degree of deviation between the first parameter information and the second parameter information, and the target deviation value is directly proportional to the degree of deviation between the first parameter information and the second parameter information.

[0148] In other words, the larger the target deviation value, the greater the deviation between the first parameter information and the second parameter information; the smaller the target deviation value, the smaller the deviation between the first parameter information and the second parameter information.

[0149] S404. The fault detection device determines whether the target deviation value is less than the preset deviation threshold.

[0150] In one possible implementation, the fault detection device stores a preset deviation threshold. The fault detection device can compare the target deviation value with the preset deviation threshold to determine whether the target deviation value is less than the preset deviation threshold.

[0151] In some embodiments, if the fault detection device determines that the target deviation value is less than a preset deviation threshold, the fault detection device generates a target prompt message.

[0152] In other embodiments, if the fault detection device determines that the target deviation value is greater than or equal to a preset deviation threshold, the fault detection device executes S206.

[0153] Understandably, random parameters may arise during actual operation, causing differences in parameters even under two identical operating conditions. Therefore, when the first and second parameter information are determined to be different, the fault detection device can determine the degree of deviation by accumulating the differences between the sub-parameter information corresponding to each preset time point in both the first and second parameter information. Furthermore, by comparing this degree of deviation with a threshold, it can determine whether the on-board equipment under test has a potential fault. This improves the accuracy of fault detection results.

[0154] In other embodiments, such as Figure 5 As shown, after step 401, if the fault detection device determines that the first quantity is greater than or equal to the first preset quantity threshold, the vehicle fault detection method provided in this application embodiment further includes the following steps:

[0155] S501, The fault detection device obtains the target time from multiple preset times.

[0156] In one possible design, the target time is any one of a plurality of preset times.

[0157] In another possible design, the target time is the last of a set of preset times.

[0158] S502, the fault detection device determines the second difference based on the target time, the first parameter information, and the second parameter information.

[0159] The second difference is the difference between the two sub-parameters corresponding to the target time in the first and second parameter information.

[0160] It should be noted that the process by which the fault detection device determines the second difference based on the target time, the first parameter information, and the second parameter information can be referred to the description of determining the first difference based on the preset time, the first parameter information, and the second parameter information in the above embodiment, and will not be repeated here.

[0161] S503, The fault detection device determines whether the second difference is less than the preset difference threshold.

[0162] In one possible implementation, the fault detection device stores a preset difference threshold. The fault detection device can compare the second difference with the preset difference threshold to determine whether the second difference is less than the preset difference threshold.

[0163] In some embodiments, if the fault detection device determines that the second difference is less than a preset difference threshold, the fault detection device generates a target prompt message.

[0164] In some other embodiments, if the fault detection device determines that the second difference is greater than or equal to a preset difference threshold, the fault detection device executes S206.

[0165] Understandably, when the first parameter information and the second parameter information are different, and there are a large number of preset time points, the fault detection device can determine whether the vehicle-mounted equipment under test has a potential fault by comparing the difference between the sub-parameter information corresponding to any preset time point in the first and second parameter information using a threshold comparison. This reduces the amount of information processed and improves fault detection efficiency. Furthermore, the fault detection device can determine whether the vehicle-mounted equipment under test has a potential fault by comparing the difference between the sub-parameter information corresponding to the last preset time point in the first and second parameter information using a threshold comparison. In other words, the fault detection device can determine whether the equipment has a potential fault based on parameter information after the equipment has been running for a period of time. This improves fault detection efficiency while ensuring the accuracy of the fault detection results.

[0166] It should be noted that when a vehicle malfunctions, it generates multiple fault codes to detect the fault in the equipment. However, when there are many fault codes, it is necessary to detect the fault in multiple devices sequentially, which affects the efficiency of fault detection.

[0167] In some embodiments, to improve the efficiency of fault detection, such as Figure 6 As shown, prior to S203, the vehicle fault detection method provided in this application embodiment further includes the following steps:

[0168] S601, The fault detection device acquires the first set of fault codes.

[0169] The first fault code set includes multiple first fault codes of the target vehicle in the test state.

[0170] S602, The fault detection device determines the second number of the first fault codes in the first fault code set.

[0171] S603, The fault detection device determines whether the second quantity is less than the second preset quantity threshold.

[0172] In one possible implementation, the fault detection device stores a second preset quantity threshold. The fault detection device can compare the second quantity with the second preset quantity threshold to determine whether the second quantity is less than the second preset quantity threshold.

[0173] In some embodiments, if the fault detection device determines that the second quantity is less than the second preset quantity threshold, the fault detection device may execute S203.

[0174] Understandably, when a vehicle malfunctions, it generates multiple fault codes to detect device failures. However, with a large number of fault codes, it's necessary to check multiple devices sequentially. Therefore, a fault detection device can perform sequential fault checks on multiple devices when there are fewer fault codes. This ensures efficient fault detection for each device in the vehicle.

[0175] In other embodiments, such as Figure 7 As shown, after S603, if the fault detection device determines that the second quantity is greater than or equal to the second preset quantity threshold, the vehicle fault detection method provided in this application embodiment further includes the following steps:

[0176] S701, The fault detection device acquires the target state parameters of the preset digital twin system model in the state to be detected.

[0177] The target state parameters include the state parameters of all digital twin devices in the preset digital twin system model under the state to be detected.

[0178] S702, the fault detection device updates the first twin device in the preset digital twin system model to the second twin device, thereby obtaining the updated preset digital twin system model.

[0179] In one possible implementation, the preset digital twin system model includes a first twin device and a second twin device, with the first twin device in an active state and the second twin device in a frozen state. During the process of the fault detection device updating the first twin device in the preset digital twin system model to the second twin device, the fault detection device activates the second twin device while simultaneously freezing the first twin device, and connects the second twin device to the target data transmission link, while the first twin device ceases all data recording functions.

[0180] In another possible implementation, the preset digital twin system model includes a first twin device and a second twin device, with the first twin device being active and the second twin device being isolated. During the process of the fault detection device updating the first twin device in the preset digital twin system model to the second twin device, the fault detection device activates the second twin device while isolating the first twin device. The first twin device retains all its data recording functions but does not participate in data transmission in the target data transmission link.

[0181] Optionally, the preset digital twin system model includes a first twin device and a second twin device, both of which are active. During the process of the fault detection device updating the first twin device in the preset digital twin system model to the second twin device, the fault detection device maintains the operation of the second twin device while activating the first twin device. It distinguishes the operating parameters of the first and second twin devices based on their respective device identifiers, and both devices operate normally according to their initial configurations.

[0182] For example, such as Figure 8 The diagram illustrates the process by which a fault detection device updates digital twin devices in a preset digital twin system model. The target vehicle includes onboard device A, onboard device B, and onboard device C. The preset digital twin system model includes digital twin device A corresponding to onboard device A, digital twin device B corresponding to onboard device B, and digital twin device C corresponding to onboard device C. Digital twin devices A, B, and C constitute the target data transmission link. If onboard devices A and C are both good components (i.e., normally operating components), and onboard device B is a suspected faulty component (i.e., a component with potential for failure), the fault detection device can construct a digital twin device D corresponding to onboard device B. Digital twin device D is a new component (i.e., the digital twin device of onboard device B in its normal state). Then, the fault detection device replaces digital twin device B in the target data transmission link with digital twin device D to obtain the updated target data transmission link, thereby obtaining the updated preset digital twin system model.

[0183] S703. The fault detection device adjusts the updated preset digital twin system model to the detection state according to the target state parameters, and obtains multiple second fault codes of the updated preset digital twin system model in the detection state to obtain a set of second fault codes.

[0184] S704. The fault detection device determines whether the second fault code set is a proper subset of the first fault code set.

[0185] In some embodiments, if the fault detection device determines that the second fault code set is a proper subset of the first fault code set, the fault detection device may execute S206.

[0186] In other embodiments, if the fault detection device determines that the second fault code set is not a proper subset of the first fault code set, the fault detection device may generate target prompt information.

[0187] Understandably, fault detection devices can, when faced with a large number of fault codes, determine whether the number of fault codes generated during the replacement of the first twin device with the second twin device in a pre-defined digital twin system model has decreased, thereby judging whether there are potential faults in the vehicle-mounted equipment under test. In this way, even with a large number of devices under test, fault detection for each device can be achieved by analyzing the overall change in the number of fault codes in the digital twin system model, avoiding the need to collect and verify parameter information for each twin device. Therefore, this improves the operability and efficiency of fault detection.

[0188] In some embodiments, in S204, if the node type is not the starting node, the fault detection device can determine the upstream and downstream twin devices of the first twin device in the preset digital twin system model, and obtain third parameter information based on a preset time period. Next, the fault detection device can input the third parameter information into the first twin device to obtain first parameter information, which includes parameter information sent by the first twin device to the downstream twin device based on the third parameter information and parameter information generated based on the third parameter information. Similarly, the fault detection device can input the third parameter information into the second twin device to obtain second parameter information, which includes parameter information sent by the second twin device to the downstream twin device based on the third parameter information and parameter information generated based on the third parameter information. Afterwards, if the first parameter information and the second parameter information are the same, the fault detection device can determine whether there is a potential fault in the on-board equipment to be tested by executing S701-S704.

[0189] In some embodiments, to enrich the information on the source of the fault and improve the comprehensiveness of vehicle fault detection, such as Figure 9 As shown, prior to S201, the vehicle fault detection method provided in this application embodiment further includes the following steps:

[0190] S901, The fault detection device acquires the first set of device identifiers, the second set of device identifiers, and the third set of device identifiers.

[0191] The first set of device identifiers includes device identifiers of multiple vehicle-mounted devices determined based on fault phenomenon description information, which is used to indicate the fault status of the target vehicle.

[0192] For example, the fault description information could be "The engine makes a loud noise when the brake is applied".

[0193] In one possible implementation, the fault detection device can acquire fault phenomenon description information input by the user and perform natural language processing on the fault phenomenon description information to obtain the device identifier of the second vehicle-mounted device and the target fault manifestation of the second vehicle-mounted device. Next, the fault detection device can determine the target fault cause in a preset fault knowledge graph based on the device identifier of the second vehicle-mounted device and the target fault manifestation. The target fault cause is the reason that causes the second vehicle-mounted device to exhibit the target fault manifestation. The preset fault knowledge graph includes the device identifiers of multiple preset vehicle-mounted devices, the correspondence between multiple preset fault manifestations and multiple preset fault causes. Then, the fault detection device can acquire the device identifiers of multiple third vehicle-mounted devices corresponding to the target fault cause in the preset fault knowledge graph to obtain a first device identifier set.

[0194] In other words, the fault detection device can use a pre-defined fault knowledge graph, which includes the correspondence between multiple preset vehicle-mounted device identifiers, multiple preset fault manifestations, and multiple preset fault causes, to associate the faulty devices and fault manifestations parsed from the fault phenomenon description information, determine the cause of the fault, and extend from the cause to other vehicle-mounted devices affected by it, thereby obtaining multiple vehicle-mounted devices that need to be fault-detected. This improves the comprehensiveness of vehicle fault detection.

[0195] In one possible design, the number of target failure causes can be multiple.

[0196] In other words, there can be multiple reasons why the second on-board equipment exhibits the target malfunction.

[0197] For example, such as Figure 10 As shown, it illustrates a preset fault knowledge graph that includes device identifiers for multiple preset on-board devices, multiple preset fault manifestations, and multiple preset fault causes, representing the corresponding relationships between them. If the fault description information for vehicle A is "high engine coolant temperature," it can be linked to "engine B (i.e., preset on-board device)" and "high coolant temperature C (i.e., preset fault manifestation)" in the preset fault knowledge graph. Through these two hit entities, the associated set of fault causes can be obtained. The component corresponding to the fault cause, such as "thermostat assembly fault D" corresponding to "thermostat assembly E," is used as the component set for knowledge reasoning (i.e., the first set of device identifiers).

[0198] In this embodiment of the application, the second device identifier set includes device identifiers of multiple vehicle-mounted devices corresponding to the first fault codes.

[0199] In one possible implementation, after obtaining a first set of fault codes, the fault detection device can determine the device identifier of the corresponding on-board equipment in the target vehicle based on each first fault code, so as to obtain a second set of device identifiers.

[0200] It should be noted that the process of determining the device identifier of the vehicle equipment based on the fault code can be found in the existing technology for the description and use of fault codes, and will not be elaborated here.

[0201] In this embodiment of the application, the third device identifier set includes device identifiers of multiple in-vehicle devices specified by the user in the target vehicle.

[0202] In one possible implementation, the fault detection device can receive device identifiers of multiple in-vehicle devices input by the user to obtain a third set of device identifiers.

[0203] S902. The fault detection device determines the set of device identifiers to be detected based on the first set of device identifiers, the second set of device identifiers, and the third set of device identifiers.

[0204] The set of device identifiers to be detected is the union of the first set of device identifiers, the second set of device identifiers, and the third set of device identifiers.

[0205] In this embodiment of the application, S201 may include:

[0206] S903, The fault detection device obtains the device identifier of the vehicle-mounted device to be tested from the set of device identifiers to be tested.

[0207] Among them, the device identifier of the vehicle-mounted device to be tested is the device identifier of any vehicle-mounted device in the set of device identifiers to be tested.

[0208] Understandably, fault detection devices can acquire multiple onboard devices requiring fault detection by obtaining fault codes and their contents reported by the vehicle, user descriptions of the fault symptoms, and devices specified by the user based on personal experience. This enriches the information about the source of the fault and improves the comprehensiveness of vehicle fault detection.

[0209] In some embodiments, since fault information from different sources corresponds to different levels of urgency, and in order to determine the priority of each device and improve the efficiency of fault detection, such as... Figure 11 As shown, after S902, the vehicle fault detection method provided in this application embodiment further includes the following steps:

[0210] S1101, The fault detection device determines the device identifier of at least one first vehicle-mounted device based on the first device identifier set, the second device identifier set, and the third device identifier set.

[0211] Among them, the device identifier of the first vehicle-mounted device is the device identifier of the vehicle-mounted device that is repeated in at least two of the first device identifier set, the second device identifier set, and the third device identifier set.

[0212] For example, if the first set of device identifiers includes: device identifier A, device identifier B and device identifier C, the second set of device identifiers includes: device identifier B and device identifier D, and the third set of device identifiers includes: device identifier B and device identifier C, then the device identifiers of at least one first vehicle-mounted device include: device identifier B and device identifier C.

[0213] S1102. For each device identifier of the first vehicle-mounted device, the fault detection device sums up at least two initial priority levels corresponding to the device identifier of the first vehicle-mounted device to determine the target priority level corresponding to the device identifier of the first vehicle-mounted device, so as to obtain multiple target priority levels.

[0214] Among them, the device identifier of a first vehicle-mounted device corresponds to a target priority level.

[0215] In this embodiment of the application, the device identifiers of all vehicle-mounted devices in the first device identifier set correspond to the first priority level, the device identifiers of all vehicle-mounted devices in the second device identifier set correspond to the second priority level, and the device identifiers of all vehicle-mounted devices in the third device identifier set correspond to the third priority level. The initial priority level is any one of the first priority level, the second priority level, and the third priority level.

[0216] For example, the first device identifier set includes device identifier A, device identifier B, and device identifier C; the second device identifier set includes device identifier B and device identifier D; and the third device identifier set includes device identifier B and device identifier C. If all device identifiers of vehicle-mounted devices in the first device identifier set correspond to the first priority level 1, all device identifiers of vehicle-mounted devices in the second device identifier set correspond to the second priority level 2, and all device identifiers of vehicle-mounted devices in the third device identifier set correspond to the third priority level 3, then the initial priority level corresponding to device identifier B includes the first priority level 1, the second priority level 2, and the third priority level corresponding to device identifier C includes the first priority level 1 and the third priority level 3, and the target priority level corresponding to device identifier B is 6, and the target priority level corresponding to device identifier C is 4.

[0217] S1103. The fault detection device determines the priority level corresponding to the device identifier of each vehicle-mounted device in the set of device identifiers to be detected based on multiple target priority levels, first priority level, second priority level and third priority level.

[0218] For example, if the first device identifier set includes: device identifier A, device identifier B, and device identifier C; the second device identifier set includes: device identifier B and device identifier D; and the third device identifier set includes: device identifier B and device identifier C, and all device identifiers of vehicle-mounted devices in the first device identifier set correspond to the first priority level 1, all device identifiers of vehicle-mounted devices in the second device identifier set correspond to the second priority level 2, and all device identifiers of vehicle-mounted devices in the third device identifier set correspond to the third priority level 3, then the device identifier set to be detected includes: device identifier A, device identifier B, device identifier C, and device identifier D, and the priority level corresponding to device identifier A is 1, the priority level corresponding to device identifier B is 6, the priority level corresponding to device identifier C is 4, and the priority level corresponding to device identifier D is 2.

[0219] In this embodiment of the application, S903 may include S1104.

[0220] S1104. The fault detection device obtains the device identifier of the vehicle-mounted device to be tested from the device identifier set according to the priority level corresponding to the device identifier of each vehicle-mounted device in the device identifier set to be tested.

[0221] Among them, the priority level of the device identifier of the vehicle-mounted device to be tested is higher than the priority level of the device identifier of any other vehicle-mounted device in the set of device identifiers to be tested.

[0222] Understandably, fault information from different sources corresponds to varying degrees of urgency. Therefore, the fault detection device can determine the corresponding priority level based on the fault information from different sources and prioritize the detection of on-board equipment with higher priority during subsequent fault detection. This improves the efficiency of fault detection.

[0223] In some embodiments, after the fault detection device completes fault detection on the first twin device (i.e., S205 above), if the fault detection device determines that the first twin device is a normal component, it will delete the second twin device and restore the mapping relationship between the first twin device and the vehicle-mounted device under test. If the fault detection device determines that the first twin device is a faulty component, it will add the first twin device to the located faulty component set. Furthermore, the fault detection device can recycle and manage the first twin device and its entire lifecycle data, providing a data foundation for subsequent analysis and use.

[0224] In one possible implementation, after the fault detection device completes the above deletion operation, it can remove the device identifier of the on-board equipment to be tested from the set of device identifiers to be tested, obtaining an updated set of device identifiers to be tested, and determine whether the updated set of device identifiers to be tested is empty. If the fault detection device determines that the updated set of device identifiers to be tested is empty, the fault detection of the target vehicle is completed. If the fault detection device determines that the updated set of device identifiers to be tested is not empty, the fault detection device re-extracts components for verification, performing iterative component verification operations (i.e., S201-S205 above), until the updated set of device identifiers to be tested is empty, at which point component extraction stops.

[0225] In one possible design, after the fault detection device stops extracting components, it can obtain the final set of located faulty components and determine whether the set is empty. If the fault detection device determines that the set is empty, it can generate a first prompt message indicating that the currently provided fault information has not located any faulty components, and the conclusion is that there are no faulty components in the set of device identifiers to be tested (this does not mean that the car has no faulty components). The device then suggests that the user supplement the fault information, re-determine a new set of device identifiers to be tested, and start a new round of automated verification of faulty components.

[0226] If the fault detection device determines that the set of faulty components is a non-empty set, the fault detection device can generate a second prompt message. The second prompt message is used to indicate that there is a faulty component in the set of device identifiers to be tested, and to suggest that the user replace the corresponding vehicle-end component entity according to the located faulty component for real vehicle verification.

[0227] The vehicle fault detection method provided in this application will be described below with specific examples. For example... Figure 12 As shown, the fault detection device may include: a fault information collection module, a natural language processing module, a fault knowledge graph retrieval module, a multi-source component fusion module, an automotive digital twin verification system, and a verification result push module.

[0228] Among them, the fault information collection module is used to interact with the user and collect various fault information (such as fault phenomenon description information, fault codes and contents, and user-inferred component identifiers).

[0229] It should be noted that when a car malfunctions, the malfunction includes both visible and invisible parts. The visible part is the fault phenomenon, which the user can perceive and describe; the invisible part is vehicle data, including controller area network (CAN) data, diagnostic trouble codes (DTCs), tags, lengths, values ​​(TLVs), etc., which the user cannot perceive or describe. This application draws on offline diagnostic procedures, and the "user" described below typically refers to repair technicians, but it also applies to car owners.

[0230] First, the fault detection device can collect information on aspects perceptible to the user, namely, descriptions of the fault symptoms. This information is collected through a fault information collection module that interacts with the user. User input can take various forms, such as voice or text. If it's voice, advanced speech recognition converts it to text. Optionally, if a fault code appears, the fault detection device can automatically extract the fault code and its contents, further identifying the components associated with the fault code. If the user has inferred certain components based on the fault symptoms and their experience, this component information collection module also collects that information.

[0231] It should be noted that the fault detection device can operate when at least one of the above three types of fault information is present.

[0232] Natural Language Processing Module: Used to convert unstructured fault descriptions into structured fault information.

[0233] It should be noted that fault descriptions are typically in unstructured text format. The natural language processing (NLP) module needs to cleanse this text, including but not limited to error correction, invalid character removal, symbol standardization, entity extraction, and relation extraction (this involves numerous NLP algorithms, which can be implemented using traditional NLP techniques or large-scale language models). After processing by the NLP module, structured fault information (i.e., device identification and fault manifestation) is obtained.

[0234] Fault knowledge graph retrieval module: used to retrieve the associated set of faulty components based on structured fault phenomenon information (i.e., the first set of equipment identifiers obtained by the aforementioned fault detection device).

[0235] Multi-source component fusion module: This module integrates the components to be verified obtained through different means (such as the component set obtained through exponential inference (i.e., the first device identifier set), the component set obtained through fault code association (i.e., the second device identifier set), and the component set obtained through user inference (i.e., the third device identifier set)) to obtain a unified component set, which serves as the input to the automotive digital twin verification system.

[0236] Automotive digital twin verification system: The system automatically replaces and verifies all components to be verified, and determines whether a component is a faulty component based on its role, thereby obtaining a set of located faulty components.

[0237] Verification result push module: The system pushes the results to the user based on the located faulty component, and collects the user's verification results on the actual vehicle. If the user inputs new fault information, a new round of automated verification will be started.

[0238] In this embodiment of the application, the system architecture of the automotive digital twin verification system is as follows: Figure 13 As shown, it includes: a component extraction and positioning module, a twin data sampling module, a twin component management module, a twin vehicle fault component verification module, and a failure data analysis module. The twin data acquisition module includes: a baseline data sampling submodule, a sampling rule configuration submodule, and a verification data sampling submodule. The twin component management module includes: a component registration submodule, a status management submodule, and a component recycling submodule.

[0239] The component extraction and positioning module is used to select components from the set of components to be verified (i.e., the set of device identifiers to be tested) according to priority, and at the same time locate the corresponding component twin in the twin environment (i.e., the preset digital twin system model) to obtain the corresponding component information.

[0240] It should be noted that the component extraction and positioning module can select components to be verified from the set of components to be verified, and use the selected components as inputs to the twin component management module and the twin data sampling module.

[0241] Twin component management module: Provides component registration, status management and recycling functions.

[0242] It should be noted that the component registration submodule is used to construct new twin components (i.e., new digital twin devices) and uses these new twin components as sampling objects for the verification data sampling submodule. The status management submodule is used to configure the data functions of the digital twin device, manage its operational status (i.e., active, frozen, and isolated states), and synchronize the updated component status of the sampling objects for the verification data sampling submodule. The component recycling submodule is used to manage older twin components with potential faults (e.g., deleting older twin components, recording full lifecycle data), and uses this full lifecycle data as input for the failure data analysis module.

[0243] Twin data sampling module: It is used to sample old twin components and new twin components according to different sampling rules (i.e. node types) to obtain baseline data (i.e. first parameter information) and verification data (i.e. second parameter information), and use the baseline data and verification data as input to the twin vehicle fault component verification module.

[0244] Twin vehicle fault component verification module: Based on benchmark data and verification data, the selected twin components are used to determine faults (i.e., S205), and the verification results are obtained to determine the set of faulty components located.

[0245] Failure Data Analysis Module: Used to analyze the entire lifecycle data of recycled twin components.

[0246] In other words, this application introduces a knowledge graph to extract information from fault phenomena and utilizes three types of fault information for fault component localization, increasing the sources of fault information. Furthermore, while traditional component twins are typically independent in application, the component twins defined in this application establish data links through data transmission, assign component roles, and establish associations. Moreover, unlike existing technologies that require deep human involvement in fault component diagnosis, this application automates the replacement and verification of twin components in the cloud for fault component localization, a first in the industry. This means that deep user involvement is unnecessary; users only need to transmit some fault information, and the fault detection device can automatically determine the faulty component, effectively improving the efficiency of fault component localization. Furthermore, the faulty components used for verification in this application encompass user inference, knowledge reasoning, and fault code association, while also incorporating expert experience and historical experience. This results in broad coverage of potential faulty components during verification, reducing the missed detection rate. This enables the digital transformation of offline diagnostic services. When a vehicle malfunctions, the replacement and verification of faulty components can be completed quickly, replacing the actual component replacement process by offline repair technicians, effectively improving repair efficiency and accuracy.

[0247] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, the vehicle fault detection device or equipment includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0248] This application embodiment can, according to the above method, exemplarily divide a vehicle fault detection device or equipment into functional modules. For example, the vehicle fault detection device or equipment may include functional modules corresponding to each functional division, or two or more functions may be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods.

[0249] Figure 14 This is a block diagram illustrating a vehicle fault detection device according to an exemplary embodiment, the vehicle fault detection device being used to perform... Figure 2 , Figure 4 , Figure 5 , Figure 6 , Figure 7 , Figure 9 and Figure 11 The method is shown. The vehicle fault detection device 1400 includes: an acquisition module 1401 and a processing module 1402.

[0250] The acquisition module 1401 is used to acquire the device identifier of the on-board device to be tested in the target vehicle. The processing module 1402 is used to determine the first twin device and the second twin device corresponding to the on-board device to be tested based on the device identifier. The first twin device is the digital twin device corresponding to the on-board device to be tested in a preset digital twin system model, and the second twin device is the digital twin device constructed based on the initial data of the on-board device to be tested. The preset digital twin system model includes digital twin devices corresponding to any on-board device in the target vehicle. The processing module 1402 is also used to determine the node type of the first twin device in the preset digital twin system model. The acquisition module 1401 is also used to acquire the first parameter information of the first twin device and the second parameter information of the second twin device based on the node type. The processing module 1402 is also used to generate target detection information if the first parameter information and the second parameter information are different. The target detection information is used to indicate that the on-board device to be tested has a potential fault.

[0251] In one possible implementation, both the first parameter information and the second parameter information include sub-parameter information corresponding to multiple preset times within a preset time period. The processing module 1402 is further configured to, if the first parameter information and the second parameter information are different, and the first quantity is less than a first preset quantity threshold, determine a first difference for each preset time based on the preset time, the first parameter information, and the second parameter information, to obtain multiple first differences. The first difference is the difference between two sub-parameter information corresponding to the same preset time in the first parameter information and the second parameter information. One first difference corresponds to one preset time, and the first quantity is the number of preset times within the preset time period. The processing module 1402 is further configured to sum the multiple first differences to determine a target deviation value between the first parameter information and the second parameter information. Specifically, if the target deviation value is greater than or equal to a preset deviation threshold, the processing module 1402 generates target detection information.

[0252] In one possible implementation, both the first parameter information and the second parameter information include sub-parameter information corresponding to multiple preset times within a preset time period. The acquisition module 1401 is further configured to, if the first parameter information and the second parameter information are different, and the first quantity is greater than or equal to a first preset quantity threshold, acquire a target time from the multiple preset times, where the target time is the last time among the multiple preset times, and the first quantity is the number of preset times within the preset time period. The processing module 1402 is further configured to, based on the target time, the first parameter information, and the second parameter information, determine a second difference, where the second difference is the difference between the two sub-parameter information corresponding to the target time in the first parameter information and the second parameter information. Specifically, the processing module 1402 is configured to, if the second difference is greater than or equal to a preset difference threshold, generate target detection information.

[0253] In one possible implementation, the acquisition module 1401 is specifically used to acquire first parameter information and second parameter information based on a preset time period if the node type is a starting node. The first parameter information is the parameter information generated by the first twin device within the preset time period, and the second parameter information is the parameter information generated by the second twin device within the preset time period.

[0254] In one possible implementation, processing module 1402 is further configured to, if the node type is an end node, determine the upstream twin device of the first twin device in the preset digital twin system model. Acquisition module 1401 is specifically configured to acquire third parameter information based on a preset time period, wherein the third parameter information is parameter information sent by the upstream twin device to the first twin device within the preset time period. Processing module 1402 is further configured to input the third parameter information into the first twin device to acquire first parameter information, wherein the first parameter information is parameter information generated by the first twin device based on the third parameter information. Processing module 1402 is further configured to input the third parameter information into the second twin device to acquire second parameter information, wherein the second parameter information is parameter information generated by the second twin device based on the third parameter information.

[0255] In one possible implementation, processing module 1402 is further configured to, if the node type is a relay node, determine the upstream and downstream twin devices of the first twin device in the preset digital twin system model. Acquisition module 1401 is specifically configured to acquire third parameter information based on a preset time period, wherein the third parameter information is the parameter information sent by the upstream twin device to the first twin device within the preset time period. Processing module 1402 is further configured to input the third parameter information into the first twin device to acquire first parameter information, wherein the first parameter information is the parameter information sent by the first twin device to the downstream twin device based on the third parameter information. Processing module 1402 is further configured to input the third parameter information into the second twin device to acquire second parameter information, wherein the second parameter information is the parameter information sent by the second twin device to the downstream twin device based on the third parameter information.

[0256] In one possible implementation, the acquisition module 1401 is further configured to acquire a first fault code set, the first fault code set including multiple first fault codes of the target vehicle in the state to be tested. The processing module 1402 is further configured to determine a second number of first fault codes in the first fault code set. Specifically, if the second number is less than a second preset number threshold, the processing module 1402 determines the node type of the first twin device in a preset digital twin system model.

[0257] In one possible implementation, the acquisition module 1401 is further configured to acquire target state parameters of the preset digital twin system model in the state to be detected if the second quantity is greater than or equal to a second preset quantity threshold. The processing module 1402 is further configured to update the first twin device in the preset digital twin system model to a second twin device, obtaining an updated preset digital twin system model. The processing module 1402 is further configured to adjust the updated preset digital twin system model to the state to be detected according to the target state parameters, and acquire multiple second fault codes of the updated preset digital twin system model in the state to be detected, to obtain a second fault code set. Specifically, the processing module 1402 is configured to generate target detection information if the second fault code set is a proper subset of the first fault code set.

[0258] In one possible implementation, the acquisition module 1401 is further configured to acquire a first device identifier set, a second device identifier set, and a third device identifier set. The first device identifier set includes device identifiers of multiple vehicle-mounted devices determined based on fault phenomenon description information. The second device identifier set includes device identifiers of vehicle-mounted devices corresponding to multiple first fault codes of the target vehicle in the test state. The third device identifier set includes device identifiers of multiple vehicle-mounted devices specified by the user in the target vehicle. The fault phenomenon description information is used to indicate the fault condition of the target vehicle. The processing module 1402 is further configured to determine a device identifier set to be tested based on the first device identifier set, the second device identifier set, and the third device identifier set. The device identifier set to be tested is the union of the first device identifier set, the second device identifier set, and the third device identifier set. Specifically, the acquisition module 1401 is configured to acquire the device identifier of the vehicle-mounted device to be tested from the device identifier set to be tested. The device identifier of the vehicle-mounted device to be tested is the device identifier of any vehicle-mounted device in the device identifier set to be tested.

[0259] In one possible implementation, all device identifiers of vehicle-mounted devices in the first device identifier set correspond to a first priority level, all device identifiers of vehicle-mounted devices in the second device identifier set correspond to a second priority level, and all device identifiers of vehicle-mounted devices in the third device identifier set correspond to a third priority level. The processing module 1402 is further configured to determine at least one device identifier of a first vehicle-mounted device based on the first device identifier set, the second device identifier set, and the third device identifier set. The device identifier of the first vehicle-mounted device is a device identifier of a vehicle-mounted device that is repeated in at least two of the first, second, and third device identifier sets. The processing module 1402 is further configured to, for each device identifier of a first vehicle-mounted device, sum the at least two initial priority levels corresponding to the device identifier of the first vehicle-mounted device to determine a target priority level corresponding to the device identifier of the first vehicle-mounted device, thereby obtaining multiple target priority levels. One device identifier of a first vehicle-mounted device corresponds to one target priority level, and the initial priority level is any one of the first, second, and third priority levels. The processing module 1402 is further configured to determine the priority level corresponding to the device identifier of each vehicle-mounted device in the set of device identifiers to be tested based on multiple target priority levels, a first priority level, a second priority level, and a third priority level. The acquisition module 1401 is specifically configured to acquire the device identifier of the vehicle-mounted device to be tested from the set of device identifiers to be tested based on the priority level corresponding to the device identifier of each vehicle-mounted device in the set of device identifiers to be tested, wherein the priority level corresponding to the device identifier of the vehicle-mounted device to be tested is greater than the priority level corresponding to the device identifier of any other vehicle-mounted device in the set of device identifiers to be tested.

[0260] In one possible implementation, the acquisition module 1401 is further configured to acquire fault phenomenon description information. The processing module 1402 is further configured to perform natural language processing on the fault phenomenon description information to obtain the device identifier of the second vehicle-mounted device and the target fault manifestation of the second vehicle-mounted device. The processing module 1402 is further configured to determine the target fault cause in a preset fault knowledge graph based on the device identifier of the second vehicle-mounted device and the target fault manifestation. The target fault cause is the reason that causes the second vehicle-mounted device to be in the target fault manifestation. The preset fault knowledge graph includes the correspondence between multiple preset vehicle-mounted device identifiers, multiple preset fault manifestations and multiple preset fault causes. Specifically, the acquisition module 1401 is configured to acquire the device identifiers of multiple third vehicle-mounted devices corresponding to the target fault cause in the preset fault knowledge graph to obtain a first device identifier set.

[0261] Regarding the apparatus in the above embodiments, the specific manner in which each unit performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0262] Figure 15 This is a block diagram illustrating an electronic device according to an exemplary embodiment. Figure 15 As shown, the electronic device 1500 includes, but is not limited to, a processor 1501 and a memory 1502.

[0263] The memory 1502 described above is used to store the executable instructions of the processor 1501. It is understood that the processor 1501 is configured to execute instructions to implement the vehicle fault detection method in the above embodiments.

[0264] It should be noted that those skilled in the art will understand that Figure 15 The electronic device structure shown does not constitute a limitation on the electronic device; the electronic device may include, but is not limited to, other electronic devices. Figure 15 This may indicate more or fewer components, or combinations of certain components, or different component arrangements.

[0265] Processor 1501 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in memory 1502, and by calling data stored in memory 1502, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. Processor 1501 may include one or more processing units. Optionally, processor 1501 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into processor 1501.

[0266] The memory 1502 can be used to store software programs and various data. The memory 1502 may primarily include a program storage area and a data storage area, wherein the program storage area may store the operating system, application programs (such as processing units) required by at least one functional module, etc. Furthermore, the memory 1502 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0267] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 1502 including instructions, which can be executed by a processor 1501 of an electronic device 1500 to implement the vehicle fault detection method in the above embodiments.

[0268] In actual implementation, Figure 14 The functions of the acquisition module 1401 and the processing module 1402 can both be provided by Figure 15The processor 1501 calls the computer program stored in the memory 1502 to implement the function. The specific execution process can be found in the description of the vehicle fault detection method section of the previous embodiment, and will not be repeated here.

[0269] Optionally, the computer-readable storage medium may be a non-transitory computer-readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a CD-ROM, magnetic tape, a floppy disk, and an optical data storage device.

[0270] In an exemplary embodiment, this application also provides a computer program product including one or more instructions, which can be executed by a processor of an electronic device to complete the vehicle fault detection method in the above embodiments.

[0271] It should be noted that when one or more instructions in the computer-readable storage medium or computer program product are executed by the processor of the electronic device, they implement the various processes of the above-described vehicle fault detection method embodiments and achieve the same technical effects as the above-described vehicle fault detection method. To avoid repetition, they will not be described again here.

[0272] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0273] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0274] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0275] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0276] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0277] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A vehicle fault detection method, characterized in that, The method includes: Obtain the device identifier of the on-board equipment to be tested in the target vehicle; Based on the device identifier of the vehicle-mounted device to be tested, a first twin device and a second twin device corresponding to the vehicle-mounted device to be tested are determined. The first twin device is the digital twin device corresponding to the vehicle-mounted device to be tested in the preset digital twin system model. The second twin device is a digital twin device constructed based on the initial data of the vehicle-mounted device to be tested. The preset digital twin system model includes the digital twin device corresponding to any vehicle-mounted device in the target vehicle. Determine the node type of the first twin device in the preset digital twin system model; Based on the node type, obtain the first parameter information of the first twin device and the second parameter information of the second twin device; If the first parameter information is different from the second parameter information, target detection information is generated, which is used to indicate that the vehicle-mounted equipment to be detected has potential faults. Wherein, if the node type is a starting node, the first parameter information is the parameter information generated by the first twin device within a preset time period, and the second parameter information is the parameter information generated by the second twin device within the preset time period; or... When the node type is an end node, the first parameter information is parameter information generated by the first twin device based on the third parameter information, the second parameter information is parameter information generated by the second twin device based on the third parameter information, and the third parameter information is parameter information sent by the upstream twin device of the first twin device in the preset digital twin system model to the first twin device within the preset time period; or, When the node type is a relay node, the first parameter information is the parameter information sent by the first twin device to the downstream twin device of the first twin device in the preset digital twin system model based on the third parameter information; the second parameter information is the parameter information sent by the second twin device to the downstream twin device of the first twin device in the preset digital twin system model based on the third parameter information; and the third parameter information is the parameter information sent by the upstream twin device of the first twin device in the preset digital twin system model to the first twin device within the preset time period.

2. The method according to claim 1, characterized in that, Both the first parameter information and the second parameter information include sub-parameter information corresponding to multiple preset times within the preset time period. Before generating the target detection information, the method further includes: If the first parameter information is different from the second parameter information and the first quantity is less than the first preset quantity threshold, then for each preset time, a first difference is determined based on the preset time, the first parameter information and the second parameter information to obtain multiple first differences. The first difference is the difference between two sub-parameter information corresponding to the same preset time in the first parameter information and the second parameter information. One first difference corresponds to one preset time, and the first quantity is the number of preset times in the preset time period. The summation of the plurality of first differences is used to determine the target deviation value between the first parameter information and the second parameter information; Generating the target detection information includes: If the target deviation value is greater than or equal to a preset deviation threshold, the target detection information is generated.

3. The method according to claim 1, characterized in that, Both the first parameter information and the second parameter information include sub-parameter information corresponding to multiple preset times within the preset time period. Before generating the target detection information, the method further includes: If the first parameter information is different from the second parameter information, and the first quantity is greater than or equal to the first preset quantity threshold, then the target time is obtained from the plurality of preset times, the target time is the last time among the plurality of preset times, and the first quantity is the number of preset times within the preset time period; Based on the target time, the first parameter information, and the second parameter information, a second difference is determined. The second difference is the difference between the two sub-parameter information corresponding to the target time in the first parameter information and the second parameter information. Generating the target detection information includes: If the second difference is greater than or equal to a preset difference threshold, then the target detection information is generated.

4. The method according to claim 1, characterized in that, Before determining the node type of the first twin device in the preset digital twin system model, the method further includes: Obtain a first fault code set, the first fault code set including multiple first fault codes of the target vehicle in the test state; Determine the second number of the first fault codes in the first fault code set; Determining the node type of the first twin device in the preset digital twin system model includes: If the second quantity is less than the second preset quantity threshold, then the node type of the first twin device in the preset digital twin system model is determined.

5. The method according to claim 4, characterized in that, The method further includes: If the second quantity is greater than or equal to the second preset quantity threshold, then the target state parameters of the preset digital twin system model in the state to be detected are obtained; The first twin device in the preset digital twin system model is updated to the second twin device to obtain the updated preset digital twin system model; According to the target state parameters, the updated preset digital twin system model is adjusted to the state to be detected, and multiple second fault codes of the updated preset digital twin system model in the state to be detected are obtained to obtain a set of second fault codes. Generating the target detection information includes: If the second fault code set is a proper subset of the first fault code set, then the target detection information is generated.

6. The method according to claim 1, characterized in that, Before obtaining the device identifier of the on-board device to be detected in the target vehicle, the method further includes: Acquire a first device identifier set, a second device identifier set, and a third device identifier set. The first device identifier set includes device identifiers of multiple vehicle-mounted devices determined based on fault phenomenon description information. The second device identifier set includes device identifiers of vehicle-mounted devices corresponding to multiple first fault codes of the target vehicle in the test state. The third device identifier set includes device identifiers of multiple vehicle-mounted devices specified by the user in the target vehicle. The fault phenomenon description information is used to indicate the fault condition of the target vehicle. Based on the first set of device identifiers, the second set of device identifiers, and the third set of device identifiers, a set of device identifiers to be detected is determined, wherein the set of device identifiers to be detected is the union of the first set of device identifiers, the second set of device identifiers, and the third set of device identifiers; The acquisition of the device identifier of the on-board device to be detected in the target vehicle includes: Obtain the device identifier of the vehicle-mounted device to be tested from the set of device identifiers to be tested, wherein the device identifier of the vehicle-mounted device to be tested is the device identifier of any vehicle-mounted device in the set of device identifiers to be tested.

7. The method according to claim 6, characterized in that, In the first set of device identifiers, all device identifiers of vehicle-mounted devices correspond to the first priority level; in the second set of device identifiers, all device identifiers of vehicle-mounted devices correspond to the second priority level; and in the third set of device identifiers, all device identifiers of vehicle-mounted devices correspond to the third priority level. After determining the set of device identifiers to be detected, the method further includes: Based on the first device identifier set, the second device identifier set, and the third device identifier set, at least one device identifier of a first vehicle-mounted device is determined, wherein the device identifier of the first vehicle-mounted device is a device identifier of a vehicle-mounted device that is repeated in at least two of the first device identifier set, the second device identifier set, and the third device identifier set. For each device identifier of the first vehicle-mounted device, at least two initial priority levels corresponding to the device identifier of the first vehicle-mounted device are summed to determine the target priority level corresponding to the device identifier of the first vehicle-mounted device, so as to obtain multiple target priority levels. One device identifier of the first vehicle-mounted device corresponds to one target priority level. The initial priority level is any one of the first priority level, the second priority level, and the third priority level. Based on the plurality of target priority levels, the first priority level, the second priority level, and the third priority level, determine the priority level corresponding to the device identifier of each vehicle device in the set of device identifiers to be detected; The step of obtaining the device identifier of the vehicle-mounted device to be tested from the set of device identifiers to be tested includes: Based on the priority level corresponding to the device identifier of each vehicle-mounted device in the device identifier set to be tested, the device identifier of the vehicle-mounted device to be tested is obtained from the device identifier set to be tested, wherein the priority level corresponding to the device identifier of the vehicle-mounted device to be tested is greater than the priority level corresponding to the device identifier of any other vehicle-mounted device in the device identifier set to be tested.

8. The method according to claim 6, characterized in that, Before obtaining the first set of device identifiers, the method further includes: Obtain the description information of the fault phenomenon; Natural language processing is performed on the fault phenomenon description information to obtain the device identifier of the second vehicle-mounted device and the target fault manifestation of the second vehicle-mounted device; Based on the device identifier of the second vehicle-mounted device and the target fault manifestation, the target fault cause is determined in a preset fault knowledge graph. The target fault cause is the reason that causes the second vehicle-mounted device to be in the target fault manifestation. The preset fault knowledge graph includes the correspondence between multiple preset vehicle-mounted device identifiers, multiple preset fault manifestations and multiple preset fault causes. Obtaining the first device identifier set includes: Obtain the device identifiers of multiple third-party vehicle-mounted devices corresponding to the target fault cause in the preset fault knowledge graph to obtain the first device identifier set.

9. A vehicle fault detection device, characterized in that, The device includes: The acquisition module is used to acquire the device identifier of the on-board device to be detected in the target vehicle; The processing module is used to determine the first twin device and the second twin device corresponding to the vehicle-mounted device under test based on the device identifier of the vehicle-mounted device under test. The first twin device is the digital twin device corresponding to the vehicle-mounted device under test in a preset digital twin system model. The second twin device is a digital twin device constructed based on the initial data of the vehicle-mounted device under test. The preset digital twin system model includes the digital twin device corresponding to any vehicle-mounted device in the target vehicle. The processing module is further configured to determine the node type of the first twin device in the preset digital twin system model; The acquisition module is further configured to acquire first parameter information of the first twin device and second parameter information of the second twin device according to the node type; The processing module is further configured to generate target detection information if the first parameter information is different from the second parameter information, and the target detection information is used to indicate that the vehicle-mounted device to be detected has a potential fault. Wherein, if the node type is a starting node, the first parameter information is the parameter information generated by the first twin device within a preset time period, and the second parameter information is the parameter information generated by the second twin device within the preset time period; or... When the node type is an end node, the first parameter information is parameter information generated by the first twin device based on the third parameter information, the second parameter information is parameter information generated by the second twin device based on the third parameter information, and the third parameter information is parameter information sent by the upstream twin device of the first twin device in the preset digital twin system model to the first twin device within the preset time period; or, When the node type is a relay node, the first parameter information is the parameter information sent by the first twin device to the downstream twin device of the first twin device in the preset digital twin system model based on the third parameter information; the second parameter information is the parameter information sent by the second twin device to the downstream twin device of the first twin device in the preset digital twin system model based on the third parameter information; and the third parameter information is the parameter information sent by the upstream twin device of the first twin device in the preset digital twin system model to the first twin device within the preset time period.

10. An electronic device, characterized in that, include: processor; A memory for storing processor-executable instructions; wherein the processor is configured to execute the instructions to implement the method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, When the computer-executable instructions stored in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is capable of performing the method as described in any one of claims 1 to 8.

Images