Fault reporting method and device, electronic equipment and storage medium

Abstract

The application provides a fault reporting method and device, electronic equipment and storage medium, which are applied to a vehicle and belong to the technical field of computers. The method comprises the following steps: periodically detecting a target component in the vehicle; in the case that it is detected that the target component has a fault, reporting a component fault message to a cloud server, wherein the component fault message indicates that the target component has a fault; in the case that the fault belongs to a target event, reporting event information corresponding to the fault to the cloud server; wherein the event information comprises an event identifier of the target event and a vehicle log in a target time period, and the target time period comprises a time period in a first preset time period before the fault occurs and a time period in a second preset time period after the fault occurs. The application can improve the efficiency and real-time performance of fault reporting.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a fault reporting method and device, electronic equipment and storage medium. BACKGROUND

[0002] In recent years, with the development of science and technology, vehicles have become the main means of transportation in people's daily life. With the rapid development of automobile industry and electronic control technology, the performance of vehicles has been greatly improved, but at the same time, the electronic control system of vehicles has become more and more complex, and the possibility of failure has increased.

[0003] In the related art, after the vehicle fails, the fault is usually reported to the cloud server manually, or the cloud server periodically sends a fault diagnosis request to the vehicle, so the real-time performance of the fault reporting is poor. SUMMARY

[0004] The embodiments of the present application provide a fault reporting method, device, electronic equipment and storage medium, which can improve the convenience of the fault reporting method. The technical solution is as follows:

[0005] In one aspect, a fault reporting method is provided, applied to a vehicle, and the method comprises:

[0006] Periodically detecting a target component in the vehicle, and reporting a component fault message to a cloud server in a case where it is detected that the target component has a fault, the component fault message indicating that the target component has the fault;

[0007] In a case where the fault belongs to a target event, reporting event information corresponding to the fault to the cloud server;

[0008] The event information comprises an event identifier of the target event and a vehicle log in a target time period, and the target time period comprises a time period within a first preset time period before the fault occurs and a time period within a second preset time period after the fault occurs.

[0009] In one possible implementation, the periodically detecting a target component in the vehicle, and reporting a component fault message to a cloud server in a case where it is detected that the target component has a fault, comprises:

[0010] Determining a third preset time period corresponding to the target component;

[0011] Every third preset time period, performing a self-check on the target component by the target component, and reporting a component fault message to a cloud server in a case where it is detected that the target component has a fault.

[0012] In a possible implementation, the self-checking of the target component is performed every third preset time length, and in a case where a fault is detected in the target component, a component fault message is reported to a cloud server, including:

[0013] In a case where the target component belongs to a first component type, the self-checking of the target component is performed every third preset time length, a state message of this self-checking is generated, and the state message is reported to a controller of the vehicle.

[0014] The controller receives the state message, detects the state message, and in a case where the state message indicates that the target component has a fault, reports the component fault message to the cloud server.

[0015] In a possible implementation, the self-checking of the target component is performed every third preset time length, and in a case where a fault is detected in the target component, a component fault message is reported to a cloud server, including:

[0016] In a case where the target component belongs to a second component type, the self-checking of the target component is performed every third preset time length, and in a case where a fault is detected in the target component during this self-checking, a state message of this self-checking is generated, and the state message is reported to a controller of the vehicle, and the state message indicates that the target component has a fault.

[0017] The controller receives the state message and reports the component fault message to the cloud server.

[0018] In a possible implementation, in a case where a fault is detected in the target component, a component fault message is reported to a cloud server, including:

[0019] In a case where a fault is detected in the target component, a component fault message is generated based on a component identifier of the target component and a fault identifier of the fault, the component fault message including the component identifier and the fault identifier.

[0020] The component fault message is reported to the cloud server, and the cloud server is configured to query a fault type matching the component identifier and the fault identifier in a fault list.

[0021] In a possible implementation, the cloud server is further configured to process the event information by using an event analysis model to obtain fault detail information.

[0022] The event analysis model is an artificial intelligence model trained based on sample event information and sample fault detail information, and the fault detail information includes an occurrence cause and a solution of a fault to which the event information belongs.

[0023] In a possible implementation, the cloud server is further configured to send the fault detail information to the vehicle; and the method further includes:

[0024] receiving the fault detail information sent by the cloud server;

[0025] displaying the fault detail information on a display screen of a vehicle machine of the vehicle.

[0026] In a possible implementation, in a case where the fault belongs to a target event, the second reporting module is configured to report event information corresponding to the fault to the cloud server, including:

[0027] In the fault event mapping table, searching for an event identifier mapped with the fault identifier of the fault, the fault event mapping table being configured to store a mapping relationship between any fault identifier and any event identifier, and the mapping relationship indicating that the fault indicated by the fault identifier belongs to the event indicated by the event identifier.

[0028] In a case where the event identifier mapped with the fault identifier of the fault is found, determining that the fault belongs to the target event indicated by the event identifier, and reporting the event information to the cloud server.

[0029] On the other hand, a fault reporting apparatus is provided, applied to a vehicle, and the apparatus includes:

[0030] A first reporting module configured to periodically detect a target component in the vehicle, and in a case where it is detected that the target component has a fault, report a component fault message to a cloud server, the component fault message indicating that the target component has the fault.

[0031] A second reporting module configured to, in a case where the fault belongs to a target event, report event information corresponding to the fault to the cloud server.

[0032] The event information includes an event identifier of the target event and a vehicle log in a target time period, and the target time period includes a time period in a first preset time length before the fault occurs and a time period in a second preset time length after the fault occurs.

[0033] In a possible implementation, the first reporting module is configured to:

[0034] determine a third preset time length corresponding to the target component.

[0035] Every third preset time length, the target component performs a self-check on the target component, and in a case where a fault is detected in the target component, a component fault message is reported to a cloud server.

[0036] In a possible implementation, the first reporting module is configured to:

[0037] In a case where the target component belongs to a first component type, every third preset time length, the target component performs a self-check on the target component, a state message of this self-check is generated, and the state message is reported to a controller of the vehicle;

[0038] The controller receives the state message, detects the state message, and in a case where the state message indicates that the target component has a fault, the component fault message is reported to the cloud server.

[0039] In a possible implementation, the first reporting module is configured to:

[0040] In a case where the target component belongs to a second component type, every third preset time length, the target component performs a self-check on the target component, in a case where a fault is detected in the target component during this self-check, a state message of this self-check is generated, the state message is reported to a controller of the vehicle, and the state message indicates that the target component has a fault;

[0041] The controller receives the state message, and reports the component fault message to the cloud server.

[0042] In a possible implementation, the first reporting module is configured to:

[0043] In a case where the target component has a fault, based on a component identifier of the target component and a fault identifier of the fault, the component fault message is generated, and the component fault message includes the component identifier and the fault identifier;

[0044] The component fault message is reported to the cloud server, and the cloud server is configured to query a fault type that matches the component identifier and the fault identifier in a fault list.

[0045] In a possible implementation, the cloud server is further configured to process the event information by using an event analysis model to obtain fault detail information.

[0046] The event analysis model is an artificial intelligence model trained based on sample event information and sample fault detail information, and the fault detail information includes an occurrence cause and a solution of a fault to which the event information belongs.

[0047] In a possible implementation, the cloud server is further configured to send the fault detail information to the vehicle; and the apparatus further includes:

[0048] a receiving module configured to receive the fault detail information sent by the cloud server;

[0049] a display module configured to display the fault detail information on a display screen of a vehicle machine of the vehicle.

[0050] In a possible implementation, the second reporting module is configured to:

[0051] In the fault event mapping table, find an event identifier mapped with the fault identifier of the fault, and the fault event mapping table is configured to store a mapping relationship between any fault identifier and any event identifier, and the mapping relationship indicates that the fault indicated by the fault identifier belongs to the event indicated by the event identifier.

[0052] In a case where the event identifier mapped with the fault identifier of the fault is found, it is determined that the fault belongs to the target event indicated by the event identifier, and the event information is reported to the cloud server.

[0053] On the other hand, a computer readable storage medium is provided, and at least one piece of program code is stored in the computer readable storage medium. The at least one piece of program code is loaded and executed by a processor to implement the fault reporting method according to any one of the above implementation manners.

[0054] On the other hand, a computer program product is provided, and the computer program product includes at least one piece of program code. The at least one piece of program code is loaded and executed by a processor to implement the fault reporting method according to any one of the above implementation manners.

[0055] The technical scheme provided by the embodiments of the present application has at least the following beneficial effects:

[0056] The embodiment of the present application provides a fault reporting method, whether a component in a vehicle exists a fault is periodically detected, if the fault exists, the component fault message is actively reported to a cloud server, quick reporting can be performed when the fault occurs, and the efficiency and real-time performance of fault reporting are improved. Moreover, if the fault belongs to a target event, the vehicle log when the fault occurs is additionally reported to the cloud server, so that specific faults can be analyzed, important faults can be monitored on one hand, and resource waste caused by reporting the vehicle log corresponding to each fault is avoided on the other hand. BRIEF DESCRIPTION OF DRAWINGS

[0057] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0058] Figure 1 Fig. 1 is a system architecture diagram of a fault reporting method provided by the embodiment of the present application;

[0059] Figure 2 Fig. 2 is a system architecture diagram of another fault reporting method provided by the embodiment of the present application;

[0060] Figure 3 Fig. 3 is a flowchart of a fault reporting method provided by the embodiment of the present application;

[0061] Figure 4 Fig. 4 is a flowchart of another fault reporting method provided by the embodiment of the present application;

[0062] Figure 5 Fig. 5 is a structural schematic diagram of a fault reporting device provided by the embodiment of the present application;

[0063] Figure 6 Fig. 6 is a structural schematic diagram of another fault reporting device provided by the embodiment of the present application;

[0064] Figure 7 Fig. 7 is a structural schematic diagram of an electronic device provided by the embodiment of the present application. DETAILED DESCRIPTION

[0065] In order to make the purpose, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail with reference to the drawings.

[0066] The terms "first," "second," "third," and "fourth," etc., used in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0067] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals (including but not limited to signals transmitted between the user terminal and other devices) involved in this application have been fully authorized by the user or relevant parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the vehicle driving data in this application was obtained with the full authorization of the user.

[0068] Figure 1 This is a system architecture diagram of a fault reporting method provided in an embodiment of this application, such as... Figure 1 As shown, the system architecture of this fault reporting method includes a vehicle 101 and a cloud server 102. The vehicle 101 and the cloud server 102 have a communication connection.

[0069] In this embodiment, vehicle 101 performs real-time monitoring of its components. If a fault is detected in a component, the vehicle reports the corresponding component fault message to cloud server 102. Simultaneously, if the fault is a target event, vehicle 101 also reports the corresponding event information to the cloud server, including vehicle logs for a period of time when the fault occurred. If the fault is not a target event, vehicle 101 does not need to report the corresponding event information to the cloud server.

[0070] Subsequently, the cloud server 102 can analyze the component failure message and the event information to obtain analysis results, which will then be provided to vehicle maintenance personnel or the vehicle driver. Additionally, the analysis results can also be used to evaluate the performance of this type of vehicle.

[0071] In a possible implementation, the cloud server 102 can be a stand-alone physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN (Content Delivery Network), and big data and artificial intelligence platform.

[0072] In a possible implementation, the vehicle 101 includes a CAN (Controller Area Network) component, a CANFD (CAN with Flexible Data-rate) component, an Ethernet component, and a controller, and a system architecture diagram of the fault reporting method is as shown in Figure 2

[0073] The CAN component, the CANFD component, and the Ethernet component in the vehicle 101 are configured to detect faults and report the faults to the controller in the vehicle 101, and the controller can be a VCC (Vehicle Communication Controller).

[0074] The ZCU (Zonal Control Unit), the ICC (Intelligent Cruise Control), the FCM (Forward Collision Mitgation system), and the like domain controller are connected to the CAN component or the CANFD component, the CAN component or the CANFD component sends a status message to the domain controller, and the domain controller reports the status message to the controller through Ethernet. The Ethernet component directly reports the status message to the controller through Ethernet.

[0075] The vehicle 101 is further configured with a TBOX (Telematics-BOX), and the controller forwards the component fault message to the cloud server 102 through the TBOX after generating the component fault message based on the status message.

[0076] Figure 3 is a flowchart of a fault reporting method provided by an embodiment of the present application, and is applied to a vehicle, as shown in Figure 3 The method comprises the following steps.

[0077] ​301, periodically detecting a target component in the vehicle, and in a case where it is detected that the target component has a fault, reporting a component fault message to a cloud server, the component fault message indicating that the target component has a fault.

[0078] 302, in a case where the fault belongs to a target event, reporting event information corresponding to the fault to the cloud server.

[0079] The event information includes an event identifier of the target event and a vehicle log in a target time period, and the target time period includes a time period in a first preset time period before the fault occurs and a time period in a second preset time period after the fault occurs.

[0080] The method provided by the embodiment of the application periodically detects whether a component in the vehicle has a fault, and if there is a fault, actively reports a component fault message to a cloud server, which can quickly report the fault when the fault occurs, and improves the efficiency and real-time performance of fault reporting. Moreover, if the fault belongs to a target event, the vehicle additionally reports a vehicle log when the fault occurs to the cloud server, so as to analyze the specific fault, on the one hand, to monitor the important fault, and on the other hand, to avoid the waste of resources caused by reporting the vehicle log corresponding to each fault.

[0081] Figure 4 is a flowchart of another fault reporting method provided by the embodiment of the application, applied to a vehicle and a cloud server, referring to Figure 4 The method comprises the following steps.

[0082] 401, the vehicle periodically detects a target component in the vehicle, and in a case where it is detected that the target component has a fault, reports a component fault message to a cloud server, the component fault message indicating that the target component has a fault.

[0083] The vehicle includes a plurality of components, and the target component is a component of the plurality of components that is preconfigured to report a fault. The vehicle periodically detects the target component, and if it is detected that the target component has a fault, generates a component fault message corresponding to the target component, and the vehicle reports the component fault message to the cloud server.

[0084] In a possible implementation manner, the plurality of components include a first component type and a second component type, the components of the first component type include CAN components and CANFD components, and the components of the second component type include Ethernet components.

[0085] Optionally, the components belonging to the first component type can refer to the component list shown in Table 1 below, which shows the manner of reporting the status message of the target component. The status message of the target component is obtained by self-checking of the target component, and can reflect the status of the target component. Therefore, whether the target component has a fault can be determined according to whether the status message of the target component has an abnormality.

[0086] Table 1

[0087]

[0088] In the table, the message name refers to the name of the status message of the target component, the message identifier is used to indicate the status message of the target component, and the network segment refers to the CAN BUS network segment used to send the status message of the target component.

[0089] Optionally, the components belonging to the second component type can refer to the component list shown in Table 2 below, which shows the target component that needs to report a fault.

[0090] Table 2

[0091] Service name Service end Client end Third preset time length Component identifier VHM_Alm VCC_MPU ICC Fault detection period is 500ms 0x1000~0x1010 VHM_Alm VCC_MPU ADCC Fault detection period is 500ms 0x1800~0x1810 VHM_Alm VCC_MPU FCM Fault detection period is 500ms 0x4900~0x4910 VHM_Alm VCC_MPU FLM Fault detection period is 500ms 0x4800~0x4810 VHM_Alm VCC_MPU TBOX Fault detection period is 500ms 0x0800~0x0810 VHM_Alm VCC_MPU FLZCU Fault detection period is 500ms 0x2800~0x2810 VHM_Alm VCC_MPU FRZCU Fault detection period is 500ms 0x3000~0x3010 VHM_Alm VCC_MPU RZCU Fault detection period is 500ms 0x3800~0x3810 VHM_Alm VCC_MPU VCC Fault detection period is 500ms 0x2000~0x2010

[0092] In the table, the third preset time length is the interval time length of the periodic detection of the fault of the target component. The client is an Ethernet component that needs to report a fault, and the server is a controller that needs to receive the fault reported by the Ethernet component.

[0093] In a possible implementation, when the vehicle detects that the target component has a fault, the vehicle generates a component fault message based on the component identifier of the target component and the fault identifier of the fault, the component fault message including the component identifier and the fault identifier; and reports the component fault message to the cloud server.

[0094] In the table, the fault identifier can be a fault code or a fault internal number (FaultNum), and the combination of the component identifier and the fault identifier can represent a specific fault.

[0095] In a possible implementation, the vehicle determines a third preset time length corresponding to the target component, and performs a self-check on the target component through the target component every third preset time length. When it is detected that the target component has a fault, the vehicle reports a component fault message to the cloud server.

[0096] In the table, the third preset time length corresponding to different target components can be the same or different. For example, the third preset time length corresponding to the target component can be 500 ms, etc.

[0097] Optionally, the process of reporting the component fault message is different for different types of target components. The detailed process is shown in the following two manners.

[0098] The first mode: in the case that the target component belongs to the first component type, every third preset time length, the target component performs a self-check on the target component, generates a state message of this self-check, and reports the state message to the controller of the vehicle; the controller receives the state message, detects the state message, and in the case that the state message indicates that the target component has a fault, reports a component fault message to the cloud server.

[0099] The target component belonging to the first component type includes a CAN component and a CANFD component. For each target component belonging to the first component type, the target component performs a detection on itself every third preset time length, and generates a state message corresponding to this detection, and reports each generated state message to the controller. The controller determines whether the state message indicates that the target component has a fault from the received multiple state messages. If a certain state message indicates that the target component has a fault, the controller reports a corresponding component fault message to the cloud server.

[0100] Optionally, the state message of the target component of the first component type can refer to Table 3 shown below. One state message includes multiple signals, and each signal corresponds to a signal name, a signal description, an arrangement format, a starting byte, a starting bit, a signal sending type, and a signal length.

[0101] Table 3

[0102]

[0103] The second mode: in the case that the target component belongs to the second component type, every third preset time length, the target component performs a self-check on the target component, and in the case that the target component has a fault in this self-check, generates a state message of this self-check, and reports the state message to the controller of the vehicle, and the state message indicates that the target component has a fault; the controller receives the state message, and reports a component fault message to the cloud server.

[0104] The target component belonging to the second component type includes an Ethernet component. For each target component belonging to the second component type, the target component performs a detection on itself every third preset time length. If it is detected that the target component has a fault, a state message of this self-check is generated, and the state message is reported to the controller. If it is detected that the target component does not have a fault, the state message does not need to be reported to the controller. Therefore, when the controller receives the state message sent by the target component, it indicates that the target component has a fault, and therefore the controller reports a component fault message corresponding to the state message to the cloud server.

[0105] Optionally, the status message of the target component of the second component type can refer to Table 4 shown below. One status message indicates a plurality of fault DTC (Diagnostic Trouble Code) information units. Each fault DTC information unit corresponds to a field name and a length.

[0106] Table 4

[0107]

[0108] In a possible implementation, the controller of the vehicle performs start-stop processing of fault reporting of the target component according to remote configuration information of the cloud server, an alarm function inhibition state of the target component, and a privacy authorization state of the target component. After the controller completes initialization, a ready service notification is sent to the target component. After the target component receives the ready service notification, the target component starts to periodically report a status message of its own fault. After the controller receives the status message reported by each target component, the controller performs reporting detection and message packaging according to the status message to obtain a component fault message, and reports the component fault message to the cloud server.

[0109] 402. The cloud server receives the component fault message.

[0110] After the vehicle reports the component fault message to the cloud server, the cloud server receives the component fault message sent by the vehicle.

[0111] In a possible implementation, the component fault message includes a component identifier and a fault identifier. The cloud server queries a fault type matching the component identifier and the fault identifier in a fault list.

[0112] Optionally, the fault list stores a matching relationship between the component identifier, the fault identifier, and the fault type.

[0113] Optionally, each target component has a respective fault list. The cloud server finds a fault list corresponding to the component identifier in a plurality of fault lists. The fault list includes a matching relationship between the fault identifier and the fault type. Therefore, the cloud server can find the fault type matching the fault identifier in the fault list. Optionally, the fault list can refer to Table 5 shown below.

[0114] Table 5

[0115]

[0116] In a possible implementation, the cloud server records fault states of each target component. After receiving the component fault message, the cloud server updates the fault state of the target component according to the component fault message.

[0117] In a possible implementation, the cloud server sends the component fault message to a terminal, and the terminal displays the component fault message. The terminal can be a terminal operated by a vehicle maintenance personnel.

[0118] 403、In a case where the fault belongs to a target event, the vehicle reports event information corresponding to the fault to the cloud server.

[0119] The event information includes an event identifier of the target event and a vehicle log in a target time period, and the target time period includes a time period in a first preset time length before the fault occurs and a time period in a second preset time length after the fault occurs.

[0120] For example, the first preset time length is 5 seconds, and the second preset time length is 5 seconds. Then, the vehicle generates the event information corresponding to the fault based on the vehicle log in 5 seconds before the fault occurs and the vehicle log in 5 seconds after the fault occurs, and reports the event information to the cloud server.

[0121] In a possible implementation, the vehicle finds, in a fault event mapping table, an event identifier mapped with a fault identifier of the fault. The fault event mapping table is configured to store a mapping relationship between any fault identifier and any event identifier, and the mapping relationship indicates that the fault indicated by the fault identifier belongs to the event indicated by the event identifier. In a case where the event identifier mapped with the fault identifier of the fault is found, the vehicle determines that the fault belongs to a target event indicated by the event identifier, and reports the event information to the cloud server.

[0122] The target event refers to an event in which a major fault occurs, for example, a collision or a thermal runaway. The vehicle is configured with a mapping relationship between a fault identifier and an event identifier. The vehicle finds whether there is an event identifier having a mapping relationship with the fault identifier in the fault event mapping table. If there is an event identifier having a mapping relationship with the fault identifier, it indicates that the fault belongs to the target event, that is, the fault belongs to a major fault, and therefore corresponding event information needs to be generated for reporting. If there is no event identifier having a mapping relationship with the fault identifier, it indicates that the fault does not belong to the target event, that is, the fault does not belong to a major fault, and therefore corresponding event information does not need to be generated for reporting.

[0123] In a possible implementation, each fault identifier corresponds to configuration information, and the configuration information is configured to indicate whether the fault indicated by the fault identifier belongs to a target event. Therefore, the vehicle can determine whether the fault belongs to the target event according to the configuration information. Optionally, the configuration information is further configured to indicate whether to report an event identifier and a vehicle log. If the configuration information indicates to report the event identifier and the vehicle log, the vehicle generates event information including the event identifier and the vehicle log, and reports the event information to the cloud server. Optionally, the configuration information is further configured to configure the first preset time length and the second preset time length.

[0124] Optionally, the configuration information corresponding to the fault identification is shown in Table 6 below.

[0125] Table 6

[0126]

[0127] Wherein, the fault identification is a 0x starting 14-bit string formed by a 16 hexadecimal number, and the size is 6 bytes. The event identification is a 0x starting 14-bit string formed by a 16 hexadecimal number, and the size is 6 bytes. The event identification includes two bytes of AlmUnitId, 1 byte of 0x00 and 3 bytes of DTC code.

[0128] 404, the cloud server receives the event information corresponding to the fault.

[0129] After the vehicle sends the event information corresponding to the fault to the cloud server, the cloud server receives the event information sent by the vehicle, and the event information includes the event identification of the target event and the vehicle log in the target time period.

[0130] In one possible implementation, the cloud server processes the event information through an event analysis model to obtain fault detail information, and the fault detail information includes the occurrence reason and solution of the fault to which the event information belongs. That is, the cloud server inputs the event information into the event analysis model, and the event analysis model analyzes and processes the event information to output the fault detail information.

[0131] Wherein, the event analysis model is an artificial intelligence model trained based on sample event information and sample fault detail information, for example, the event analysis model is a machine learning model or a deep learning model, etc. Optionally, in the training process of the event analysis model, the cloud server inputs the sample event information into the event analysis model, and the event analysis model outputs the predicted fault detail information. The cloud server determines the loss parameter according to the predicted fault detail information and the sample fault detail information, and trains the event analysis model based on the loss parameter, so as to reduce the loss parameter obtained by the trained event analysis model.

[0132] In the embodiment of the application, the cloud server uses an artificial intelligence model to predict the occurrence reason and solution of the fault of the target component, which is beneficial to master the detailed situation of the fault of the target component, so as to formulate countermeasures in combination with the predicted occurrence reason and solution of the fault.

[0133] Optionally, the cloud server also sends the fault detail information to the vehicle. The vehicle receives the fault detail information sent by the cloud server, and displays the fault detail information on the vehicle machine display screen of the vehicle.

[0134] In the embodiments of the present application, after obtaining the fault detail information, the cloud server can also provide the fault detail information to the vehicle, so as to display the fault detail information on the vehicle to the user, so that the user can understand the fault and help the user to cope with the fault.

[0135] In a possible implementation, after obtaining the fault detail information of the fault by processing the event information through the event analysis model, the cloud server further determines a fault level of the fault, the fault level indicating the severity of the fault. In a case where the fault level reaches a preset level, the cloud server sends the fault detail information to the vehicle. In a case where the fault level does not reach the preset level, the cloud server does not need to send the fault detail information to the vehicle.

[0136] Optionally, the fault level can be obtained from the fault list, or the fault level can be predicted through the event analysis model, and the determination manner of the fault level is not limited in the embodiments of the present application.

[0137] The embodiments of the present application provide a fault reporting method, which periodically detects whether a component in a vehicle has a fault, and actively reports a component fault message to a cloud server if there is a fault, so that the fault can be quickly reported when the fault occurs, and the efficiency and real-time performance of fault reporting are improved. Moreover, if the fault belongs to a target event, the vehicle log when the fault occurs is additionally reported to the cloud server, so as to facilitate targeted analysis of a specific fault, on the one hand, important faults can be monitored in a targeted manner, and on the other hand, resource waste caused by reporting of the vehicle log corresponding to each fault is avoided.

[0138] Figure 5 FIG. 1 is a structural schematic diagram of a fault reporting device provided by the embodiments of the present application, which is applied to a vehicle, and FIG. 2 is a structural schematic diagram of the fault reporting device provided by the embodiments of the present application. Figure 5 The device comprises:

[0139] A first reporting module 501 is configured to periodically detect a target component in a vehicle, and report a component fault message to a cloud server if it is detected that the target component has a fault, the component fault message indicating that the target component has a fault.

[0140] A second reporting module 502 is configured to report event information corresponding to the fault to the cloud server if the fault belongs to a target event.

[0141] The event information comprises an event identifier of the target event and a vehicle log in a target time period, and the target time period comprises a time period in a first preset time length before the fault occurs and a time period in a second preset time length after the fault occurs.

[0142] The fault reporting device provided by the embodiment of the application can periodically detect whether a component in a vehicle has a fault, and if the component has a fault, actively report a component fault message to a cloud server, so that the fault can be quickly reported when the fault occurs, and the efficiency and real-time performance of fault reporting are improved. Moreover, if the fault belongs to a target event, the vehicle log when the fault occurs is additionally reported to the cloud server, so that specific faults can be analyzed, on the one hand, important faults can be monitored, and on the other hand, resource waste caused by reporting the vehicle log corresponding to each fault is avoided.

[0143] Optionally, referring to Figure 6 , the first reporting module 501 is configured to:

[0144] determine a third preset time length corresponding to the target component;

[0145] every third preset time length, perform a self-check on the target component through the target component, and report a component fault message to the cloud server if it is detected that the target component has a fault.

[0146] Optionally, referring to Figure 6 , the first reporting module 501 is configured to:

[0147] if the target component belongs to the first component type, every third preset time length, perform a self-check on the target component through the target component, generate a state message of this self-check, and report the state message to a controller of the vehicle;

[0148] receive the state message through the controller, detect the state message, and report a component fault message to the cloud server if it is detected that the state message indicates that the target component has a fault.

[0149] Optionally, referring to Figure 6 , the first reporting module 501 is configured to:

[0150] if the target component belongs to the second component type, every third preset time length, perform a self-check on the target component through the target component, generate a state message of this self-check, and report the state message to a controller of the vehicle, the state message indicating that the target component has a fault;

[0151] receive the state message through the controller, and report a component fault message to the cloud server.

[0152] Optionally, referring to Figure 6 , the first reporting module 501 is configured to:

[0153] In a case where it is detected that the target component has a fault, a component fault message is generated based on a component identifier of the target component and a fault identifier of the fault, the component fault message including the component identifier and the fault identifier;

[0154] The component fault message is reported to a cloud server, and the cloud server is configured to query a fault type matching the component identifier and the fault identifier in a fault list.

[0155] Optionally, referring to Figure 6 The cloud server is further configured to process the event information by using an event analysis model to obtain fault detail information.

[0156] The event analysis model is an artificial intelligence model trained based on sample event information and sample fault detail information, and the fault detail information includes an occurrence cause and a solution of a fault to which the event information belongs.

[0157] Optionally, referring to Figure 6 The cloud server is further configured to send the fault detail information to the vehicle.

[0158] The receiving module 503 is configured to receive the fault detail information sent by the cloud server.

[0159] The display module 504 is configured to display the fault detail information on a vehicle machine display screen of the vehicle.

[0160] Optionally, referring to Figure 6 The second reporting module 502 is configured to:

[0161] In the fault event mapping table, an event identifier mapped with the fault identifier of the fault is searched, and the fault event mapping table is configured to store a mapping relationship between any fault identifier and any event identifier, and the mapping relationship indicates that the fault indicated by the fault identifier belongs to the event indicated by the event identifier.

[0162] In a case where the event identifier mapped with the fault identifier of the fault is searched, it is determined that the fault belongs to a target event indicated by the event identifier, and the event information is reported to the cloud server.

[0163] It should be noted that: the fault reporting device provided in the above embodiments is only exemplified by the division of the above functional modules, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the electronic device is divided into different functional modules to complete all or part of the functions described above. In addition, the fault reporting device and the fault reporting method provided in the above embodiments belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.

[0164] The embodiment of the present application further provides an electronic device, which comprises a processor and a memory, and the memory stores at least one computer program, which is loaded and executed by the processor to implement the operations performed in the fault reporting method of the above-mentioned embodiment.

[0165] Figure 7 A structural schematic diagram of an electronic device provided by an example embodiment of the present application is shown. The electronic device comprises a processor 701 and a memory 702.

[0166] The processor 701 can comprise one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 701 can be implemented in the form of at least one of a DSP (Digital Signal Processing), an FPGA (Field Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 701 can also comprise a main processor and a coprocessor. The main processor is a processor for processing data in a wake-up state, also referred to as a CPU (Central Processing Unit). The coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 701 can be integrated with a GPU (Graphics Processing Unit) for rendering and drawing the content to be displayed by the display screen. In some embodiments, the processor 701 can further comprise an AI (Artificial Intelligence) processor for processing machine learning-related computing operations.

[0167] The memory 702 can comprise one or more computer-readable storage media, which can be non-transitory. The memory 702 can further comprise a high-speed random access memory and a non-volatile memory such as one or more disk storage devices, flash storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 702 is configured to store at least one computer program for being executed by the processor 701 to implement the fault reporting method provided by the method embodiment of the present application.

[0168] Those skilled in the art can understand that, Figure 7 The structure shown in the above-mentioned figures does not constitute a limitation on the electronic device, and can comprise more or fewer components than those shown, or combine certain components, or adopt a different arrangement of components.

[0169] The embodiment of the present application further provides a computer readable storage medium, at least one program code is stored in the computer readable storage medium, and the at least one program code is loaded and executed by a processor to realize the fault reporting method as described in any of the above implementation manners.

[0170] The embodiment of the present application further provides a computer program product, and the computer program product comprises at least one program code, the at least one program code is loaded and executed by a processor to realize the fault reporting method as described in any of the above implementation manners.

[0171] The above is only optional embodiment of the present application, and does not limit the present application, and any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A fault reporting method, characterized in that, Applied to vehicles, the method includes: Determine the third preset duration corresponding to the target component in the vehicle; Every third preset time interval, the target component performs a self-test. If a fault is detected in the target component, a component fault message is generated based on the component identifier of the target component and the fault identifier of the fault. The component fault message is reported to the cloud server. The component fault message indicates that the target component has experienced the fault. The component fault message includes the component identifier and the fault identifier. The cloud server is used to query the fault list for fault types that match the component identifier and the fault identifier. In the fault event mapping table, find the event identifier that is mapped to the fault identifier of the fault. The fault event mapping table is used to store the mapping relationship between any fault identifier and any event identifier. The mapping relationship indicates that the fault indicated by the fault identifier belongs to the event indicated by the event identifier. If the event identifier mapped to the fault identifier is found, it is determined that the fault belongs to the target event indicated by the event identifier, and the event information corresponding to the fault is reported to the cloud server. The cloud server is also used to process the event information through an event analysis model to obtain fault details information. The event analysis model is an artificial intelligence model trained based on sample event information and sample fault details information. The fault details information includes the cause of the fault to which the event information belongs and the solution. The event information includes the event identifier of the target event and the vehicle log within the target time period. The target time period includes a time period within a first preset duration before the fault occurs and a time period within a second preset duration after the fault occurs.

2. The method according to claim 1, characterized in that, Every third preset time interval, the target component performs a self-test. If a fault is detected in the target component, a component fault message is generated based on the component identifier of the target component and the fault identifier, and the component fault message is reported to the cloud server, including: If the target component belongs to the first component type, every third preset time interval, the target component performs a self-test, generates a status message for this self-test, and reports the status message to the vehicle controller. The controller receives the status message, detects the status message, and if the status message indicates that the target component is faulty, it generates the component fault message based on the component identifier of the target component and the fault identifier of the fault, and reports the component fault message to the cloud server.

3. The method according to claim 1, characterized in that, Every third preset time interval, the target component performs a self-test. If a fault is detected in the target component, a component fault message is generated based on the component identifier of the target component and the fault identifier, and the component fault message is reported to the cloud server, including: If the target component belongs to the second component type, a self-test is performed on the target component every third preset time interval. If a fault is detected in the target component during this self-test, a status message for this self-test is generated and reported to the vehicle controller. The status message indicates that the target component is faulty. The controller receives the status message, generates the component fault message based on the component identifier of the target component and the fault identifier of the fault, and reports the component fault message to the cloud server.

4. The method according to claim 1, characterized in that, The cloud server is also used to send the fault details information to the vehicle; the method further includes: Receive the fault details information sent by the cloud server; The fault details are displayed on the vehicle's infotainment screen.

5. A fault reporting device, characterized in that, Applied to vehicles, the device includes: The first reporting module is used to determine the third preset duration corresponding to the target component in the vehicle; The first reporting module is further configured to perform a self-test on the target component every third preset time interval, and if a fault is detected in the target component, generate a component fault message based on the component identifier of the target component and the fault identifier of the fault, and report the component fault message to the cloud server. The component fault message indicates that the target component has experienced the fault, and the component fault message includes the component identifier and the fault identifier. The cloud server is configured to query the fault list for a fault type that matches the component identifier and the fault identifier. The second reporting module is used to look up an event identifier that is mapped to the fault identifier of the fault in the fault event mapping table. The fault event mapping table is used to store the mapping relationship between any fault identifier and any event identifier. The mapping relationship indicates that the fault indicated by the fault identifier belongs to the event indicated by the event identifier. The second reporting module is further configured to, upon finding the event identifier mapped to the fault identifier of the fault, determine that the fault belongs to the target event indicated by the event identifier, and report the event information corresponding to the fault to the cloud server. The cloud server is further configured to process the event information through an event analysis model to obtain fault details information. The event analysis model is an artificial intelligence model trained based on sample event information and sample fault details information. The fault details information includes the cause and solution of the fault to which the event information belongs. The event information includes the event identifier of the target event and the vehicle log within the target time period. The target time period includes a time period within a first preset duration before the fault occurs and a time period within a second preset duration after the fault occurs.

6. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing at least one computer program, which is loaded and executed by the processor to enable the electronic device to implement the fault reporting method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to implement the fault reporting method as described in any one of claims 1 to 4.

8. A computer program product, characterized in that, The computer program product includes at least one piece of program code, which is loaded and executed by a processor to implement the fault reporting method as described in any one of claims 1 to 4.

Images