CN117409500A

CN117409500A - Abnormality investigation method, abnormality investigation device, abnormality investigation server and storage medium

Info

Publication number: CN117409500A
Application number: CN202311434981.6A
Authority: CN
Inventors: 段月雷
Original assignee: Great Wall Motor Co Ltd
Current assignee: Great Wall Motor Co Ltd
Priority date: 2023-10-31
Filing date: 2023-10-31
Publication date: 2024-01-16

Abstract

The application provides an anomaly investigation method, an anomaly investigation device, a server and a storage medium. The method comprises the steps of acquiring state data of at least one vehicle component associated with vehicle condition abnormal data after acquiring the vehicle condition abnormal data acquired at a first moment, and carrying out abnormality investigation on the vehicle condition abnormal data based on the state data and the vehicle condition abnormal data. This avoids the prior art of performing abnormality investigation on the vehicle condition abnormal data based on various links, and there may be a case of cyclically executing the same step in the process of performing abnormality investigation on the vehicle condition abnormal data. Therefore, the method can improve the processing efficiency of abnormality investigation on the vehicle condition abnormal data by acquiring the state data of at least one vehicle component associated with the vehicle condition abnormal data, performing abnormality investigation on the vehicle condition abnormal data based on the state data and the vehicle condition abnormal data, and not requiring complex multiple link judgment and cyclically executing the same step.

Description

Abnormality investigation method, abnormality investigation device, abnormality investigation server and storage medium

Technical Field

The present application relates to the field of vehicles, and more particularly, to a method, an apparatus, a server, and a storage medium for abnormality detection in the field of vehicles.

Background

With the development of vehicle technology, more and more vehicles enter people's life.

In the related art, there is a vehicle condition display Application (APP) on which vehicle condition abnormality data of a vehicle and a time at which the vehicle condition abnormality data is acquired can be displayed. The vehicle user can acquire a specific failure of the vehicle by feeding back the vehicle condition abnormality data to the background of the vehicle condition display APP. Specifically, after the background of the vehicle condition display APP acquires the vehicle condition abnormal data, background personnel of the vehicle condition abnormal data APP conduct investigation on the vehicle condition abnormal data based on various links so as to locate faults occurring in the vehicle. However, in the process of checking the vehicle condition abnormality data by the background personnel, there may be a case where the same step is cyclically executed.

For example, in the process of performing abnormality investigation on the tire pressure abnormality data collected at the first time, since the tire pressure abnormality data is transmitted to the vehicle condition abnormality data APP by a Telematics BOX (TBOX) on the vehicle, the background person may investigate whether or not there is a failure in the transmission link. Under the condition that the transmission link has no fault, tire pressure data of the previous moment needs to be acquired, when the tire pressure data of the previous moment is abnormal, in order to accurately judge that the reason for the abnormality of the tire pressure data is caused by the acquisition process, the tire pressure data of the previous moment is acquired again, and further whether the acquisition process has a problem or not is determined, and the steps of acquiring and analyzing the tire pressure data of different moments for multiple times can exist, so that the processing efficiency of background investigation is low.

Therefore, a method capable of optimizing the background troubleshooting capability is needed to improve the processing efficiency of troubleshooting the vehicle condition abnormality data.

Disclosure of Invention

The application provides an abnormality investigation method, an abnormality investigation device, a server and a storage medium.

In a first aspect, a method for exception checking is provided, the method comprising: acquiring abnormal vehicle condition data of a vehicle acquired at a first moment; acquiring status data of at least one vehicle component associated with the vehicle condition anomaly data, the status data being indicative of an operational status of the at least one vehicle component at the first time; and based on the state data and the vehicle condition abnormal data, performing abnormality investigation on the vehicle condition abnormal data.

In the above technical solution, after acquiring the vehicle condition abnormal data acquired at the first moment, the present application acquires the state data of at least one vehicle component associated with the vehicle condition abnormal data, and performs abnormality investigation on the vehicle condition abnormal data based on the state data and the vehicle condition abnormal data. This avoids the prior art of performing abnormality investigation on the vehicle condition abnormal data based on various links, and there may be a case of cyclically executing the same step in the process of performing abnormality investigation on the vehicle condition abnormal data. For example, in order to accurately determine whether or not there is an abnormality in the acquisition process, vehicle condition data at different times is acquired, and the vehicle condition data is analyzed. Therefore, according to the scheme, the state data of at least one vehicle component related to the vehicle condition abnormal data is acquired, the vehicle condition abnormal data is subjected to abnormal investigation based on the state data and the vehicle condition abnormal data, multiple-loop judgment is not needed, repeated steps of acquiring the vehicle condition data at different moments and analyzing the abnormality of the vehicle condition data are not needed, and the processing efficiency of the abnormal investigation of the vehicle condition abnormal data can be improved.

With reference to the first aspect, in some possible implementations, performing anomaly investigation on the vehicle condition anomaly data based on the state data and the vehicle condition anomaly data includes: determining whether a target vehicle component of the at least one vehicle component is malfunctioning, the target vehicle component being configured to collect the vehicle condition anomaly data; determining, based on the status data, whether a failure of a vehicle component other than the target vehicle component among the at least one vehicle component has occurred in a case where the target vehicle component has not failed; determining that the abnormality cause of the vehicle condition abnormality data includes an external environmental factor in the case where the other vehicle component does not fail; the method comprises the steps of sending first reminding information to a target terminal, wherein the first reminding information is used for reminding to ignore abnormal vehicle condition data, and the target terminal is a terminal for feeding back the abnormal vehicle condition data; in the event of a failure of the other vehicle component, determining an abnormality cause of the vehicle condition abnormality data includes the other vehicle component failing and being independent of the target vehicle component; and sending first early warning information to the target terminal, wherein the first early warning information is used for reminding the maintenance of the other vehicle components.

In the above-described aspect, whether or not the target vehicle component has failed is preferentially detected, and if the target vehicle component has not failed, the vehicle condition abnormality data is subjected to abnormality detection based on the state data. That is, in the case where the target vehicle component for collecting the vehicle condition abnormality data does not fail, there is a possibility that another vehicle component for assisting in determining the vehicle condition abnormality data fails, and thus the vehicle condition abnormality data is subjected to abnormality investigation based on the state data. Specifically, under the condition that the other vehicle components do not have faults, the abnormal reasons of the vehicle condition abnormal data comprise external environment factors, and first reminding information is sent to the target terminal, so that a vehicle user can acquire the abnormal conditions corresponding to the vehicle condition abnormal data based on the target terminal, the abnormal conditions are caused by the external environment factors, and the vehicle condition abnormal data can be ignored. This can avoid unnecessary panic to the vehicle user. In addition, under the condition that other vehicle components are in failure, determining that the abnormality reasons of the vehicle condition abnormality data comprise that the other vehicle components are in failure and are irrelevant to the target vehicle components, and sending first early warning information to the target terminal so as to remind a vehicle user of repairing the other vehicle components, so that the vehicle user can quickly find out a vehicle problem and solve the vehicle problem.

With reference to the first aspect and the foregoing implementation manners, in some possible implementation manners, after determining whether a target vehicle component of the at least one vehicle component fails, the method further includes: in the event of a failure of the target vehicle component, determining an abnormality cause of the vehicle condition abnormality data includes the failure of the target vehicle component; and sending second early warning information to the target terminal, wherein the second early warning information is used for reminding the maintenance of the target vehicle component.

In the above technical solution, after detecting whether a target vehicle component fails, determining that an abnormality cause of the vehicle condition abnormality data includes that the target vehicle component fails in a case where the target vehicle component fails; and sending second early warning information to the target terminal, wherein the second early warning information is used for reminding the maintenance of the target vehicle component. That is, in the case where it is determined that the abnormality cause of the vehicle condition abnormality data includes that the target vehicle component is malfunctioning, the second warning information may be transmitted to the target terminal, so that the vehicle user can be timely reminded of repairing the target vehicle component, so that the vehicle user can quickly find out and solve the vehicle problem.

With reference to the first aspect and the foregoing implementation manners, in some possible implementation manners, in a case where the target vehicle component fails, determining an abnormality cause of the vehicle condition abnormality data includes after the target vehicle component fails, the method further includes: determining that the abnormality cause of the vehicle condition abnormality data includes that the target vehicle component is faulty and is irrelevant to the other vehicle component under the condition that the other vehicle component is not faulty, wherein the second early warning information is also used for reminding that the abnormality cause of the vehicle condition abnormality data is irrelevant to the other vehicle component; in the event of a failure of the other vehicle component, determining an abnormality cause of the vehicle condition abnormality data includes the failure of the target vehicle component and the failure of the other vehicle component; and sending third early warning information to the target terminal, wherein the third early warning information is used for reminding the maintenance of the target vehicle component and the other vehicle components.

In the above technical solution, when the target vehicle component fails, determining that the abnormality cause of the vehicle condition abnormality data includes that the target vehicle component fails, and when the state data indicates that the other vehicle component does not fail, determining that the abnormality cause includes that the target vehicle component fails and is irrelevant to the other vehicle component, the second warning information is also used to remind that the abnormality cause is irrelevant to the other vehicle component. That is, the abnormality cause of the vehicle condition abnormality data includes only that the target vehicle component is malfunctioning, which enables the vehicle user to clarify the abnormality cause, enabling to deal with the vehicle problem in time. In the event that the status data indicates that the other vehicle component is malfunctioning, determining the cause of the abnormality includes the failure of the target vehicle component and the failure of the other vehicle component; and sending third early warning information to the target terminal, wherein the third early warning information is used for reminding the maintenance of the target vehicle component and the other vehicle components. This enables the vehicle user to repair the target vehicle component and the other vehicle component at the same time, improving the efficiency of handling the vehicle problem.

With reference to the first aspect and the foregoing implementation manners, in some possible implementation manners, determining whether other vehicle components than the target vehicle component in the at least one vehicle component are faulty based on the status data includes: determining that the other vehicle component is faulty when the status data is in the abnormal value range; and under the condition that the state data is in a normal value range, determining that the other vehicle component is not in fault.

In the above technical solution, since the status data is used to indicate the working status of the at least one vehicle component at the first moment, when the status data is in the normal value range, the working status of the other vehicle component is normal, and the other vehicle component is not faulty. Otherwise, the other vehicle component fails.

With reference to the first aspect and the foregoing implementation manners, in some possible implementation manners, determining whether a target vehicle component of the at least one vehicle component is faulty includes: acquiring vehicle condition original data corresponding to the vehicle condition abnormal data acquired by the target vehicle component at a second moment, wherein the second moment is after the first moment; determining that the target vehicle component is faulty in the event that the vehicle condition raw data is abnormal; and under the condition that the vehicle condition original data is normal, determining that the target vehicle component does not fail.

In the above technical solution, the cause of the abnormality of the vehicle condition abnormality data is various, and it may be that the target terminal displaying the vehicle condition abnormality data is faulty, or that there is a problem with the data link for transmission to the target terminal, or the like. Therefore, it is possible to verify whether or not the target vehicle component is malfunctioning by acquiring the vehicle condition raw data corresponding to the vehicle condition abnormality data acquired by the target vehicle component at other times.

With reference to the first aspect and the foregoing implementation manner, in some possible implementation manners, after acquiring the vehicle condition abnormal data of the vehicle acquired at the first moment, the method further includes: displaying the abnormal vehicle condition data; in response to a triggering operation on the vehicle condition abnormality data, the step of acquiring state data of at least one vehicle component associated with the vehicle condition abnormality data is performed.

In the technical scheme, after the vehicle condition abnormal data of the vehicle acquired at the first moment is acquired, the vehicle condition abnormal data is displayed; when the vehicle condition abnormality data is triggered, status data of at least one vehicle component associated with the vehicle condition abnormality data is acquired. This enables the abnormality detection process to be specifically performed after the abnormality detection of the vehicle abnormality data is definitely required.

In a second aspect, there is provided an abnormality investigation apparatus, the apparatus comprising: an acquisition module for: acquiring abnormal vehicle condition data of a vehicle acquired at a first moment; acquiring status data of at least one vehicle component associated with the vehicle condition anomaly data, the status data being indicative of an operational status of the at least one vehicle component at the first time; and the checking module is used for checking the abnormality of the vehicle condition abnormal data based on the state data and the vehicle condition abnormal data.

With reference to the second aspect, in some possible implementations, the apparatus further includes: a determining module for: determining whether a target vehicle component of the at least one vehicle component is malfunctioning, the target vehicle component being configured to collect the vehicle condition anomaly data; determining, based on the status data, whether a failure of a vehicle component other than the target vehicle component among the at least one vehicle component has occurred in a case where the target vehicle component has not failed; determining that the abnormality cause of the vehicle condition abnormality data includes an external environmental factor in the case where the other vehicle component does not fail; the apparatus further comprises: the sending module is used for sending first reminding information to a target terminal, wherein the first reminding information is used for reminding to ignore the abnormal vehicle condition data, and the target terminal is a terminal for feeding back the abnormal vehicle condition data; the determining module is further configured to determine that, in a case where the other vehicle component fails, an abnormality cause of the vehicle condition abnormality data includes that the other vehicle component fails and is independent of the target vehicle component; the sending module is further used for sending first early warning information to the target terminal, wherein the first early warning information is used for reminding maintenance of other vehicle components.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, after determining whether a target vehicle component of the at least one vehicle component has a fault, the determining module is further configured to determine, in a case where the target vehicle component has a fault, that an abnormality cause of the vehicle condition abnormality data includes the fault of the target vehicle component; the sending module is further used for sending second early warning information to the target terminal, and the second early warning information is used for reminding of maintaining the target vehicle component.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, in a case where the target vehicle component fails, determining an abnormality cause of the vehicle condition abnormality data includes, after the target vehicle component fails, the determining module is further configured to: determining that the abnormality cause of the vehicle condition abnormality data includes that the target vehicle component is faulty and is irrelevant to the other vehicle component under the condition that the other vehicle component is not faulty, wherein the second early warning information is also used for reminding that the abnormality cause of the vehicle condition abnormality data is irrelevant to the other vehicle component; in the event of a failure of the other vehicle component, determining an abnormality cause of the vehicle condition abnormality data includes the failure of the target vehicle component and the failure of the other vehicle component; the sending module is further configured to send third early warning information to the target terminal, where the third early warning information is used to remind of repairing the target vehicle component and the other vehicle components.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, the determining module is specifically configured to: determining that the other vehicle component is faulty when the status data is in the abnormal value range; and under the condition that the state data is in a normal value range, determining that the other vehicle component is not in fault.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, the acquiring module is further configured to acquire vehicle condition raw data corresponding to the vehicle condition abnormal data acquired by the target vehicle component at a second moment, where the second moment is after the first moment; the determining module is further configured to: determining that the target vehicle component is faulty in the event that the vehicle condition raw data is abnormal; and under the condition that the vehicle condition original data is normal, determining that the target vehicle component does not fail.

With reference to the second aspect and the foregoing implementation manner, in some possible implementation manners, after acquiring the vehicle condition abnormal data of the vehicle acquired at the first moment, the apparatus further includes: the display module is used for displaying the abnormal data of the vehicle condition; the inspection module is further configured to perform the step of acquiring status data of at least one vehicle component associated with the vehicle condition abnormality data in response to a triggering operation on the vehicle condition abnormality data.

In a third aspect, a server is provided, comprising a memory, a processor and a computer program stored in the memory and running on the processor, wherein the processor, when executing the computer program, causes the server to perform the method of the first aspect or any one of the possible implementation manners of the first aspect.

In a fourth aspect, a computer readable storage medium is provided, in which instructions are stored which, when run on a computer or processor, cause the computer or processor to perform the method of the first aspect or any one of the possible implementations of the first aspect.

Drawings

Fig. 1 is a schematic flow chart of processing abnormal vehicle condition data according to an embodiment of the present application;

FIG. 2 is a schematic flow chart of a method for exception checking provided in an embodiment of the present application;

fig. 3 is a schematic structural diagram of a background server according to an embodiment of the present application;

FIG. 4 is a schematic flow chart of acquiring status data provided by an embodiment of the present application;

FIG. 5 is a block flow diagram of abnormality detection for abnormal vehicle condition data according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a vehicle condition problem traceability tool according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of an abnormality detection apparatus according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

The technical solutions in the present application will be clearly and thoroughly described below with reference to the accompanying drawings. Wherein, in the description of the embodiments of the present application, "a plurality" means two or more than two. The terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as implying or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature.

Fig. 1 is a schematic flow chart of processing abnormal vehicle condition data according to an embodiment of the present application.

In the prior art, after a background person of a vehicle condition display APP obtains vehicle condition abnormal data of a vehicle, the background person checks the vehicle condition abnormal data based on various links to position the problem existing in the vehicle. However, in the process of checking the abnormal vehicle condition data by the background personnel, the situation that the same step is executed in a circulating way may be encountered, so that the processing efficiency of the background checking problem is low.

For example, as shown in fig. 1, the front end of the vehicle condition display APP can receive the tire pressure abnormality data, the tire pressure abnormality data acquired at the first time, the geographical location, and the like. The front end generates a vehicle condition data abnormality question work order based on the tire pressure abnormality data, the first moment and the geographic position. The front end carries out team discussion based on the abnormal problem work order of the vehicle condition data, and determines that the abnormality of the tire pressure abnormal data is caused by the problem of the rear end of the vehicle condition display APP. The front end sends the abnormal problem work orders of the vehicle condition data to a background server of the vehicle condition display APP, and the background server receives the abnormal problem work orders of the vehicle condition data. Because the vehicle condition abnormal data on the vehicle condition display APP is reported by a Telematics BOX (TBOX) on the vehicle, the background server can search the tire pressure reported by the TBOX at the first moment (the tire pressure reported by the TBOX at the vehicle end) and inquire a specific first tire pressure value, wherein the vehicle condition display APP is installed on a target terminal, and the target terminal is a terminal with the control authority of the vehicle. The background server determines whether the first tire pressure value is valid. And under the condition that the first tire pressure value is effective, the background server compares the tire pressure abnormal data with the first tire pressure value and returns a compared processing result to the front end so as to enable a vehicle user to respond to the processing result. When the first tire pressure value is invalid, the background server checks a processing scheme based on a vehicle condition abnormality processing policy to determine whether the tire pressure at the previous time of the first time needs to be acquired. In the case where it is not necessary to acquire the tire pressure at the time immediately before the first time, the background server no longer determines the abnormality cause of the tire pressure abnormality data. Under the condition that the tire pressure at the previous moment needs to be acquired, the background server inquires a second tire pressure value at the previous moment, further determines whether the second tire pressure value is effective or not, and repeats judgment.

In the process of abnormality investigation, the involved links are complex, and a circulation process of repeatedly inquiring tire pressure values at different moments may exist, which greatly reduces the processing efficiency of abnormality investigation.

It should be understood that the vehicle condition abnormality processing strategy in the above-described aspect is used to describe a processing method of abnormality investigation of vehicle condition abnormality data, specifically indicating a processing method for acquiring state data of at least one vehicle component associated with the tire pressure abnormality data.

In order to improve the processing efficiency of abnormality detection of the vehicle condition abnormal data. The application proposes a method for troubleshooting, and a specific embodiment may specifically refer to fig. 2.

Fig. 2 is a schematic flowchart of a method for exception checking according to an embodiment of the present application.

It should be understood that the method for troubleshooting provided in the embodiment of the present application may be applied to a background server of the vehicle condition display APP shown in fig. 1. Specifically, the abnormality investigation method can also be applied to a vehicle condition problem tracing tool in the background server, wherein the vehicle condition problem tracing tool refers to an application program capable of carrying out abnormality investigation on vehicle condition abnormal data through a graphical interface.

Illustratively, as shown in FIG. 2, the method 200 includes:

In step 201, the background server acquires abnormal vehicle condition data of the vehicle acquired at the first moment.

It should be understood that the "vehicle condition abnormality data" in step 201 is state data that is collected at the first time and reported to the vehicle condition display APP by the TBOX for indicating that an abnormality has occurred in the operation state of any one of the vehicle components in the vehicle.

In some embodiments, the vehicle component is a tire and the vehicle anomaly data is an anomalous tire pressure value.

In some embodiments, step 201 comprises: the background server acquires vehicle condition abnormal data fed back by the front end of the vehicle condition display APP, wherein the vehicle condition abnormal data is state data which is acquired at the first moment and is used for indicating the abnormal working state of any vehicle component, and the front end feeds back the vehicle condition abnormal data to the front end of the background server after responding to the triggering operation of the vehicle condition abnormal data.

In some embodiments, the front end is capable of feeding back the vehicle condition abnormality data of the vehicle acquired at the first time to the background server in response to a triggering operation on the vehicle condition abnormality data if it is determined that the abnormality cause of the vehicle condition abnormality data is not a display problem of the vehicle condition display APP.

According to the technical scheme, the abnormal data of the vehicle condition can be fed back to the background server under the condition that the display problem of the vehicle condition display APP is not solved. This can enable the abnormality cause of the vehicle condition abnormality data to be analyzed stepwise, contributing to an expedited determination of the abnormality cause of the vehicle condition abnormality data.

Step 202, a background server obtains status data of at least one vehicle component associated with the vehicle condition anomaly data, the status data being indicative of an operational status of the at least one vehicle component at the first time.

It should be appreciated that the "status data of at least one vehicle component" and the "vehicle condition abnormality data" in step 202 are both used to indicate the operation status of the vehicle component, with the difference that: the vehicle condition abnormality data is state data indicating that an abnormality has occurred in the operation state of any one of the vehicle components, and is used to emphasize the operation state of the abnormality of the vehicle component. And the status data of the at least one vehicle component is used to indicate the operational status of the at least one vehicle component at the first time, but it is not clear whether the operational status of the at least one vehicle component is abnormal.

It should also be appreciated that the "at least one vehicle component" in step 202 described above specifically includes: a target vehicle component for collecting the vehicle condition abnormality data, and other vehicle components for assisting in determining the vehicle condition abnormality data in addition to the target vehicle component.

In some embodiments, the vehicle condition anomaly data is an anomalous tire pressure value. The target vehicle component is a tire pressure sensor, and the other vehicle component is an on-vehicle battery. Specifically, the background server acquires state data of the vehicle-mounted battery for providing electric quantity for the tire pressure sensor under the condition that the abnormal tire pressure value is received.

In a possible implementation, after step 201, the method 200 further includes: the background server displays the abnormal data of the vehicle condition; the background server performs the step of acquiring state data of at least one vehicle component associated with the vehicle condition abnormality data in response to a trigger operation on the vehicle condition abnormality data.

In some embodiments, the triggering operation includes any one of clicking on the vehicle condition anomaly data, voice triggering the vehicle condition anomaly data, gaze triggering the vehicle condition anomaly data, and a target gesture triggering the vehicle condition anomaly data.

In some embodiments, the background server also displays the physical meaning and the first time indicated by the vehicle condition anomaly data.

Optionally, the physical meaning indicated by the first tire pressure value is tire pressure.

In some embodiments, following step 202, the background server displays the current time, the vehicle condition anomaly data, a physical meaning of the vehicle condition anomaly data, a vehicle condition anomaly handling policy for indicating acquisition of the state data of the at least one vehicle component associated with the vehicle condition anomaly data, the state data of the at least one vehicle component, the first time, and a vehicle identification code (Vehicle Identification Number, VIN) of the vehicle.

In step 203, the background server performs abnormality detection on the vehicle condition abnormality data based on the state data and the vehicle condition abnormality data.

It should be understood that step 203 may be understood as: based on the state data and the vehicle condition abnormality data, whether an abnormality cause of the vehicle condition abnormality data is a failure of a target vehicle component for collecting the vehicle condition abnormality data, or other vehicle components for assisting in determining the vehicle condition abnormality data, or neither the target vehicle component nor the other vehicle components is a failure, is influenced only by external environmental factors, or the like is analyzed.

In some embodiments, the abnormal vehicle condition data is an abnormal tire pressure value, and the abnormal cause of the abnormal tire pressure value is the cause that the tire pressure sensor for collecting the abnormal tire pressure value is failed, the vehicle-mounted battery for providing the electric quantity for the tire pressure sensor is failed, or the tire pressure sensor and the vehicle-mounted battery are not failed, and only the tire pressure sensor is collided.

In a possible implementation, step 203 includes: the background server determines whether a target vehicle component of the at least one vehicle component is faulty, wherein the target vehicle component is used for collecting abnormal vehicle condition data; in the event that the target vehicle component does not fail, the background server determines whether other vehicle components of the at least one vehicle component other than the target vehicle component fail based on the status data; the background server determines that the abnormal reasons of the abnormal data of the vehicle condition comprise external environment factors under the condition that the other vehicle components do not have faults; the background server sends first reminding information to a target terminal, wherein the first reminding information is used for reminding to ignore the abnormal vehicle condition data, and the target terminal is a terminal for feeding back the abnormal vehicle condition data; in the event of a failure of the other vehicle component, the background server determines that the cause of the abnormality of the vehicle condition abnormality data includes that the other vehicle component is failed and is independent of the target vehicle component; the background server sends first early warning information to the target terminal, wherein the first early warning information is used for reminding maintenance of other vehicle components.

In some embodiments, the target terminal may be capable of displaying the first alert message and/or voice broadcasting the first alert message. The target terminal can display the first early warning information and/or broadcast the first early warning information in a voice mode.

In some embodiments, the background server determines a target store around the vehicle that is capable of servicing the other vehicle component based on the geographic location where the vehicle is located and information that the other vehicle component is malfunctioning; the background server transmits information of the target store and a travel route of the vehicle from the geographic location to the target store to the target terminal.

In the above technical solution, the background server transmits the information of the target shop and the travel route of the vehicle from the geographic location to the target shop to the target terminal. The method can enable the vehicle user to quickly determine the related information of the target store for repairing other vehicle components through the target terminal, and quickly reach the target store through the driving route so as to quickly repair the other vehicle components.

In some embodiments, the background server determining whether a target vehicle component of the at least one vehicle component is malfunctioning comprises: the background server acquires vehicle condition original data corresponding to the vehicle condition abnormal data, which is acquired by the target vehicle component at a second moment, wherein the second moment is after the first moment; the background server determines that the target vehicle component fails under the condition that the original data of the vehicle condition is abnormal; in the case where the vehicle condition raw data is normal, the background server determines that the target vehicle component has not failed.

It should be understood that the "vehicle condition raw data" in the above-described scheme refers to the state data collected by the target vehicle component in the vehicle end at the second moment, and is not reported to the vehicle condition display APP via TBOX. "the vehicle condition raw data corresponding to the vehicle condition abnormality data" can be understood specifically as: the collecting time of the original data of the vehicle condition is different from that of the abnormal data of the vehicle condition, the physical meaning is the same, the original data of the vehicle condition is not reported to the vehicle condition display APP, and the abnormal data of the vehicle condition is reported to the vehicle condition display APP. The second time is any time after the first time, and corresponds to the second time, and the first time is a history time. In some embodiments, the second time may be a current time of abnormality investigation of the vehicle condition abnormality data.

It should also be appreciated that the above scheme can be understood as: and deducing whether the target vehicle component fails or not according to the vehicle condition original data at the second moment. Since the status data is used to indicate the operating status of the at least one vehicle component at the first moment, the operating status of the target vehicle component is normal and the target vehicle component is not faulty if the status data is in a normal range of values. Conversely, the target vehicle component fails.

In some embodiments, after the background server determines whether the target vehicle component of the at least one vehicle component has failed, the method further comprises: in the event that the target vehicle component fails, the background server determines that the cause of the abnormality of the vehicle condition abnormality data includes that the target vehicle component fails; the background server sends second early warning information to the target terminal, wherein the second early warning information is used for reminding the maintenance of the target vehicle component.

In some embodiments, the target terminal can display the second early warning information and/or voice broadcast the second early warning information.

In some embodiments, in the event that the target vehicle component fails, the background server determines that the cause of the anomaly of the vehicle condition anomaly data includes that the target vehicle component fails, the method 200 further comprises: the background server determines that the abnormality cause of the vehicle condition abnormality data includes that the target vehicle component is failed and is irrelevant to the other vehicle component under the condition that the other vehicle component is not failed, and the second early warning information is also used for reminding that the abnormality cause of the vehicle condition abnormality data is irrelevant to the other vehicle component; in the event of a failure of the other vehicle component, the background server determines that the cause of the abnormality of the vehicle condition abnormality data includes the failure of the target vehicle component and the failure of the other vehicle component; the background server sends third early warning information to the target terminal, wherein the third early warning information is used for reminding the maintenance of the target vehicle component and the other vehicle components.

In some embodiments, the target terminal can display the third warning information and/or voice broadcast the third warning information.

In some embodiments, the background server determining whether other vehicle components of the at least one vehicle component than the target vehicle component are malfunctioning based on the status data comprises: when the state data is in an abnormal value range, the background server determines that the other vehicle component fails; and under the condition that the state data is in a normal value range, the background server determines that the other vehicle component does not fail.

Fig. 3 is a schematic structural diagram of a background server according to an embodiment of the present application.

Illustratively, as shown in fig. 3, the background server may be implemented by a remote service provider (Telematics Service Provider, TSP) platform, and an operation interface (TSP operation interface) of the TSP platform includes the vehicle condition problem tracing tool, and further includes a remote control debugging tool, a vehicle condition parsing debugging tool, a bicycle visual monitoring tool, and a gateway configuration tool. The remote control debugging tool is used for realizing remote test and control of the vehicle; the vehicle condition analysis and debugging tool is used for analyzing and controlling the states of vehicle components in the vehicle; the bicycle visual monitoring tool is used for monitoring the individual vehicles; the gateway configuration tool is used to configure a secure communication link between the vehicle and an external network. A plurality of vehicle services may be implemented by the plurality of tools. For example, travel services, remote control of vehicles (vehicle remote control), vehicle condition resolution, V2X (Vehicle to Everything) services, adaptation of various application protocols in vehicles (protocol adaptation), correspondence between people and vehicles (person-to-vehicle relationship), electronic fencing (anti-theft alarm system of vehicles), vehicle sharing, high-speed assistance for high-speed automatic Navigation On Hilot (NOH), automatic cruise control, service suites (providing vehicles with a series of related service items to meet various demands of vehicle users), bluetooth keys, energy management, autonomous parking assistance (Automated Valet Parking, AVP) system parking, remote diagnosis, subscription center (providing regularly updated electronic newspapers for vehicles), security alarms, ECALL (emergency rescue call of vehicles), data resolution and distribution, FOTA upgrades (updating software On vehicles through a connection network), etc. The plurality of vehicle services obtain vehicle data, equipment data and the like, and can provide data query/synchronization services for a plurality of three-party applications (positioning applications, navigation applications, automatic driving applications and the like). The service core domain provided by the TSP platform comprises a message center (user message and user short message) and a user center (account registration, account binding and security password). The service execution end corresponding to the service provided by the TSP platform comprises TBOX, head-up display in the vehicle and various Application programs (APP). Among them, the front end customer service of the APP and the after-sales (background server) of the TSP operation can realize various vehicle services through tools in the TSP platform.

Fig. 4 is a schematic flow chart of acquiring status data according to an embodiment of the present application.

Illustratively, as shown in fig. 4, the vehicle condition problem traceability tool acquires vehicle condition abnormality data of the vehicle acquired at the first time. The vehicle condition problem tracing tool acquires state data of at least one vehicle component which is reported by the TBOX and is related to the vehicle condition abnormal data after being analyzed by the protocol, wherein the state data is used for indicating the working state of the at least one vehicle component at the first moment. Further, the vehicle condition problem tracing tool performs abnormality detection on the vehicle condition abnormality data based on the state data and the vehicle condition abnormality data.

Fig. 5 is a flowchart of abnormality checking for vehicle condition abnormality data according to an embodiment of the present application.

By way of example, a process of multi-terminal interaction is described as shown in FIG. 5. The multi-terminal includes a user, a front end of a vehicle display APP, a background server, and a TBOX. Specifically, the front end of the vehicle condition display APP receives user feedback, specifically receives vehicle condition abnormal data, a first time of the vehicle condition abnormal data acquisition, a geographic position, and the like. The front end generates a vehicle condition data abnormality question work order based on the vehicle condition abnormality data, the first time and the geographic location. The front end carries out team discussion based on the abnormal problem work order of the vehicle condition data, and determines whether the abnormal reason of the vehicle condition abnormal data is the display problem of the vehicle condition display APP. When it is determined that the cause of the abnormality is a display problem, the vehicle condition display APP processes the display problem and outputs the processing result. And if the abnormality cause is not a display problem, the front end sends the vehicle condition data abnormality problem work order to a background server of the vehicle condition display APP, and the background server receives the vehicle condition data abnormality problem work order. The backend server determines if it is a problem with TBOX. When the background server determines that the problem is not TBOX, the background server processes the vehicle condition abnormal data to obtain a processing result and sends the processing result to the front end. If the background server determines that the vehicle condition data is a problem, the background server transmits the vehicle condition data abnormality problem ticket to the TBOX, which receives the vehicle condition data abnormality problem ticket. The TBOX obtains a processing result based on the abnormal problem work order analysis problem of the vehicle condition data, and sends the processing result to the front end. The vehicle condition display APP outputs a processing result so that a user responds to the processing result.

Fig. 6 is a schematic diagram of a vehicle condition problem tracing tool according to an embodiment of the present application.

For example, after the vehicle condition problem tracing tool acquires the vehicle condition abnormality data of the vehicle acquired at the first time, a first interface is displayed as shown in (a) in fig. 6, where the VIN code (LUAU 2AUB3GE 383467), the current time (2023/10/1 12:15) and a table are displayed, where the table includes the vehicle condition abnormality data (1.5 bar), the physical meaning (tire pressure) of the vehicle condition abnormality data and the first time (2023/10/1 12:10). The vehicle condition problem tracing tool responds to the clicking operation of the vehicle condition abnormal data, displays a second interface as shown in (b) in fig. 6, and displays a vehicle condition abnormal processing strategy and state data (the electric quantity of the vehicle-mounted battery is 50% and ON) of at least one vehicle component ON the basis of the first interface. The vehicle condition abnormality processing policy is used to instruct acquisition of status data of at least one vehicle component (specifically, the target vehicle component is a tire pressure sensor, and the other vehicle components are on-vehicle batteries) associated with the vehicle condition abnormality data.

Fig. 7 is a schematic structural diagram of an abnormality detection device according to an embodiment of the present application.

Illustratively, as shown in FIG. 7, the apparatus 700 includes:

a receiving module 701, configured to obtain abnormal vehicle condition data of a vehicle acquired at a first moment;

an acquisition module 702 for acquiring status data of at least one vehicle component associated with the vehicle condition anomaly data, the status data being indicative of an operating status of the at least one vehicle component at the first time;

an troubleshooting module 703 is configured to troubleshoot the vehicle condition abnormality data based on the state data and the vehicle condition abnormality data.

Optionally, the apparatus 700 further comprises: a determining module for: determining whether a target vehicle component of the at least one vehicle component is malfunctioning, the target vehicle component being configured to collect the vehicle condition anomaly data; determining, based on the status data, whether a failure of a vehicle component other than the target vehicle component among the at least one vehicle component has occurred in a case where the target vehicle component has not failed; determining that the abnormality cause of the vehicle condition abnormality data includes an external environmental factor in the case where the other vehicle component does not fail; the apparatus 700 further comprises: the sending module is used for sending first reminding information to a target terminal, wherein the first reminding information is used for reminding to ignore the abnormal vehicle condition data, and the target terminal is a terminal for feeding back the abnormal vehicle condition data; the determining module is further configured to determine that, in a case where the other vehicle component fails, an abnormality cause of the vehicle condition abnormality data includes that the other vehicle component fails and is independent of the target vehicle component; the sending module is further used for sending first early warning information to the target terminal, wherein the first early warning information is used for reminding maintenance of other vehicle components.

Optionally, after determining whether a target vehicle component of the at least one vehicle component fails, the determining module is further configured to determine that an abnormality cause of the vehicle condition abnormality data includes that the target vehicle component fails, in a case where the target vehicle component fails; the sending module is further used for sending second early warning information to the target terminal, and the second early warning information is used for reminding of maintaining the target vehicle component.

Optionally, in the case that the target vehicle component fails, determining the cause of the abnormality of the vehicle condition abnormality data includes, after the target vehicle component fails, the determining module further configured to: determining that the abnormality cause of the vehicle condition abnormality data includes that the target vehicle component is faulty and is irrelevant to the other vehicle component under the condition that the other vehicle component is not faulty, wherein the second early warning information is also used for reminding that the abnormality cause of the vehicle condition abnormality data is irrelevant to the other vehicle component; in the event of a failure of the other vehicle component, determining an abnormality cause of the vehicle condition abnormality data includes the failure of the target vehicle component and the failure of the other vehicle component; the sending module is further configured to send third early warning information to the target terminal, where the third early warning information is used to remind of repairing the target vehicle component and the other vehicle components.

Optionally, the determining module is specifically configured to: determining that the other vehicle component is faulty when the status data is in the abnormal value range; and under the condition that the state data is in a normal value range, determining that the other vehicle component is not in fault.

Optionally, the acquiring module 702 is further configured to acquire vehicle condition raw data corresponding to the vehicle condition abnormal data acquired by the target vehicle component at a second time, where the second time is after the first time; the determining module is further configured to: determining that the target vehicle component is faulty in the event that the vehicle condition raw data is abnormal; and under the condition that the vehicle condition original data is normal, determining that the target vehicle component does not fail.

Optionally, after acquiring the vehicle condition abnormality data of the vehicle acquired at the first time, the apparatus 700 further includes: the display module is used for displaying the abnormal data of the vehicle condition; the checking module 703 is further configured to perform a step of acquiring status data of at least one vehicle component associated with the vehicle condition abnormality data in response to a triggering operation on the vehicle condition abnormality data.

Illustratively, as shown in FIG. 8, the server 800 includes: a memory 801, a processor 802, and a computer program 803 stored in the memory 801 and running on the processor 802, wherein the processor 802, when executing the computer program 803, causes the server to perform any of the methods of anomaly investigation described previously.

In some embodiments, the server is a background server of the vehicle condition display APP.

In this embodiment, the server may be divided into functional modules according to the above method example, for example, each functional module may be corresponding to one processing module, or two or more functions may be integrated into one processing module, where the integrated modules may be implemented in a hardware form. It should be noted that, in this embodiment, the division of the modules is schematic, only one logic function is divided, and another division manner may be implemented in actual implementation.

In the case of dividing each function module with corresponding each function, the server may include: the system comprises an acquisition module, an investigation module, a detection module, a sending module, a determination module, a display module and the like. It should be noted that, all relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.

The server provided in this embodiment is configured to perform the above-described method for exception checking, so that the same effects as those of the above-described implementation method can be achieved.

In case of an integrated unit, the server may comprise a processing module, a storage module. The processing module can be used for controlling and managing the action of the server. The storage modules may be used for the server to execute, inter alia, program code and data.

Wherein the processing module may be a processor or controller that may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the present disclosure. A processor may also be a combination of computing functions, e.g., including one or more microprocessors, digital signal processing (digital signal processing, DSP) and microprocessor combinations, etc., and a memory module may be a memory.

The present embodiment provides a computer-readable storage medium having instructions stored therein that, when executed on a computer or processor, cause the computer or processor to perform any of the methods of anomaly investigation described above.

The present embodiment also provides a computer program product containing instructions, which when executed on a computer or a processor, cause the computer or the processor to perform the above-mentioned related steps to implement any of the methods of anomaly investigation described above.

The server, the computer readable storage medium, the computer program product or the chip containing the instructions provided in this embodiment are used to execute the corresponding method provided above, so that the benefits achieved by the method can refer to the benefits in the corresponding method provided above, and are not repeated herein.

It will be appreciated by those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules or units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of anomaly investigation, the method comprising:

acquiring abnormal vehicle condition data of a vehicle acquired at a first moment;

acquiring state data of at least one vehicle component associated with the vehicle condition abnormality data, the state data being used to indicate an operating state of the at least one vehicle component at the first time;

and based on the state data and the vehicle condition abnormal data, performing abnormality investigation on the vehicle condition abnormal data.

2. The method according to claim 1, wherein the abnormality check of the vehicle condition abnormality data based on the state data and the vehicle condition abnormality data includes:

determining whether a target vehicle component of the at least one vehicle component is faulty, the target vehicle component being configured to collect the vehicle condition anomaly data;

Determining, in the event that the target vehicle component does not fail, whether a further vehicle component of the at least one vehicle component other than the target vehicle component fails based on the status data;

determining that the abnormality cause of the vehicle condition abnormality data includes an external environmental factor in the case where the other vehicle component does not fail; the method comprises the steps of sending first reminding information to a target terminal, wherein the first reminding information is used for reminding to ignore the abnormal vehicle condition data, and the target terminal is a terminal for feeding back the abnormal vehicle condition data;

in the event of a failure of the other vehicle component, determining an abnormality cause of the vehicle condition abnormality data includes the other vehicle component failing and being independent of the target vehicle component; and sending first early warning information to the target terminal, wherein the first early warning information is used for reminding maintenance of other vehicle components.

3. The method of claim 2, wherein after the determining whether a target vehicle component of the at least one vehicle component has failed, the method further comprises:

determining, in the event of a failure of the target vehicle component, an abnormality cause of the vehicle condition abnormality data includes the failure of the target vehicle component;

And sending second early warning information to the target terminal, wherein the second early warning information is used for reminding the maintenance of the target vehicle component.

4. The method of claim 3, wherein the determining of the cause of the abnormality of the vehicle condition abnormality data in the event of a failure of the target vehicle component comprises, after the failure of the target vehicle component, the method further comprising:

determining that the abnormality cause of the vehicle condition abnormality data includes that the target vehicle component is faulty and is irrelevant to the other vehicle component when the other vehicle component is not faulty, wherein the second early warning information is also used for reminding that the abnormality cause of the vehicle condition abnormality data is irrelevant to the other vehicle component;

determining, in the event of a failure of the other vehicle component, an abnormality cause of the vehicle condition abnormality data including a failure of the target vehicle component and a failure of the other vehicle component; and sending third early warning information to the target terminal, wherein the third early warning information is used for reminding the maintenance of the target vehicle component and the other vehicle components.

5. The method of claim 2, wherein the determining whether other of the at least one vehicle component than the target vehicle component is malfunctioning based on the status data comprises:

Determining that the other vehicle component is faulty when the state data is in an abnormal value range;

and under the condition that the state data is in a normal value range, determining that the other vehicle components do not have faults.

6. The method of claim 2, wherein the determining whether a target vehicle component of the at least one vehicle component is malfunctioning comprises:

acquiring vehicle condition original data corresponding to the vehicle condition abnormal data acquired by the target vehicle component at a second moment, wherein the second moment is after the first moment;

determining that the target vehicle component is faulty in the event that the vehicle condition raw data is abnormal;

and under the condition that the original data of the vehicle condition is normal, determining that the target vehicle component does not fail.

7. The method of claim 1, wherein after the acquiring the vehicle condition abnormality data of the vehicle acquired at the first time, the method further comprises:

displaying the abnormal vehicle condition data;

the step of acquiring state data of at least one vehicle component associated with the vehicle condition abnormality data is performed in response to a trigger operation on the vehicle condition abnormality data.

8. An anomaly investigation apparatus, the apparatus comprising:

the determining module is used for acquiring abnormal vehicle condition data of the vehicle acquired at the first moment;

an acquisition module for acquiring status data of at least one vehicle component associated with the vehicle condition anomaly data, the status data being for indicating an operating status of the at least one vehicle component at the first time;

and the checking module is used for checking the abnormality of the vehicle condition abnormal data based on the state data and the vehicle condition abnormal data.

9. A server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, causes the server to perform the anomaly investigation method of any one of claims 1 to 7.

10. A computer readable storage medium having instructions stored therein which, when executed on a computer or processor, cause the computer or processor to perform the anomaly investigation method of any of claims 1 to 7.