Vehicle fault remote diagnosis method, device, server and system

Abstract

The invention relates to the technical field of vehicle fault diagnosis, and provides a vehicle fault remote diagnosis method, device, server and system. According to the technical scheme provided by one or more embodiments of the invention, the remote server further screens the fault code corresponding to the currently-lightened indicator light of the vehicle from the current fault code information reported by the vehicle, namely, the fault codes are filtered and screened layer by layer based on the indicator light and the fault code information, so that the fault code filtering efficiency is improved. According to the vehicle fault diagnosis method and device, the vehicle fault code is screened out, the fault type information of the vehicle is determined according to the screened fault code, the accuracy of the determined fault type information can be improved, the reliability and accuracy of remote fault diagnosis are improved, more accurate and reliable after-sales service is provided for a vehicle user in time, and the user experience and the fault diagnosis and maintenance efficiency are improved.

Description

Technical Field

[0001] The present disclosure relates to the field of vehicle fault diagnosis, and in particular to a remote diagnosis method, device, server and system for vehicle faults. Background Art

[0002] With the rapid development of vehicle intelligence and networking, the overall software and hardware systems of vehicles are becoming increasingly complex. Accordingly, when a vehicle fails, the difficulty of fault location and analysis is also increasing. In the traditional vehicle maintenance process, for complex vehicle failures, it is often necessary to use a variety of detection methods such as OBDⅡ diagnostic instruments and maintenance experience to determine the fault location and cause, resulting in low work efficiency, low accuracy, and low maintenance quality.

[0003] In recent years, with the development of intelligent connected vehicles, vehicle companies have remotely collected fault information reported by vehicles, identified faults in the cloud, and made full use of the computing power of cloud servers to locate and analyze complex faults, hoping to quickly identify vehicle problems and achieve remote diagnosis of vehicle faults.

[0004] Currently, in the existing remote diagnosis methods, when a vehicle breaks down, the cloud server determines the failed vehicle component and the major fault category based on the vehicle's fault code information and obtains the fault diagnosis results.

[0005] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of the present disclosure and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because these solutions are described in the background technology section of the present disclosure. Summary of the invention

[0006] In the above-mentioned related technologies, the cause or type of fault can be determined directly based on the vehicle's fault code information. However, with the development of vehicle technology, intelligent networked vehicles integrate a large number of complex software and hardware systems, and the various system components are interrelated or dependent on each other. When a certain component of the vehicle fails, it may cause a chain reaction in other components and fail to work properly, which in turn causes multiple components to generate fault codes at the same time. Therefore, it is difficult to effectively filter out interference information by simply using fault code information to determine the major fault category and detailed fault, which is easy to cause misjudgment and wrong judgment, resulting in unreliable fault diagnosis results.

[0007] In view of this, the embodiments of the present disclosure provide a remote diagnosis method, device, server and system for vehicle faults. The remote server further screens the fault code corresponding to the indicator light currently lit in the vehicle from the current fault code information reported by the vehicle, that is, filters and screens the fault code layer by layer based on the indicator light and fault code information, and determines the fault type information of the vehicle according to the screened fault code, which can improve the accuracy of the determined fault type information, improve the reliability and accuracy of remote fault diagnosis, provide more accurate and reliable after-sales service to vehicle users in a timely manner, and improve user experience and the efficiency of fault diagnosis and maintenance.

[0008] According to a first aspect of an embodiment of the present disclosure, a remote diagnosis method for vehicle faults is provided, the method comprising: a server obtains current indicator light information of the vehicle from a vehicle, and determines whether the vehicle has a possibility of fault based on the indicator light information; when it is determined that the vehicle has a possibility of fault, the server determines first fault code information corresponding to the indicator light that is lit in the indicator light information based on a preset rule; the server obtains current candidate fault code information of the vehicle from the vehicle, and uses it as second fault code information; the server compares the first fault code information with the second fault code information, and when the second fault code information contains a fault code included in the first fault information, determines that the vehicle has a fault, and determines the fault type information of the vehicle based on the fault code.

[0009] In combination with the first aspect, in an optional implementation, the method further includes: the server performs validity verification on the reported data of the vehicle, the reported data including the indicator light information and the candidate fault code information; when the validity verification passes, a judgment is made as to whether there is a possibility of a fault in the vehicle based on the indicator light information.

[0010] In combination with the first aspect, in an optional embodiment, determining whether the vehicle has a possibility of a fault based on the indicator light information includes: determining the state of an indicator light of a preset type based on the indicator light information; and determining that the vehicle has a possibility of a fault when at least one indicator light of a preset type is continuously lit for a preset time period.

[0011] In combination with the first aspect, in an optional implementation, the first fault code information corresponding to the indicator light that is lit in the indicator light information is determined according to preset rules, including: searching for the fault code corresponding to the indicator light that is lit in the indicator light information in a pre-generated mapping relationship table between indicator lights and fault codes; and generating the first fault code information based on a set of all corresponding fault codes.

[0012] In combination with the first aspect, in an optional implementation, in a pre-generated mapping relationship table between indicator lights and fault codes, the fault code corresponding to the indicator light that is lit in the indicator light information is searched, including: grouping the indicator lights that are lit in the indicator light information, and determining the fault code corresponding to each group of indicator lights in the mapping relationship table.

[0013] In combination with the first aspect, in an optional implementation, determining the fault type information of the vehicle based on the fault code includes: separately determining the fault type corresponding to each of the fault codes; deduplicating the fault types; and generating fault type information based on the deduplicated fault types.

[0014] In combination with the first aspect, in an optional implementation, the method further includes: the server sending the fault type information of the vehicle to the vehicle to notify the user of the vehicle.

[0015] In combination with the first aspect, in an optional implementation, the method further includes: the server generating rescue information of the vehicle according to the fault type information of the vehicle and the location information of the vehicle.

[0016] According to a second aspect of an embodiment of the present disclosure, a remote diagnosis device for vehicle faults is provided, wherein the device is arranged in a server, and comprises: a first acquisition unit, which acquires current indicator light information of the vehicle from the vehicle; a first determination unit, which determines whether the vehicle has a possibility of fault according to the indicator light information; a second determination unit, which determines, when determining that the vehicle has a possibility of fault, first fault code information corresponding to the lighted indicator light in the indicator light information according to a preset rule; a second acquisition unit, which acquires current candidate fault code information of the vehicle from the vehicle and uses it as second fault code information; a third determination unit, which compares the first fault code information with the second fault code information, and determines that the vehicle has a fault when the second fault code information contains a fault code included in the first fault information, and determines the fault type information of the vehicle according to the fault code.

[0017] In combination with the second aspect, in an optional embodiment, the device also includes: a verification unit, which performs validity verification on the reported data of the vehicle, the reported data including the indicator light information and the candidate fault code information; when the validity verification passes, it is determined whether there is a possibility of a fault in the vehicle based on the indicator light information.

[0018] In combination with the second aspect, in an optional embodiment, the first determination unit determines the status of an indicator light of a preset type based on the indicator light information; and when at least one indicator light of a preset type continues to light up for a preset time period, it is determined that there is a possibility of a fault in the vehicle.

[0019] In combination with the second aspect, in an optional implementation, the second determination unit searches for the fault code corresponding to the lit indicator light in the indicator light information in a pre-generated mapping relationship table between indicator lights and fault codes; and generates the first fault code information based on a set of all corresponding fault codes.

[0020] In combination with the second aspect, in an optional implementation, the second determination unit groups the lit indicator lights in the indicator light information, and determines the fault code corresponding to each group of indicator lights in the mapping relationship table.

[0021] In combination with the second aspect, in an optional implementation, the third determination unit determines the fault type corresponding to each of the fault codes respectively; and deduplicates the fault types; and generates fault type information based on the deduplicated fault types.

[0022] In combination with the second aspect, in an optional implementation, the device further includes: a sending unit, which sends the fault type information of the vehicle to the vehicle to notify the user of the vehicle.

[0023] In combination with the second aspect, in an optional implementation, the device further includes: a generation unit, which generates rescue information of the vehicle based on the fault type information of the vehicle and the location information of the vehicle.

[0024] According to a third aspect of an embodiment of the present disclosure, a server is provided, wherein the server includes the device provided in any implementation of the second aspect above.

[0025] According to the fourth aspect of the embodiment of the present disclosure, a remote diagnosis system for vehicle faults is provided, the system comprising: at least one vehicle, which reports data to a server, the reported data including at least indicator light information and candidate fault code information; a server, which determines whether the vehicle has a possibility of fault based on the indicator light information; when it is determined that the vehicle has a possibility of fault, determines first fault code information corresponding to the lighted indicator light in the indicator light information according to a preset rule, the server compares the candidate fault code information in the reported data with the first fault code information corresponding to the lighted indicator light, and when the first fault code information corresponding to the lighted indicator light contains a fault code included in the candidate fault code information in the reported data, it is determined that the vehicle has a fault, and the fault type information of the vehicle is determined based on the fault code.

[0026] In combination with the fourth aspect, in an optional implementation, the server also sends the fault type information of the vehicle and the maintenance point information near the vehicle to the vehicle.

[0027] In combination with the fourth aspect, in an optional implementation, the server also generates rescue information of the vehicle based on the fault type information of the vehicle and the location information of the vehicle, and the system also includes: a maintenance outlet, which receives the location information and rescue information of the vehicle from the server and generates rescue dispatch information.

[0028] One of the beneficial effects of the disclosed embodiment is that the remote server further screens the fault code corresponding to the indicator light currently lit in the vehicle from the current fault code information reported by the vehicle, and determines the fault type information of the vehicle based on the screened fault code. Thus, based on the dual judgment mechanism of the indicator light and the fault code information, the fault interference factors are filtered, the accuracy of the determined fault type information can be improved, the reliability and accuracy of the remote fault diagnosis can be improved, and more accurate and reliable after-sales services can be provided to vehicle users in a timely manner, thereby improving the user experience and the efficiency of fault diagnosis and maintenance.

[0029] Furthermore, the server verifies the validity of the vehicle's reported data, and after the verification is passed, determines whether the vehicle may have a fault based on the indicator light, thereby further avoiding misdiagnosis and unnecessary diagnosis.

[0030] Furthermore, when at least one indicator light of a preset type is continuously lit for a certain period of time, it is determined that the vehicle may have a fault, and a specific fault diagnosis is performed, thereby further avoiding misdiagnosis and unnecessary diagnosis.

[0031] Furthermore, by searching for the fault code corresponding to the lit indicator light in the pre-generated mapping relationship table between the indicator light and the fault code, the range of the fault code to be screened can be determined quickly and accurately, thereby improving the speed of fault diagnosis.

[0032] Furthermore, the lit indicator lights are grouped, and the fault codes corresponding to each group of indicator lights are determined in the mapping relationship table. In this way, a mapping relationship table can be established and searched for multiple related indicator lights in the form of groups, further improving the efficiency and accuracy of determining the fault codes.

[0033] Furthermore, when determining the fault type based on the screened fault codes, deduplication processing is performed on the screened fault types, which can improve the effectiveness of generating fault type information, reduce data redundancy, avoid user confusion, and improve user experience.

[0034] Furthermore, the server sends the vehicle's fault type information to the vehicle to notify the vehicle's user, so that the user can promptly learn the fault type and perform further processing in a timely manner. For example, for more serious faults, the user can wait for rescue or drive to the nearest maintenance outlet, and for simple faults, the user can self-repair, etc., thereby ensuring the safety of the vehicle and the user and improving the user experience.

[0035] Furthermore, the server generates rescue information for the vehicle based on the fault type information and the location information of the vehicle. In this way, rescue can be carried out as quickly as possible for more serious faults, ensuring the safety of the vehicle and the user and improving the user experience.

[0036] With reference to the following description and drawings, the embodiments of the present disclosure are disclosed in detail. It should be understood that the embodiments of the present disclosure are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present disclosure include many changes, modifications and equivalents.

[0037] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0038] It should be emphasized that the terms “include / comprises / has” when used herein refer to the existence of a feature, an integer, or a component, but do not exclude the existence or addition of one or more other features, integers, or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The above and other objects, features and advantages of the embodiments of the present disclosure will become more apparent from the following detailed description in conjunction with the accompanying drawings, in which:

[0040] Figure 1 It is a schematic diagram of the steps of a remote diagnosis method of a vehicle fault according to an embodiment of the present disclosure;

[0041] Figure 2 is a structural schematic diagram of a remote diagnosis system for vehicle faults according to an embodiment of the present disclosure;

[0042] Figure 3 is a flow chart of a remote diagnosis method for vehicle faults according to an embodiment of the present disclosure;

[0043] Figure 4 It is a schematic diagram of the composition structure of a remote diagnosis device for vehicle faults according to an embodiment of the present disclosure;

[0044] Figure 5 It is a schematic diagram of the composition of a server according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0045] With reference to the accompanying drawings, the above and other features of the present disclosure will become apparent through the following description. In the description and the accompanying drawings, specific embodiments of the present disclosure are specifically disclosed, which show some embodiments in which the principles of the present disclosure can be adopted, and it should be understood that the present disclosure is not limited to the described embodiments, but includes all modifications and equivalents falling within the scope of the attached claims.

[0046] The remote diagnosis method for vehicle faults according to an embodiment of the present disclosure is described below with reference to the accompanying drawings.

[0047] Example 1

[0048] The embodiment of the present disclosure provides a remote diagnosis method for vehicle faults.

[0049] Figure 1 The present invention is a schematic diagram of the steps of a remote diagnosis method for vehicle faults according to an embodiment of the present invention.

[0050] like Figure 1 As shown, the method includes:

[0051] Step 101: The server obtains the current indicator light information of the vehicle from the vehicle, and determines whether the vehicle has a possibility of failure according to the indicator light information;

[0052] Step 102: When it is determined that the vehicle has a possibility of failure, the server determines, according to a preset rule, first fault code information corresponding to the indicator light that is lit in the indicator light information;

[0053] Step 103: The server obtains the current candidate fault code information of the vehicle from the vehicle and uses it as the second fault code information;

[0054] Step 104: The server compares the first fault code information with the second fault code information, and when the second fault code information contains the fault code included in the first fault information, determines that the vehicle has a fault, and determines the fault type information of the vehicle according to the fault code.

[0055] In this embodiment, the indicator light information has a corresponding relationship with the first fault code information, and different indicator light combinations can correspond to different fault code sets. The second fault code information is the candidate fault code information that the vehicle terminal will send to the server in real time, usually intercepting the candidate fault code within a certain time period. Then, the first fault code information is compared with the second fault code information, and according to the intersection of the two fault code information, the fault code that accurately represents the vehicle fault type can be screened out.

[0056] In some embodiments, the method can be applied to remote fault diagnosis of various vehicles.

[0057] The vehicle may be various types of vehicles, for example, a car, an electric car, or a hybrid car; for example, a private car, a public bus, a bus, a van, a truck, a motorcycle, a tour bus, etc.; for example, an unmanned car or an automatic driving car, etc.

[0058] In some embodiments, the method can be used for remote diagnosis of various faults of the vehicle.

[0059] In some embodiments, the vehicle to which the remote diagnosis method for vehicle faults according to the embodiments of the present invention is applied is also referred to as a target vehicle.

[0060] In some embodiments, the method can be applied to a remote diagnosis system for vehicle faults. The remote diagnosis method for vehicle faults in an embodiment of the present invention is specifically described below in conjunction with a remote diagnosis system for vehicle faults. Figure 2 FIG. 1 is a schematic diagram of the structure of a remote diagnosis system for vehicle faults according to an embodiment of the present invention. Figure 2 As shown, the remote diagnosis system 10 for vehicle failure includes:

[0061] At least one vehicle 11, namely, a target vehicle, reports data to a server 12, wherein the reported data at least includes indicator light information and candidate fault code information;

[0062] The server 12 determines whether the vehicle 11 has a possibility of failure according to the indicator light information; when it is determined that the vehicle 11 has a possibility of failure, determines the fault code information corresponding to the indicator light that is lit in the indicator light information according to a preset rule;

[0063] The server 12 compares the candidate fault code information in the reported data with the first fault code information corresponding to the lit indicator light. When the first fault code information corresponding to the lit indicator light contains a fault code included in the candidate fault code information in the reported data, it is determined that there is a fault in the vehicle 11, and the fault type information of the vehicle 11 is determined based on the fault code.

[0064] In addition, if Figure 2 As shown, the system 10 also includes at least one maintenance outlet 13, which is used to provide after-sales services such as repair, rescue, and maintenance for the vehicle.

[0065] For example, the server 12 is a cloud server, that is, a server in the cloud. The server 12 exchanges data with the vehicle 11 and the maintenance outlet 13 through one or more networks such as the Internet of Vehicles, the Internet of Things, and the Internet.

[0066] For example, the maintenance outlet 13 may be various organizations that provide after-sales services including repair, rescue, maintenance, etc. for vehicles, such as a vehicle 4S store, a vehicle repair shop, or other types of vehicle maintenance organizations.

[0067] In this way, the remote server further screens the fault code corresponding to the currently lit indicator light of the vehicle from the current fault code information reported by the vehicle, and determines the fault type information of the vehicle based on the screened fault code. Thus, based on the dual judgment mechanism of indicator light and fault code information, the fault interference factors are filtered, the accuracy of the determined fault type information is improved, the reliability and accuracy of remote fault diagnosis are improved, and more accurate and reliable after-sales services are provided to vehicle users in a timely manner, which improves the user experience and the efficiency of fault diagnosis and maintenance.

[0068] In some embodiments, the vehicle reports data to the server in real time or periodically, and the reported data may include, for example, one or more of the vehicle's power status, charging status, driving status and speed, indicator light information currently displayed on the instrument, candidate fault code information, and vehicle location information.

[0069] In some embodiments, before performing fault diagnosis, the server performs a validity check on the vehicle's reported data. When the validity check passes, it determines whether the vehicle may have a fault based on the indicator light information.

[0070] For example, the validity check includes the integrity of necessary vehicle information, field validity, etc.

[0071] Table 1 shows an example of verification rules for verifying the validity of reported data.

[0072] Table 1

[0073]

[0074] As shown in Table 1, the verification items include, for example, verification of indicator light signals and information reporting time. For indicator light signals, the verification rule is that if the valid value of the data field is within [0, 255], the data is valid, otherwise the data is invalid; for information reporting time, the verification rule is that if the data reporting time is within 5 minutes before and after the current time, the data is valid, otherwise the data is invalid.

[0075] In this way, the server verifies the validity of the vehicle's reported data, and after the verification is passed, it determines whether the vehicle may have a fault based on the indicator light, thereby further avoiding misdiagnosis and unnecessary diagnosis.

[0076] In step 101, the server obtains the current indicator light information of the vehicle from the vehicle, for example, obtains the current indicator light information of the vehicle from the reported data of the vehicle.

[0077] The indicator light information is information about the indicator light currently displayed or lit, and the indicator light may be various indicator lights related to faults or abnormalities that can be displayed or lit inside the vehicle (eg, a dashboard).

[0078] In step 101, the server also determines whether there is a possibility of failure of the vehicle based on the indicator light information.

[0079] For example, the server determines the status of a preset type of indicator light based on the indicator light information; when at least one indicator light of the preset type continues to light up within a preset time period, it is determined that the vehicle may have a fault.

[0080] For example, the preset types of indicator lights may include but are not limited to the following indicator lights: vehicle system fault indicator light; vehicle system fault stop indicator light; vehicle system fault power limiting indicator light; braking system fault indicator light; 12V charging system abnormality indicator light; AC charging system fault indicator light; DC charging system fault indicator light; AC discharge system fault indicator light; DC discharge system fault indicator light; SBW fault indicator light; EBS fault indicator light.

[0081] When one or more indicator lights of a preset category are continuously lit for a preset time (e.g., 1 minute), it is determined that the vehicle may have a fault, that is, there is a possibility of a fault. In this way, when at least one indicator light belonging to a preset category is continuously lit for a certain time, it can be determined that the vehicle may have a fault, and a specific fault diagnosis can be performed, thereby further avoiding misdiagnosis and unnecessary diagnosis.

[0082] In some practical application examples, the preset types of indicator lights may also include functional indicator lights such as "request parking indicator light" and "vehicle ready indicator light". Although these functional indicator lights will also be lit when the vehicle is in normal use. However, if these functional indicator lights and at least one fault indicator light are continuously lit for a certain period of time, it can be considered that the vehicle may have a fault.

[0083] In step 102, when it is determined that the vehicle has a possibility of failure, the server determines the first fault code information corresponding to the lit indicator light in the indicator light information according to a preset rule, that is, the first fault code information represents a set or range of fault codes corresponding to the lit indicator light.

[0084] Specifically, by using the preset rules, the matching relationship between "one or more indicator lights that are lit" and "one or more first fault codes" can be accurately and efficiently determined. In actual application scenarios, the preset rules may vary according to different vehicle manufacturers or vehicle models, thereby ensuring the reliability and accuracy of the preset rules.

[0085] In an actual application example, the preset rules may include: determining the set or range of fault codes corresponding to the lit indicator lights by looking up a table. For example, a mapping table between indicator lights and fault codes is pre-established to find the fault codes corresponding to the lit indicator lights. In this way, the range of fault codes for screening can be determined quickly and accurately, thereby improving the speed of fault diagnosis.

[0086] In some embodiments, the lit indicator lights may be grouped, and the fault codes corresponding to the respective groups of indicator lights may be determined in a mapping relationship table.

[0087] Table 2 shows an example of a mapping relationship table between indicator lights and fault codes.

[0088] Table 2

[0089]

[0090]

[0091] For example, as shown in Table 2, when a group of indicator lights including "vehicle system fault indicator light", "vehicle system fault stop indicator light", "vehicle system fault power limit indicator light" and "brake system fault indicator light" are lit for a certain period of time at the same time, the cloud server believes that the vehicle may be in a fault state and filters out the range of fault codes that need further verification: "P0E6D", "P0E70", "P0562", and "P0AA8".

[0092] For another example, as shown in Table 2, when a group of indicator lights including "vehicle system fault indicator light", "12V charging system abnormality indicator light", "brake system fault indicator light", "AC charging system fault indicator light" and "DC charging system fault indicator light" are lit up for a certain period of time at the same time, the cloud server believes that the vehicle may be in a fault state and selects the range of fault codes that need further verification: "P0C44", "P0C45", "P0CD7", "P0CD8", "P0DAC", "P1D64", and "P3155".

[0093] In this way, a mapping relationship table can be established and searched for multiple related indicator lights in the form of a group, further improving the efficiency and accuracy of determining the fault code.

[0094] For example, in step 102, the fault code corresponding to the indicator light that is lit in the indicator light information is searched in the pre-generated mapping relationship table between the indicator light and the fault code, and the first fault code information is generated according to the set of all corresponding fault codes. For example, as described above, the range of fault codes that need to be further verified is screened out: "P0E6D", "P0E70", "P0562", "P0AA8", then the first fault code information is information containing the fault codes "P0E6D", "P0E70", "P0562", "P0AA8".

[0095] In step 103, the server obtains the current candidate fault code information of the vehicle from the vehicle and uses it as the second fault code information, that is, the second fault code information represents the current candidate fault code information reported by the vehicle. For example, the current candidate fault code information is included in the reported data of the vehicle.

[0096] The current candidate fault code information obtained from the vehicle and the current indicator light information obtained in step 101 are information reported by the vehicle at substantially the same time or within a certain time range before and after. For example, the current candidate fault code information obtained from the vehicle is the aforementioned indicator light information reported by the vehicle at the same time, or both are information reported within a certain time range before and after (for example, 1-5 minutes). Thus, the correlation between the two is ensured.

[0097] In step 104, the server compares the first fault code information with the second fault code information, that is, compares the fault code information corresponding to the indicator light information reported by the vehicle with the candidate fault code information reported by the vehicle, filters and selects the fault type, and eliminates interference factors.

[0098] When the second fault code information contains the fault code included in the first fault information, it is determined that the vehicle has a fault, that is, when the fault code reported by the vehicle contains the fault code corresponding to the indicator light information reported by the vehicle at the same time (or substantially the same time), it is determined that the vehicle has a fault. In this way, after multiple screenings, the reliability and accuracy of the determined fault code are high.

[0099] For example, as described above, based on the indicator light information currently reported by the vehicle, the range of fault codes that need further verification can be screened out: "P0E6D", "P0E70", "P0562", "P0AA8", then the first fault code information is information containing the fault codes "P0E6D", "P0E70", "P0562", "P0AA8". The current candidate fault code information reported by the vehicle, that is, the second fault code information, is information containing at least the fault codes "P0562" and "P0AA8".

[0100] Then, the server compares the first fault code information and the second fault code information, and can determine the fault codes that exist in both the first fault code information and the second fault code information, i.e., "P0562" and "P0AA8", and then determines that the vehicle has a fault. In other words, the server screens the fault codes that appear in both the first fault code information and the second fault code information.

[0101] In step 104, the fault type information of the vehicle is determined according to the screened fault codes.

[0102] For example, the vehicle's fault types may include various possible fault types, such as including but not limited to the following faults or abnormalities: vehicle charging system failure; high-voltage battery system failure; vehicle system communication abnormality; drive motor system failure; vehicle cooling system failure; low-voltage power supply system failure; vehicle controller abnormality; vehicle ECU failure; charging pile failure.

[0103] In addition, the vehicle's fault type may also be referred to as the vehicle's fault cause or fault location, etc.

[0104] For example, the fault type corresponding to the screened fault code can be determined through a pre-generated mapping relationship table between fault codes and fault types, so that the corresponding fault type can be quickly obtained.

[0105] Table 3 shows an example of a mapping relationship table between fault codes and fault types.

[0106] Table 3

[0107]

[0108] For example, as shown in Table 3, as mentioned above, the fault codes screened out are "P0562" and "P0AA8", and the corresponding fault types are "drive click system fault" and "vehicle cooling system fault".

[0109] The above Tables 2 and 3 only provide some indicator lights, fault codes and fault types (fault causes) for example, and are not intended to limit the embodiments of the present invention. In addition, the embodiments of the present invention may also include indicator lights, fault codes and fault types (fault causes) not recorded in Tables 2 and 3.

[0110] In addition, Table 2 and Table 3, ie, the mapping relationship table between indicator lights and fault codes and the mapping relationship table between fault codes and fault types, may be two independent tables or may be integrated into one table.

[0111] It should be noted that the indicator lights and fault codes are not in a one-to-one correspondence. Usually, different indicator light combinations will appear when a vehicle fails. Different indicator light combinations can correspond to different fault code combinations. The same fault light will not necessarily have the same fault code when it is lit at different times. Each fault code will uniquely correspond to a fault type (see Table 3).

[0112] In some embodiments, the fault type corresponding to each of the screened fault codes is determined respectively; the fault type is deduplicated; and fault type information is generated according to the deduplicated fault type.

[0113] In this way, the effectiveness of generating fault type information can be improved, data redundancy can be reduced, user troubles can be avoided, and user experience can be improved.

[0114] In some embodiments, the method further includes: the server sending the fault type information of the vehicle to the vehicle to notify the user of the vehicle. In addition, the server can also send the maintenance network information near the vehicle to the vehicle at the same time.

[0115] In this way, users can learn about the fault type in a timely manner and take further action in a timely manner. For example, for more serious faults, users can wait for rescue or drive to the nearest maintenance outlet. For simple faults, users can self-repair, etc., ensuring the safety of vehicles and users and improving user experience.

[0116] In some embodiments, the method further includes: the server generates rescue information for the vehicle according to the fault type information of the vehicle and the location information of the vehicle. In addition, the rescue information of the vehicle can also be sent to the maintenance outlet closest to the vehicle. In this way, for more serious faults, rescue can be carried out at the fastest speed, ensuring the safety of the vehicle and the user and improving the user experience.

[0117] For example, the server determines the severity of the fault based on the fault type information of the vehicle. If the fault is a serious fault, the rescue information of the vehicle is sent to the nearest maintenance outlet. The maintenance outlet generates rescue dispatch information based on the location information and rescue information of the vehicle and rescues the vehicle in time. If the fault is not a serious fault, the server can send the fault type information of the vehicle to the vehicle, and display and / or broadcast it through the vehicle system. In addition, if the fault is a minor fault that the user can solve by himself, the troubleshooting / repair method can also be sent to the vehicle for the user's reference.

[0118] In this way, the server can make timely and reasonable responses based on fault information of different severity to ensure user safety and experience.

[0119] Figure 3It is a flow chart of a remote diagnosis method for vehicle faults according to an embodiment of the present invention.

[0120] like Figure 3 As shown, the method includes:

[0121] Step 301: The server obtains reporting data from the vehicle, where the reporting data at least includes current indicator light information and candidate fault code information, and the reporting data is reported in real time or periodically;

[0122] Step 302: The server performs validity verification on the reported data;

[0123] Step 303: Determine whether the validity check is passed. If the result is "yes", go to step 304. If the result is "no", return.

[0124] Step 304: The server determines the state of the indicator light according to the current indicator light information in the reported data;

[0125] Step 305: Determine whether one or more indicator lights are continuously on. If the determination result is "yes", proceed to step 306. If the determination result is "no", return.

[0126] Step 306: searching the indicator light information for the fault code corresponding to the indicator light in the indicator light information in the indicator light and fault code mapping relationship table;

[0127] Step 307: Generate first fault code information according to the set of fault codes corresponding to all indicator lights;

[0128] Step 308: The server compares the first fault code information with the candidate fault code information (second fault code information) in the reported data;

[0129] Step 309: Determine whether the second fault code information contains the fault code included in the first fault code information. If the determination result is "yes", proceed to step 310. If the determination result is "no", return.

[0130] Step 310: respectively determining the fault type corresponding to each of the screened fault codes, performing deduplication processing on the determined fault types, and generating fault type information according to the deduplication-processed fault types;

[0131] Step 311: The server sends the fault type information of the vehicle to the vehicle to notify the user of the vehicle.

[0132] The following is a specific description using an application example.

[0133] For example, the cloud server receives the reported data of the vehicle and verifies its validity. After the validity verification is passed, it is found that the vehicle's "vehicle system fault indicator light", "vehicle system fault parking indicator light", "vehicle system fault power limit indicator light", and "brake system fault indicator light" continue to light up simultaneously for a certain period of time. The cloud server believes that the vehicle may be in a faulty state, and through table lookup, it screens out the fault code range that needs further verification: "P0E6D", "P0E70", "P0562", and "P0AA8". In addition, the candidate fault code currently reported by the vehicle is "P0E6D". Since the fault code "P0E6D" is within the fault code range determined in the previous step, it is determined that the vehicle currently has a fault; and, according to the fault code determination rules, for example, through table lookup, it is determined that the vehicle fault corresponding to "P0E6D" is "high-voltage battery system fault".

[0134] For another example, the cloud server receives the reported data from the vehicle, and after the validity verification is passed, it is found that the vehicle's "vehicle system fault indicator light", "12V charging system abnormality indicator light", and "brake system fault indicator light" continue to light up simultaneously for a certain period of time. The cloud server believes that the vehicle may be in a faulty state, and through a table lookup, it screens out the fault code range that needs further verification: "P0C45", "P0CD7", "P0CD8", and "P0C44". In addition, the candidate fault codes currently reported by the vehicle are "P0CD7" and "U1011". Since the fault code "P0CD7" is within the fault code range determined in the previous step, it is determined that the vehicle currently has a fault; and, according to the fault code determination rules, for example, through a table lookup, it is determined that the vehicle fault corresponding to "P0CD7" is "vehicle system communication abnormality".

[0135] It can be seen from the above embodiments that the remote server further screens the fault code corresponding to the indicator light currently lit in the current fault code information reported by the vehicle, and determines the fault type information of the vehicle based on the screened fault code. Thus, based on the dual judgment mechanism of the indicator light and the fault code information, the fault interference factors are filtered, the accuracy of the determined fault type information can be improved, the reliability and accuracy of remote fault diagnosis can be improved, and more accurate and reliable after-sales services can be provided to vehicle users in a timely manner, which improves the user experience and the efficiency of fault diagnosis and maintenance.

[0136] Furthermore, the server verifies the validity of the vehicle's reported data, and after the verification is passed, determines whether the vehicle may have a fault based on the indicator light, thereby further avoiding misdiagnosis and unnecessary diagnosis.

[0137] Furthermore, when at least one indicator light of a preset type is continuously lit for a certain period of time, it is determined that the vehicle may have a fault, and a specific fault diagnosis is performed, thereby further avoiding misdiagnosis and unnecessary diagnosis.

[0138] Furthermore, by searching for the fault code corresponding to the lit indicator light in the pre-generated mapping relationship table between the indicator light and the fault code, the range of the fault code to be screened can be determined quickly and accurately, thereby improving the speed of fault diagnosis.

[0139] Furthermore, the lit indicator lights are grouped, and the fault codes corresponding to each group of indicator lights are determined in the mapping relationship table. In this way, a mapping relationship table can be established and searched for multiple related indicator lights in the form of groups, further improving the efficiency and accuracy of determining the fault codes.

[0140] Furthermore, when determining the fault type based on the screened fault codes, deduplication processing is performed on the screened fault types, which can improve the effectiveness of generating fault type information, reduce data redundancy, avoid user confusion, and improve user experience.

[0141] Furthermore, the server sends the vehicle's fault type information to the vehicle to notify the vehicle's user, so that the user can promptly learn the fault type and perform further processing in a timely manner. For example, for more serious faults, the user can wait for rescue or drive to the nearest maintenance outlet, and for simple faults, the user can self-repair, etc., thereby ensuring the safety of the vehicle and the user and improving the user experience.

[0142] Furthermore, the server generates rescue information for the vehicle based on the fault type information and the location information of the vehicle. In this way, rescue can be carried out as quickly as possible for more serious faults, ensuring the safety of the vehicle and the user and improving the user experience.

[0143] Example 2

[0144] Embodiment 2 of the present invention provides a remote diagnosis device for vehicle faults. The system corresponds to the remote diagnosis method for vehicle faults described in Embodiment 1. For specific contents, please refer to the description in Embodiment 1, and repeated contents will not be described in detail.

[0145] Figure 4 FIG. 2 is a schematic diagram of the structure of a remote diagnosis device for vehicle faults according to Embodiment 2 of the present invention. Figure 4 As shown, the remote diagnosis device 400 for vehicle failure includes:

[0146] A first acquisition unit 401, which acquires the current indicator light information of the vehicle from the vehicle;

[0147] A first determination unit 402, which determines whether the vehicle has a possibility of failure according to the indicator light information;

[0148] A second determination unit 403, which, when determining that the vehicle has a possibility of failure, determines first fault code information corresponding to the lighted indicator light in the indicator light information according to a preset rule;

[0149] A second acquisition unit 404, which acquires the current candidate fault code information of the vehicle from the vehicle and uses it as the second fault code information;

[0150] The third determination unit 405 compares the first fault code information with the second fault code information, determines that the vehicle has a fault when the second fault code information contains the fault code included in the first fault information, and determines the fault type information of the vehicle according to the fault code.

[0151] In some embodiments, the apparatus further comprises:

[0152] A verification unit, which performs validity verification on the reported data of the vehicle, wherein the reported data includes the indicator light information and the candidate fault code information;

[0153] When the validity check passes, a determination is made as to whether the vehicle has a possibility of failure based on the indicator light information.

[0154] In some embodiments, the first determination unit determines the state of a preset type of indicator light based on the indicator light information; and when at least one indicator light of the preset type continues to light up for a preset time period, it is determined that there is a possibility of a fault in the vehicle.

[0155] In some embodiments, the second determination unit searches for the fault code corresponding to the lit indicator light in the indicator light information in a pre-generated mapping relationship table between indicator lights and fault codes; and generates the first fault code information based on a set of all corresponding fault codes.

[0156] In some embodiments, the second determination unit groups the lighted indicator lights in the indicator light information, and determines the fault code corresponding to each group of indicator lights in the mapping relationship table.

[0157] In some embodiments, the third determination unit determines the fault type corresponding to each fault code respectively; and performs deduplication processing on the fault type; and generates fault type information according to the deduplication-processed fault type.

[0158] In some embodiments, the apparatus further comprises:

[0159] A sending unit sends the fault type information of the vehicle to the vehicle to inform the user of the vehicle.

[0160] In some embodiments, the apparatus further comprises:

[0161] A generating unit generates rescue information of the vehicle according to the fault type information of the vehicle and the location information of the vehicle.

[0162] It can be seen from the above embodiments that the remote server further screens the fault code corresponding to the indicator light currently lit in the current fault code information reported by the vehicle, and determines the fault type information of the vehicle based on the screened fault code. Thus, based on the dual judgment mechanism of the indicator light and the fault code information, the fault interference factors are filtered, the accuracy of the determined fault type information can be improved, the reliability and accuracy of remote fault diagnosis can be improved, and more accurate and reliable after-sales services can be provided to vehicle users in a timely manner, which improves the user experience and the efficiency of fault diagnosis and maintenance.

[0163] Example 3

[0164] An embodiment of the present application provides a server, which can execute the method applied to the server side in Example 1. In addition, the server may include the device described in Example 2.

[0165] Figure 5 FIG. 1 is a schematic diagram of a server structure in an embodiment of the present application. Figure 5 As shown, the server 500 may include: a processor 510 and a memory 520; the memory 520 is coupled to the processor 510. The memory 520 may store various data; in addition, the memory 520 may store an information processing program 530, and the program 530 is executed under the control of the processor 510 to receive various information sent by vehicles and maintenance outlets, and to send various information to vehicles and maintenance outlets.

[0166] In one embodiment, the processor 510 can be configured as follows: the server obtains the current indicator light information of the vehicle from the vehicle, and determines whether the vehicle has a possibility of a fault based on the indicator light information; when it is determined that the vehicle has a possibility of a fault, the first fault code information corresponding to the indicator light that is lit in the indicator light information is determined according to a preset rule; the server obtains the current candidate fault code information of the vehicle from the vehicle, and uses it as the second fault code information; the server compares the first fault code information with the second fault code information, and when the second fault code information contains the fault code contained in the first fault information, it is determined that the vehicle has a fault, and the fault type information of the vehicle is determined based on the fault code.

[0167] In addition, if Figure 5As shown, the server 500 may also include: a transceiver 540 and an antenna 550, etc.; wherein the functions of the above components are similar to those of the prior art and are not described here. It is worth noting that the server 500 does not necessarily have to include Figure 5 In addition, the server 500 may also include Figure 5 For components not shown, reference may be made to the prior art.

[0168] It can be seen from the above embodiments that the remote server further screens the fault code corresponding to the indicator light currently lit in the current fault code information reported by the vehicle, and determines the fault type information of the vehicle based on the screened fault code. Thus, based on the dual judgment mechanism of the indicator light and the fault code information, the fault interference factors are filtered, the accuracy of the determined fault type information can be improved, the reliability and accuracy of remote fault diagnosis can be improved, and more accurate and reliable after-sales services can be provided to vehicle users in a timely manner, which improves the user experience and the efficiency of fault diagnosis and maintenance.

[0169] The above detailed description of the embodiments of the present invention with reference to the accompanying drawings indicates the manner in which the principles of the present invention can be adopted. However, it should be understood that the implementation of the present invention is not limited to the above embodiments, but also includes all changes, modifications and equivalents that do not depart from the scope of the present invention.

Claims

1. A remote diagnosis method for vehicle failure, characterized in that: The method comprises: The server obtains the current indicator light information of the vehicle from the vehicle, and determines whether the vehicle has a possibility of failure according to the indicator light information; When it is determined that the vehicle has a possibility of failure, the server determines, according to a preset rule, first fault code information corresponding to the indicator light that is lit in the indicator light information; The server obtains the current candidate fault code information of the vehicle from the vehicle and uses the candidate fault code information as the second fault code information; The server compares the first fault code information with the second fault code information, determines that a fault exists in the vehicle when the second fault code information contains the fault code included in the first fault information, and determines the fault type information of the vehicle based on the fault code.

2. The method according to claim 1, characterized in that The method further comprises: The server performs validity verification on the reported data of the vehicle, wherein the reported data includes the indicator light information and the candidate fault code information; When the validity check passes, a determination is then made as to whether there is a possibility of a fault in the vehicle based on the indicator light information.

3. The method according to claim 1 or 2, characterized in that: Determining whether the vehicle has a possibility of failure according to the indicator light information includes: Determine the state of a preset type of indicator light according to the indicator light information; When at least one indicator light of a preset type is continuously lit within a preset time period, it is determined that there is a possibility of a fault in the vehicle.

4. The method according to claim 1, characterized in that: Determining first fault code information corresponding to the indicator light that is lit in the indicator light information according to a preset rule includes: In a pre-generated mapping relationship table between indicator lights and fault codes, searching for a fault code corresponding to the indicator light that is lit in the indicator light information; The first fault code information is generated according to a set of all corresponding fault codes.

5. The method according to claim 4, characterized in that In a pre-generated mapping relationship table between indicator lights and fault codes, searching for a fault code corresponding to the indicator light that is lit in the indicator light information includes: The lighted indicator lights in the indicator light information are grouped, and the fault codes corresponding to the indicator lights of each group are determined in the mapping relationship table.

6. The method according to claim 1, characterized in that Determining the fault type information of the vehicle according to the fault code includes: respectively determining the fault type corresponding to each of the fault codes; Performing deduplication processing on the fault type; Generate fault type information based on the fault type after deduplication processing.

7. The method according to claim 1, characterized in that The method further comprises: The server sends the fault type information of the vehicle to the vehicle to notify the user of the vehicle.

8. The method according to claim 1, characterized in that The method further comprises: The server generates rescue information of the vehicle according to the fault type information of the vehicle and the location information of the vehicle.

9. A remote diagnosis device for vehicle failure, the device being arranged in a server, characterized in that: The device comprises: A first acquisition unit, which acquires current indicator light information of the vehicle from the vehicle; a first determining unit, which determines whether the vehicle has a possibility of failure according to the indicator light information; a second determination unit, which, when determining that the vehicle has a possibility of failure, determines, according to a preset rule, first fault code information corresponding to the indicator light that is lit in the indicator light information; A second acquisition unit, which acquires current candidate fault code information of the vehicle from the vehicle and uses the candidate fault code information as second fault code information; A third determination unit compares the first fault code information with the second fault code information, determines that a fault exists in the vehicle when the second fault code information contains the fault code included in the first fault information, and determines the fault type information of the vehicle according to the fault code.

10. The device according to claim 9, characterized in that The device also includes: A verification unit, which performs validity verification on the reported data of the vehicle, wherein the reported data includes the indicator light information and the candidate fault code information; When the validity check passes, a determination is then made as to whether there is a possibility of a fault in the vehicle based on the indicator light information.

11. The device according to claim 9 or 10, characterized in that The first determination unit determines the state of a preset type of indicator light according to the indicator light information; and when at least one indicator light of the preset type is continuously lit within a preset time period, it is determined that there is a possibility of a fault in the vehicle.

12. The device according to claim 9, characterized in that The second determination unit searches for the fault code corresponding to the lighted indicator light in the indicator light information in a pre-generated mapping relationship table between indicator lights and fault codes; and generates the first fault code information according to a set of all corresponding fault codes.

13. The device according to claim 12, characterized in that The second determining unit groups the lighted indicator lights in the indicator light information, and determines the fault code corresponding to each group of indicator lights in the mapping relationship table.

14. The device according to claim 9, characterized in that The third determination unit determines the fault type corresponding to each of the fault codes respectively; performs deduplication processing on the fault types; and generates fault type information according to the deduplication-processed fault types.

15. The device according to claim 9, characterized in that The device also includes: A sending unit sends the fault type information of the vehicle to the vehicle to inform the user of the vehicle.

16. The device according to claim 9, characterized in that The device also includes: A generating unit generates rescue information of the vehicle according to the fault type information of the vehicle and the position information of the vehicle.

17. A server, characterized in that: The server comprises the device according to any one of claims 9 to 16.

18. A remote diagnosis system for vehicle failure, characterized in that: The system comprises: At least one vehicle reports data to the server, wherein the reported data at least includes indicator light information and candidate fault code information; The server determines whether the vehicle has a possibility of failure according to the indicator light information; when it is determined that the vehicle has a possibility of failure, determines first fault code information corresponding to the indicator light that is lit in the indicator light information according to a preset rule, The server compares the candidate fault code information in the reported data and the first fault code information corresponding to the lit indicator light. When the first fault code information corresponding to the lit indicator light contains a fault code included in the candidate fault code information in the reported data, it is determined that a fault exists in the vehicle, and the fault type information of the vehicle is determined based on the fault code.

19. The system according to claim 18, characterized in that The server also sends the fault type information of the vehicle and the maintenance network information near the vehicle to the vehicle.

20. The system according to claim 18 or 19, characterized in that The server also generates rescue information for the vehicle according to the fault type information of the vehicle and the location information of the vehicle. The system further comprises: A maintenance network point receives the location information and rescue information of the vehicle from the server and generates rescue dispatch information.

Images