Detection method and device and vehicle

Abstract

The invention provides a detection method and device and a vehicle, which are used for improving the fault analysis efficiency of a vehicle-mounted component and reducing the operation and maintenance cost of the vehicle-mounted component. The method comprises the following steps: determining a target alarm path of a first alarm event according to an alarm path diagram of a vehicle; wherein each alarm path in the alarm path diagram is used for describing a triggering relationship between at least two alarm events of the vehicle; and performing fault detection on target components associated with the target alarm path, and determining a first component with a fault in the target components.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of vehicle networking technology, and in particular to a detection method, device and vehicle. Background Art

[0002] With the development of Internet of Vehicles technology, various types of vehicle-mounted components have also been connected to the Internet. Therefore, vehicle-mounted components can report their relevant status information to the cloud server, which can perform fault analysis on the status information of various types of vehicle-mounted components and generate corresponding alarm events. In addition, the cloud server will also report the alarm event to the technical operation and maintenance personnel of the automobile company.

[0003] However, there are tens of thousands of vehicle-mounted components, and cloud servers will report a large number of alarm events, some of which may contain erroneous alarm information. Therefore, the technical operation and maintenance personnel of the car company need to perform fault analysis on a large number of alarm events to locate the vehicle-mounted components that actually failed. It can be seen that the current labor cost of fault analysis of vehicle-mounted components is high, which will lead to high operation and maintenance costs for car companies; and the current fault analysis efficiency of vehicle-mounted components is low, which may cause the operation and maintenance personnel to be unable to maintain the faulty components in time.

[0004] Therefore, how to improve the fault analysis efficiency of vehicle-mounted components and reduce the operation and maintenance costs of vehicle-mounted components is an important issue that the industry urgently needs to solve. Summary of the invention

[0005] The present application provides a detection method, device and system for improving the fault analysis efficiency of vehicle-mounted components and reducing the operation and maintenance costs of vehicle-mounted components.

[0006] In the first aspect, the embodiment of the present application provides a detection method, which can be implemented by a detection device, which can be an independent device, a chip or component in a device, or software. The vehicle detection device can be deployed in any of the cloud, the vehicle side, or a third-party device. Correspondingly, the vehicle detection device can be, for example, a server, a controller in a vehicle (such as a domain controller), or an electronic control unit (ECU) in a vehicle. Alternatively, the vehicle detection device can be a newly added hardware module in the vehicle, which can be configured with relevant judgment logic or algorithms, and can be used as an ECU in the vehicle, and transmit information with other ECUs through an internal communication network to implement the detection method of the embodiment of the present application. The embodiment of the present application does not limit the product form or deployment method of the detection device.

[0007] The detection method includes: determining a target alarm path for a first alarm event based on an alarm path diagram of a vehicle; wherein each alarm path in the alarm path diagram is used to describe a trigger relationship between at least two alarm events of the vehicle; performing fault detection on target components associated with the target alarm path, and determining a first component that has a fault among the target components.

[0008] Through the above method, the server can use the alarm path map of the vehicle to determine the target alarm path of the first alarm event, and perform fault detection on the target components associated with the target alarm path, and then determine the first component that has failed in the target components. In this way, compared with the solution in which the operation and maintenance personnel perform fault analysis on the alarm information, the fault analysis efficiency of the vehicle-mounted components can be effectively improved, so that the operation and maintenance personnel can repair the fault in a timely manner, thereby effectively improving the user experience, and can effectively reduce the operation and maintenance costs of the vehicle company. In addition, by performing fault detection on the target components associated with the target alarm path of the first alarm event, and determining the first component that actually failed in the target components, compared with the solution of directly performing fault detection on the components associated with the first alarm event, the fault identification accuracy of the vehicle-mounted components can be effectively improved.

[0009] In a possible implementation, the method further includes: outputting a first alarm prompt information, the first alarm prompt information being used to indicate that the first component has failed. In this implementation, the server only reports the alarm information corresponding to the first component that has actually failed to the user, effectively reducing the situation where the alarm event is falsely reported, thereby effectively reducing the number of alarms of the vehicle-mounted components.

[0010] In a possible implementation, the method further includes: obtaining a first alarm event; correspondingly, determining a target alarm path of the first alarm event according to an alarm path map of the vehicle, including: determining the target alarm path according to the first alarm event and the alarm path map. In this implementation, after obtaining the first alarm event, the server determines a target alarm path matching the first alarm event in the alarm path map, so that the determined target alarm path is more accurate.

[0011] In a possible implementation, the method further includes: receiving first configuration information from a user, the first configuration information being used to indicate a component domain and / or component associated with the first alarm event; determining a target alarm path for the first alarm event based on an alarm path diagram of the vehicle, including: determining a target alarm path in the alarm path diagram based on the component domain or component associated with the first alarm event. In this implementation, the user can directly configure the component domain and / or component of the first alarm event, and then the server can quickly determine a target alarm path matching the first alarm event in the alarm path diagram based on the component domain and / or component of the first alarm event.

[0012] In a possible implementation, when the target alarm path includes at least two alarm paths, the target component is a component associated with the alarm path in the at least two alarm paths whose confidences satisfy the first condition. In this implementation, when the target alarm path includes multiple alarm paths, the component associated with the alarm path in the multiple alarm paths whose confidences satisfy the first condition is used as the target component for fault detection, so that the server has a greater probability of determining that the first component has failed.

[0013] In a possible implementation, the first condition is that the confidence of the alarm path is greater than a first threshold, and the first threshold is configured by the user. In this implementation, the user configures the first threshold of the confidence of the alarm path so that the server can filter out the alarm path that meets the user's needs when the target alarm path includes multiple alarm paths.

[0014] In a possible implementation, the method further includes: obtaining historical alarm data of the vehicle in a first time period; and analyzing the historical alarm data to obtain an alarm path map. In this implementation, the alarm path map is constructed based on the historical alarm data of the vehicle in the first time period, so that the alarm path map has a high timeliness.

[0015] In a possible implementation, the method further includes: receiving second configuration information from a user, the second configuration information being used to indicate the first time period. In this implementation, the user can configure the time period of the historical alarm data, that is, the user can flexibly select vehicle alarm data within any period to construct the alarm path map. In this way, the alarm path map is timely.

[0016] In a possible implementation, analyzing historical alarm data to obtain an alarm path map includes: classifying the historical alarm data according to vehicle attributes to obtain multiple data sets; wherein the vehicle attributes include at least one of model, operation type, working condition, mileage, or version number; and constructing an alarm path map according to the multiple data sets. In this design, the server can classify the historical alarm data based on the vehicle attributes, so that the server can independently analyze the alarm data of vehicles with different attributes.

[0017] Among them, due to the different configurations of different models, the components or architectures of different models may also be different. Therefore, the server classifies the historical alarm data according to the vehicle model, and then the alarm data of different models can be independently analyzed later, which helps to build an alarm path map adapted to different models.

[0018] The operation types of vehicles include operation type and non-operation type. The operation type is divided into multiple types according to different driving environments of vehicles, for example, the operation type can include mining operation, port operation, and urban operation, etc. Therefore, the server classifies the historical alarm data according to the operation type of the vehicle, and then the alarm data of different operation types can be analyzed independently in the future, which helps to build an alarm path map adapted to different driving environments.

[0019] The vehicle's operating conditions include charging, discharging, driving, etc. The vehicle's alarm data is different under different operating conditions, so the server classifies the historical alarm data according to the vehicle's operating conditions, and then the alarm data of different operating conditions can be independently analyzed later, which helps to build an alarm path map adapted to different operating conditions.

[0020] Mileage is used to represent the total mileage of a vehicle from the time it left the factory to the present. Since vehicles with lower mileage have a lower probability of failure, and vehicles with higher mileage have a higher probability of failure, the server classifies historical alarm data according to the mileage of the vehicle, and then can perform independent analysis on alarm data of different mileages, which helps to build an alarm path map adapted to vehicles of different mileages, so that the alarm data of vehicles of different mileages will not interfere with each other.

[0021] The version number is used to identify the software version in the vehicle (for example, the alarm mechanism version of the vehicle). Different version numbers may correspond to different alarm mechanisms. Therefore, the alarm data of the vehicle is classified according to the version number of the vehicle, so that the server can analyze the alarm data under different alarm mechanisms independently, which can effectively avoid the mutual interference caused by the alarm data under different alarm mechanisms.

[0022] In a possible implementation, constructing an alarm path map based on multiple data sets includes: determining historical alarm events based on the multiple data sets; and constructing an alarm path map based on the historical alarm events. In this design, by extracting historical alarm events from multiple data sets, the server can construct an alarm path map based on historical alarm events without being interfered by other data.

[0023] In a possible implementation, the method further includes: receiving third configuration information from the user, the third configuration information being used to indicate a second threshold value and / or a target alarm level; the confidence of each alarm path being greater than the second threshold value, and / or the alarm event associated with each alarm path being in accordance with the target alarm level. In this design, the alarm path can be screened in combination with the second threshold value and / or the target alarm level configured by the user. For example, only when the confidence of the alarm path is greater than the second threshold value, the alarm path is used as the alarm path in the alarm path map, effectively improving the reliability of the alarm path map. For another example, only when the alarm path is in accordance with the target alarm level, the alarm path is used as the alarm path in the alarm path map, so that the alarm path map meets user needs.

[0024] In a possible implementation, the method further includes: receiving fourth configuration information from the user, the fourth configuration information being used to add or delete an alarm path in the alarm path map. In this design, the user can flexibly add or delete alarm paths in the alarm path map, so that the constructed alarm path map meets the needs of the user.

[0025] In one possible implementation, the information of each alarm path in the alarm path diagram may include at least one of the following: the confidence of each alarm path, the components or component domains associated with each alarm path, or the alarm levels of at least two alarm events associated with each alarm path, and the components or component domains corresponding to at least two alarm events associated with each alarm path.

[0026] In a possible implementation, the method further includes: obtaining a second alarm event; if the alarm level of the second alarm event is higher than the first level, outputting a second alarm message, the second alarm message being used to indicate that a second component associated with the second alarm event has failed. In this implementation, for a second alarm event with a higher alarm level (such as brake failure, excessive battery pressure of the BMS, and other high-risk events), there is no need to perform fault detection on the second alarm event, and the alarm prompt message can be directly output.

[0027] In a second aspect, an embodiment of the present application provides a detection device, which includes a module or unit for implementing the above-mentioned detection method.

[0028] In a third aspect, an embodiment of the present application provides a communication device, comprising: a communication interface for communicating with other devices; and a processor coupled to the communication interface so that the communication device executes the method described in the first aspect and any possible implementation method of the first aspect.

[0029] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program runs on a computer, the computer executes the method described in the first aspect and any possible implementation of the first aspect.

[0030] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes a computer program. When the computer program runs on a computer, it enables the computer to execute the method described in the first aspect and any possible implementation of the first aspect.

[0031] In a sixth aspect, an embodiment of the present application provides a chip, comprising a processor, wherein the processor is coupled to a memory and is used to execute a computer program or instructions stored in the memory. When the computer program or instructions are executed, the method described in the first aspect and any possible implementation method of the first aspect is implemented.

[0032] In a seventh aspect, an embodiment of the present application provides a vehicle, comprising a unit for implementing the method described in the first aspect and any possible implementation method of the first aspect.

[0033] In an eighth aspect, an embodiment of the present application provides a terminal device, which can be used to implement the method described in the first aspect and any possible implementation of the first aspect. For example, the terminal device includes but is not limited to: intelligent transportation equipment (such as cars, ships, drones, trains, trucks, etc.), intelligent manufacturing equipment (such as robots, industrial equipment, intelligent logistics, intelligent factories, etc.), and intelligent terminals (mobile phones, computers, tablet computers, PDAs, desktops, headphones, speakers, wearable devices, vehicle-mounted devices, etc.).

[0034] Based on the implementations provided in the above aspects, the embodiments of the present application can be further combined to provide more implementations.

[0035] The technical effects that can be achieved by any possible implementation method in any of the second to eighth aspects mentioned above can be correspondingly referred to the description of the technical effects that can be achieved by any possible implementation method in any of the first aspect mentioned above, and the repetitions will not be discussed here. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 A schematic diagram showing an application scenario to which the embodiments of the present application are applicable;

[0037] Figure 2 A schematic diagram showing a flow chart of a detection method according to an embodiment of the present application is shown;

[0038] Figure 3AOne of the schematic diagrams of the alarm path diagram provided in the embodiment of the present application is shown;

[0039] Figure 3B A second schematic diagram of an alarm path diagram provided in an embodiment of the present application is shown;

[0040] Figure 3C A third schematic diagram of an alarm path diagram provided in an embodiment of the present application is shown;

[0041] Figure 3D A fourth schematic diagram of an alarm path diagram provided in an embodiment of the present application is shown;

[0042] Figure 3E One of the user interface schematic diagrams provided in the embodiment of the present application is shown;

[0043] Figure 3F A fifth schematic diagram of an alarm path diagram provided in an embodiment of the present application is shown;

[0044] Figure 3G A sixth schematic diagram of an alarm path diagram provided in an embodiment of the present application is shown;

[0045] Figure 3H A second user interface schematic diagram provided in an embodiment of the present application is shown;

[0046] Figure 4A A schematic diagram of the architecture of a server adopted in an embodiment of the present application is shown;

[0047] Figure 4B One of the schematic diagrams of the process of constructing an alarm path diagram in an embodiment of the present application is shown;

[0048] Figure 5 The third user interface schematic diagram provided in the embodiment of the present application is shown;

[0049] Figure 6 The second schematic diagram of the process of constructing an alarm path diagram according to an embodiment of the present application is shown;

[0050] Figure 7 A schematic diagram showing the division of a data set in an embodiment of the present application is shown;

[0051] Figure 8 A schematic diagram of extracting alarm events according to an embodiment of the present application is shown;

[0052] Fig. 9 A schematic diagram of alarm path screening according to an embodiment of the present application is shown;

[0053] Fig. 10A A fourth user interface schematic diagram provided in an embodiment of the present application is shown;

[0054] Fig. 10BA fifth user interface schematic diagram provided in an embodiment of the present application is shown;

[0055] Fig. 10C A sixth user interface schematic diagram provided in an embodiment of the present application is shown;

[0056] Fig. 10D A seventh user interface schematic diagram provided in an embodiment of the present application is shown;

[0057] Fig.10E An eighth user interface schematic diagram provided in an embodiment of the present application is shown;

[0058] Fig.11 A schematic diagram of a detection device according to an embodiment of the present application is shown;

[0059] Fig.12 A schematic diagram of a communication device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0060] To facilitate understanding, some terms involved in the embodiments of the present application are first introduced below.

[0061] 1. User:

[0062] The "user" mentioned in the embodiments of the present application may include the operation and maintenance personnel of the automobile enterprise and the person using the terminal device. The person using the terminal device may include the owner of the terminal device, or other persons authorized by the owner of the terminal device to use the terminal device, such as relatives, friends, colleagues, etc. of the owner of the terminal device. Taking the terminal device as a vehicle as an example, the user may be the owner of the vehicle, or other persons authorized by the owner to use the vehicle.

[0063] 2. User equipment (UE):

[0064] Generally refers to the electronic devices used by the user. Taking the terminal device as a vehicle as an example, the user device may include the vehicle-mounted terminal of the vehicle used by the user or the user's smart terminal, such as a mobile phone, tablet computer, etc. For unmanned vehicles, the user device may be the vehicle-mounted terminal of the vehicle; it may also be a smart terminal placed on the vehicle, such as a mobile phone, tablet computer, etc.; it may also be other electronic devices associated with the vehicle, such as electronic devices operated by the operation and maintenance personnel of the vehicle company, which may include but are not limited to desktop computers, laptops, mobile phones, tablet computers, etc. The embodiments of this application do not limit the product form of the user device.

[0065] In the embodiment of the present application, the user can view the alarm path map provided in the embodiment of the present application through the user device, and perform operations such as configuration and modification on the alarm path map. This will be described in detail below and will not be repeated here.

[0066] 3. Alarm events:

[0067] Refers to one or more alarms generated by an onboard component in a vehicle in a first time period. For example, the onboard component is a battery management system (BMS), and the alarm event may be one or more alarms generated by the BMS in the first time period due to sensor failure during the high voltage process.

[0068] 4. Alarm data:

[0069] It is the alarm data associated with the vehicle-mounted components in the vehicle. Among them, the alarm data of a vehicle-mounted component includes multiple alarm events. For example, the vehicle-mounted component takes BMS as an example, and the alarm data of BMS includes one or more alarms generated by BMS due to sensor failure in the high-voltage process in the first time period, and one or more alarms generated by BMS due to low voltage supply voltage failure in the first time period.

[0070] 5. Alarm path diagram:

[0071] In the embodiment of the present application, the alarm path diagram includes multiple alarm paths, and each alarm path diagram is used to describe the trigger relationship between at least two alarm events of the vehicle. For example, alarm path 1 is associated with alarm event A and alarm event B, and in alarm path 1, alarm event A will trigger alarm event B. For another example, alarm path 2 is associated with alarm event A, alarm event A, and alarm event C, and in alarm path 2, alarm event A will trigger alarm event B, and alarm event B will trigger alarm event C.

[0072] In the embodiments of the present application, "at least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.

[0073] Furthermore, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the priority or importance of multiple objects. For example, the first configuration information and the second configuration information are only used to distinguish different configuration information, rather than indicating the difference in priority or importance of the two indication information.

[0074] As can be seen from the description of the background technology, how to improve the fault analysis efficiency of vehicle-mounted components and reduce the operation and maintenance costs of vehicle-mounted components are important issues that the industry urgently needs to solve.

[0075] In order to improve the efficiency of fault analysis of vehicle-mounted components, in some technical solutions, operation and maintenance experts build fault analysis templates based on common fault analysis indicators, so that operation and maintenance personnel can use the fault analysis templates to perform fault analysis on the alarm data of vehicle-mounted components. However, this solution relies on expert experience, resulting in a limited number of fault types applicable to the fault analysis template, which in turn leads to limited improvement in the efficiency of fault analysis.

[0076] In other technical solutions, based on the current alarm mechanism of the vehicle-mounted components, the known fault analysis rules are designed into a fault tree, and the alarm data of the vehicle-mounted components are analyzed through the fault tree. However, over the air (OTA) technology is widely used in the upgrade of vehicle-mounted components. Generally, the alarm mechanism is updated or repaired through OTA. After the OTA upgrade, the alarm mechanism of the vehicle-mounted components will also change. At this time, the constructed fault tree is no longer compatible with the current alarm mechanism, so the fault tree needs to be modified accordingly. In this way, the development failures of the front-end operation and maintenance personnel will increase, which will increase the operation and maintenance costs of the vehicle-mounted components.

[0077] In summary, the above technical solution has limited improvement in the efficiency of fault analysis of vehicle-mounted components, and the operation and maintenance costs of the vehicle-mounted components are relatively high.

[0078] In view of this, the embodiments of the present application provide a detection method, device and system to improve the fault analysis efficiency of vehicle-mounted components and reduce the operation and maintenance costs of vehicle-mounted components. In this method, the target alarm path of the first alarm event can be determined by using the alarm path diagram of the vehicle, and the target component associated with the target alarm path can be fault detected, and then the first component that has failed can be determined in the target component. In this way, compared with the solution in which the operation and maintenance personnel perform fault analysis on the alarm information, the fault analysis efficiency of the vehicle-mounted components can be effectively improved, so that the operation and maintenance personnel can repair the fault in time, thereby effectively improving the user experience, and can effectively reduce the operation and maintenance costs of the car company. In addition, by performing fault detection on the target component associated with the target alarm path of the first alarm event, and determining the first component that actually fails in the target component, the fault identification accuracy of the vehicle-mounted components can be effectively improved compared with the solution in which the components associated with the first alarm event are directly fault detected.

[0079] Among them, the method and the device are based on the same technical concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated. In addition, in each embodiment of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their internal logical relationship.

[0080] Figure 1 A schematic diagram of an application scenario to which the embodiments of the present application are applicable.

[0081] See also Figure 1 As shown, the application scenario may include a terminal device 110 and a server 120. The terminal device 110 may collect alarm data of each vehicle-mounted component in the vehicle, and report the alarm data of each vehicle-mounted component to the server 120. The server 120 may perform fault analysis on the vehicle-mounted component according to the alarm data of each vehicle-mounted component, locate the vehicle-mounted component that has failed, and generate corresponding alarm information, which may be used to indicate the vehicle-mounted component that has failed. The terminal device 110 may be any one of a vehicle, a vehicle-mounted controller, a vehicle-mounted terminal, etc.

[0082] Optionally, the scenario may also include a user device 130. The user device 130 may be, for example, an onboard terminal of a vehicle used by the user or a smart terminal of the user, such as a mobile phone, a tablet computer, etc. Accordingly, in a possible implementation, after locating the faulty onboard component and generating corresponding alarm information, the server 120 may also send the alarm information to the user device 130, and the user device 130 may display the alarm information to the user, and the alarm information may be used to indicate the faulty onboard component. In this way, it is convenient for the user to repair the faulty onboard component in a timely manner.

[0083] based on Figure 1 The application scenario shown, the embodiment of the present application proposes a detection method. The method can be implemented by a detection device, which can be an independent device, a chip or component in a device, or software. The vehicle detection device can be deployed in the cloud, the vehicle side, or any one of the third-party devices. Correspondingly, the vehicle detection device can be, for example, a cloud server, a controller in a vehicle (such as a whole vehicle domain controller, a body domain controller, etc.), an electronic control unit (electronic control unit, ECU) in a vehicle, a vehicle-mounted terminal, a third-party server, etc. Alternatively, the vehicle detection device can be a newly added hardware module in the vehicle, and the hardware module can be configured with relevant judgment logic or algorithm, which can be used as an ECU in the vehicle, and transmit information with other ECUs through an internal communication network to realize the detection method of the embodiment of the present application. The embodiment of the present application does not limit the product form or deployment method of the detection device.

[0084] The following detection device is Figure 1 Taking the server 120 in the example as an example, the method provided in the embodiment of the present application is introduced. Figure 2 1 shows a flow chart of the detection method of the embodiment of the present application, which can be implemented by the server 120. It should be understood that the server 120 as the execution subject of the method is only an example and is not a limitation of the embodiment of the present application. Figure 2 As shown, the detection method may include the following steps:

[0085] S201: The server 120 determines a target alarm path of a first alarm event according to an alarm path map of the vehicle.

[0086] S202: The server 120 performs fault detection on target components associated with the target alarm path, and determines a first component having a fault among the target components.

[0087] In an embodiment of the present application, the alarm path diagram of the vehicle includes multiple alarm paths. Each alarm path in the alarm path diagram is used to describe the trigger relationship between at least two alarm events of the vehicle. For example, alarm path 1 is a sensor failure during a high-voltage process on the battery management system (BMS) that triggers an undervoltage of the low-voltage power supply of the front motor controller (motor control unit front, MCUF0). For another example, alarm path 2 is a sensor failure during a high-voltage process on the BMS that triggers an undervoltage of the low-voltage power supply of MCUF0, and the undervoltage of the low-voltage power supply of MCUF0 triggers an undervoltage of the low-voltage power supply of the rear motor controller (rear motor control unit, MCUR0).

[0088] In a possible implementation, the information of each alarm path in the alarm path diagram may include at least one of the following: the confidence of each alarm path, the components or component domains associated with each alarm path, or the alarm levels of at least two alarm events associated with each alarm path, and the components or component domains corresponding to at least two alarm events associated with each alarm path. Among them, the confidence of each alarm path is used to characterize the credibility of each alarm path; the components associated with each alarm path are the vehicle-mounted components involved in the alarm path; the component domain associated with each alarm path is the component domain to which the vehicle-mounted components involved in the alarm path belong (for example, it can be any one of the body domain, chassis domain, automatic driving domain, entertainment domain, etc.); the components corresponding to at least two alarm events associated with each alarm path are the vehicle-mounted components corresponding to the at least two alarm events, and the component domain corresponding to at least two alarm events associated with each alarm path is the component domain to which the at least two alarm events belong. The following is a detailed description in conjunction with Examples 1 to 3.

[0089] Example 1: Figure 3A One of the alarm path diagrams provided in the embodiment of the present application is shown, in which each alarm path in the alarm path diagram includes a component associated with the alarm path and the alarm levels of at least two alarm events associated with the alarm path. For example, Figure 3AThe alarm path ① in the alarm path diagram shown is: BMS-level 1-sensor failure during high-voltage application triggers MCUF0-level 2-low-voltage power supply undervoltage; wherein, the alarm level of sensor failure during BMS high-voltage application is level 1, and the alarm level of MCUF0 low-voltage power supply undervoltage is level 2. The alarm path ② in the alarm path diagram is: BMS-level 1-sensor failure during high-voltage application triggers MCUR0-level 2-low-voltage power supply undervoltage, MCUR0-level 2-low-voltage power supply undervoltage triggers the motor control unit (GCU)-level 2-low-voltage power supply undervoltage fault; wherein, the alarm level of sensor failure during BMS high-voltage application is level 1, the alarm level of MCUR0 low-voltage power supply undervoltage is level 2, and the alarm level of GCU low-voltage power supply undervoltage fault is level 2.

[0090] Example 2: Figure 3B The second schematic diagram of the alarm path diagram provided by the embodiment of the present application is shown, in which each alarm path in the alarm path diagram includes a component associated with the alarm path, a confidence level associated with the alarm path, and an alarm level of at least two alarm events associated with the alarm path. For example, Figure 3B The alarm path ① in the alarm path diagram shown is: BMS-level 1-sensor failure during high-voltage application triggers MCUF0-level 2-low-voltage power supply undervoltage; wherein, the alarm level of sensor failure during BMS high-voltage application is level 1, the alarm level of MCUF0 low-voltage power supply undervoltage is level 2, and the confidence of alarm path ① is 0.85. The alarm path ② in the alarm path diagram is: BMS-level 1-sensor failure during high-voltage application triggers MCUR0-level 2-low-voltage power supply undervoltage, MCUR0-level 2-low-voltage power supply undervoltage triggers GCU-level 2-low-voltage power supply undervoltage fault; wherein, the alarm level of sensor failure during BMS high-voltage application is level 1, the alarm level of MCUR0-low-voltage power supply undervoltage is level 2, the alarm level of GCU low-voltage power supply undervoltage fault is level 2, and the confidence of alarm path ② is 0.75.

[0091] Example 3: Figure 3C The third schematic diagram of the alarm path diagram provided by the embodiment of the present application is shown, in which each alarm path in the alarm path diagram includes the components and component domains associated with the alarm path, the confidence associated with the alarm path, and the alarm levels of at least two alarm events associated with the alarm path. For example, Figure 3CAlarm path ① in the alarm path diagram shown is: BMS-level 1-sensor failure during high-voltage process triggers MCUF0-level 2-low-voltage power supply undervoltage; among them, the alarm level of sensor failure during the BMS high-voltage process is level 1, the alarm level of MCUF0 low-voltage power supply undervoltage is level 2, the component domain to which the sensor failure during the BMS high-voltage process and MCUF0 low-voltage power supply undervoltage belong is the electrical domain, and the confidence of alarm path ① is 0.85. Alarm path ② in the alarm path diagram is: BMS-level 1-sensor failure during high-voltage process triggers MCUR0-level 2-low-voltage power supply undervoltage, MCUR0-level 2-low-voltage power supply undervoltage triggers GCU-level 2-low-voltage power supply undervoltage fault; among them, the alarm level of sensor failure during the BMS high-voltage process is level 1, the alarm level of MCUR0 low-voltage power supply undervoltage is level 2, and the alarm level of GCUR0 low-voltage power supply undervoltage fault is level 2; the component domain to which the sensor failure, MCUR0 low-voltage power supply undervoltage, and GCU low-voltage power supply undervoltage fault during the BMS high-voltage process belong is the electrical domain, and the confidence of alarm path ② is 0.75.

[0092] In the embodiment of the present application, the "first alarm event" may include an alarm event of one or more components of the vehicle within a first duration, and the first duration may be a default setting or a user configuration. Also, the "target alarm path" may include one or more alarm paths, and an alarm event of one component may correspond to one or more alarm paths.

[0093] In the embodiment of the present application, when S201 is implemented, the server 120 determines the target alarm path of the first alarm event according to the alarm path map of the vehicle, which may include but is not limited to the following implementations:

[0094] In implementation mode 1, the server 120 obtains the first alarm event, and determines the target alarm path according to the first alarm event and the alarm path map. Specifically, the server 120 may receive the first alarm event reported by the terminal device 110, match the first alarm event with the alarm event in the alarm path map, and use all paths involved in the first alarm event in the alarm path map as the target alarm path.

[0095] For example, the first alarm event is that the BMS has one or more alarms due to a low voltage supply voltage failure within the first time period, and the server 120 combines Figure 3DThe alarm path diagram shown can determine that the alarm path corresponding to the BMS low-voltage power supply voltage is too low fault is: alarm path ①, DCDC-2 level - battery voltage is too low, triggering BMS-3 level - low-voltage power supply voltage is too low fault; alarm path ②, BMS-1 ​​level - sensor failure during high-voltage application, triggering MCUF0-2 level - low-voltage power supply undervoltage, MCUF0-2 level - low-voltage power supply undervoltage triggers MCUR0-2 level - low-voltage power supply undervoltage, MCUR0-2 level - low-voltage power supply undervoltage triggers BMS-3 level - low-voltage power supply voltage is too low fault; alarm path ③, BMS-1 ​​level - sensor failure during high-voltage application, triggering MCUF0-2 level - low-voltage power supply undervoltage, MCUF0-2 level - low-voltage power supply undervoltage triggers BMS-3 level - low-voltage power supply voltage is too low fault; accordingly, the server 120 uses alarm path ①, alarm path ②, and alarm path ③ as the target alarm paths for the first alarm event.

[0096] In implementation mode 2, the server 120 receives the first configuration information of the user, and the first configuration information is used to indicate the component domain and / or component associated with the first alarm event, and then the server 120 can determine the alarm path matching the component domain and / or component associated with the first alarm event in the alarm path diagram based on the component domain and / or component associated with the first alarm event, and use these alarm paths as target alarm paths. In this way, the efficiency of the server in determining the target alarm path of the first alarm event can be improved, and then the efficiency of fault detection of the target component associated with the target alarm path can be effectively improved.

[0097] Exemplarily, the user equipment 130 provides the following Figure 3E In the user interface shown, the user can configure the information of the first alarm event, that is, the component domain and / or component associated with the first alarm event. For example, if the first alarm event is that the BMS has one or more alarms due to a low voltage supply voltage failure within a first time period, the user can configure the component associated with the first alarm event as the BMS in the interface, and the component domain associated with the first alarm event is the electrical domain, the user can configure the component domain associated with the first alarm event as the electrical domain in the interface; further, the server 120 can configure the component domain associated with the first alarm event as the electrical domain based on the electrical domain and the BMS. Figure 3FIn the alarm path diagram shown, the alarm paths that match the electrical domain and BMS are determined as follows: alarm path ①, BMS-level 1-sensor failure during high-voltage application, triggering MCUF0-level 2-low-voltage power supply undervoltage, MCUF0-level 2-low-voltage power supply undervoltage triggers MCUR0-level 2-low-voltage power supply undervoltage, MCUR0-2-low-voltage power supply undervoltage triggers BMS-level 3-low-voltage power supply voltage is too low fault; alarm path ②, BMS-level 1-sensor failure during high-voltage application, triggering MCUF0-level 2-low-voltage power supply undervoltage, MCUF0-2-low-voltage power supply undervoltage triggers BMS-level 3-low-voltage power supply voltage is too low fault; accordingly, the server 120 uses alarm path ① and alarm path ② as the target alarm paths for the first alarm event.

[0098] Implementation method 3, the server 120 obtains the first alarm event, and receives the first configuration information of the user, and the first configuration information is used to indicate the component domain and / or component associated with the first alarm event. Specifically, the server 120 can receive the first alarm event reported by the terminal device 110, and then based on the first alarm event and the component domain and / or component associated with the first alarm event, determine the alarm path that matches the first alarm event and the component domain and / or component associated with the first alarm event in the alarm path diagram, and use these alarm paths as target alarm paths. In this way, the target alarm path corresponding to the first alarm event determined by the server 120 is more accurate.

[0099] For example, the first alarm event is that the direct-current converter (DCDC) has one or more alarms due to low battery voltage within the first time period, and the user can Figure 3E In the user interface shown, the component associated with the first alarm event is configured as DCDC, and the component domain associated with the first alarm event is the electrical domain. The user can configure the component domain associated with the first alarm event as the electrical domain in the interface; further, the server 120 can configure the component domain associated with the first alarm event as the electrical domain based on the first alarm event, the electrical domain and the BMS. Figure 3GIn the alarm path diagram shown, the alarm paths that match the first alarm event and the electrical domain are determined as follows: alarm path ①, DCDC-2 level - battery voltage is too low, triggering GCUR0-2 level - low voltage power supply undervoltage fault; alarm path ②, DCDC-2 level - battery voltage is too low, triggering MCUF0-2 level - low voltage power supply undervoltage; alarm path ③, DCDC-2 level - battery voltage is too low, triggering GCU-2 level - auxiliary voltage undervoltage fault; alarm path ④, DCDC-2 level - battery voltage is too low, triggering MCUR0-2 level - low voltage power supply undervoltage; alarm path ⑤, DCDC-2 level - battery voltage is too low, triggering BMS-3 level - low voltage power supply voltage is too low fault; accordingly, the server 120 uses alarm path ①-alarm path ⑤ as the target alarm path for the first alarm event.

[0100] In an embodiment of the present application, each alarm path is associated with at least two components, and correspondingly, the target component associated with the target alarm path includes at least two components. And, in an embodiment of the present application, the first component can be one or more components in the target component. Since there is a trigger relationship between at least two alarm events corresponding to an alarm path, the alarm event that triggers the alarm is referred to as a "source alarm event", and the alarm event to be triggered is referred to as a "derived alarm event". Correspondingly, the vehicle-mounted component associated with the source alarm event is referred to as a "source component", and the vehicle-mounted component associated with the derived alarm event is referred to as a "derived component". In some embodiments, the first component is a source component that fails in the target component. In other embodiments, the first component is a source component and a derived component that fail in the target component.

[0101] Accordingly, in the embodiment of the present application, when S202 is implemented, the server 120 performs fault detection on the target component associated with the target alarm path, and the first component that fails in the target component may include but is not limited to the following implementations:

[0102] In implementation mode 1, when the target alarm path includes one or more alarm paths, the server 120 directly performs fault detection on components associated with the one or more alarm paths.

[0103] Example 1: The first alarm event includes alarm event A. The server 120 determines that the target alarm path of alarm event A is alarm path 1 based on the alarm path map of the vehicle. Alarm path 1 is associated with components A and B. Component A corresponds to alarm event A, component B corresponds to alarm event B, and in alarm path 1, alarm event B triggers alarm event A. Therefore, the target components include components A and B, and the server 120 performs fault detection on components A and B. After the server 120 performs fault detection on components A and B, the server 120 determines that the first component that has a fault may have the following conditions:

[0104] In case 1, when the server 120 determines that component A fails, it determines component A as the first component.

[0105] In case 2, when the server 120 determines that component B fails, it determines component B as the first component.

[0106] Case 3: When server 120 determines that component A and component B fail, it determines component A and component B (ie, the failed source component and the derived component) as the first component, or determines component B (ie, the failed source component) as the first component.

[0107] Example 2: The first alarm event includes alarm event A and alarm event C. The server 120 determines the alarm path of alarm event A as alarm path 1 and the alarm path of alarm event C as alarm path 2 based on the alarm path diagram of the vehicle. Then the target alarm path includes alarm path 1 and alarm path 2. Among them, alarm path 1 is associated with component A and component B, component A corresponds to alarm event A, component B corresponds to alarm event B, and in alarm path 1, alarm event B will trigger alarm event A; alarm path 2 is associated with component C and component D, component C corresponds to alarm event C, component D corresponds to alarm event D, and in alarm path 2, alarm event D will trigger alarm event C; therefore, the target components include component A, component B, component C and component D, and the server 120 performs fault detection on component A, component B, component C and component D. Among them, after the server 120 performs fault detection on component A, component B, component C and component D, the server 120 determines that the first component that has failed may have the following conditions:

[0108] In case 1, when the server 120 determines that component A fails, it determines component A as the first component.

[0109] In case 2, when the server 120 determines that component B fails, it determines component B as the first component.

[0110] Case 3: When server 120 determines that component A and component B fail, it determines component A and component B (ie, the failed source component and the derived component) as the first component, or determines component B (ie, the failed source component) as the first component.

[0111] In case 4, when the server 120 determines that component C fails, it determines component C as the first component.

[0112] In case 5, when the server 120 determines that component D fails, it determines component D as the first component.

[0113] Case 6: When server 120 determines that component C and component D fail, it determines component C and component D (ie, the failed source component and the derived component) as the first component, or determines component D (ie, the failed source component) as the first component.

[0114] In case 7, when the server 120 determines that component B and component D fail, the server 120 determines component B and component D as first components.

[0115] In case 8, when the server 120 determines that components A and C fail, it determines components A and C as first components.

[0116] Case 9: When server 120 determines that component A, component B, component C, and component D fail, it determines component A, component B, component C, and component D (i.e., the failed source component and the derived component) as the first component, or determines component B and component D (i.e., the failed source component) as the first component.

[0117] Example three, the first alarm event includes alarm event A, and the server 120 determines that the target alarm path of alarm event A includes alarm path 1 and alarm path 2 based on the alarm path map of the vehicle. Among them, alarm path 1 is associated with component A and component B, component A corresponds to alarm event A, component B corresponds to alarm event B, and in alarm path 1, alarm event B will trigger alarm event A; alarm path 2 is associated with component C, component D and component A, component C corresponds to alarm event C, component D corresponds to alarm event D, and in alarm path 2, alarm event D will trigger alarm event C, and alarm event C will trigger alarm event A. Therefore, the target components include component A, component B, component C and component D, and the server 120 performs fault detection on component A, component B, component C and component D. Among them, after the server 120 performs fault detection on component A, component B, component C and component D, the server 120 determines that the first component that has failed may have the following situations:

[0118] In case 1, when the server 120 determines that component A fails, it determines component A as the first component.

[0119] In case 2, when the server 120 determines that component B fails, it determines component B as the first component.

[0120] In case 3, when the server 120 determines that component C fails, it determines component C as the first component.

[0121] In case 4, when the server 120 determines that component D fails, it determines component D as the first component.

[0122] Case 5: When determining that component A and component B fail, server 120 determines component A and component B (ie, the failed source component and the derived component) as the first component, or determines component B (ie, the failed source component) as the first component.

[0123] Case 6: When server 120 determines that components A, C, and D fail, it determines components A, C, and D (i.e., the failed source components and derived components) as the first components, or determines component D (i.e., the failed source component) as the first component.

[0124] Embodiment 2: When the target alarm path includes at least two alarm paths, the component associated with the alarm path whose confidence level in the at least two alarm paths satisfies the first condition is used as the target component for fault detection. In this way, the probability of determining that the first component has failed is greater. Optionally, the first condition may be that the confidence level of the alarm path is greater than a first threshold; wherein the first threshold may be pre-configured or user-configured.

[0125] Exemplarily, the user equipment 130 provides the following Figure 3H In the user interface shown, the user configures the first threshold of confidence to 0.85 in the interface; the first alarm event includes alarm event A, and the server 120 determines that the target alarm path of alarm event A includes alarm path 1 and alarm path 2 based on the alarm path map of the vehicle. Among them, the confidence of alarm path 1 is 0.75, and the confidence of alarm path 2 is 0.9, then only the confidence of alarm path 2 is greater than the first threshold. Alarm path 2 associates component C, component D and component A, and in alarm path 2, alarm event D will trigger alarm event C, and alarm event C will trigger alarm event A; then the server 120 uses component C, component D and component A as target components for fault detection. Among them, after the server 120 performs fault detection on component C, component D and component A, the server 120 determines that the following situations may exist in the faulty first component:

[0126] In case 1, when the server 120 determines that component A fails, it determines component A as the first component.

[0127] In case 2, when the server 120 determines that component C fails, it determines component C as the first component.

[0128] In case 3, when the server 120 determines that component D fails, it determines component D as the first component.

[0129] Case 4: When server 120 determines that component C and component D fail, it determines component C and component D (ie, the failed source component and the derived component) as the first component, or determines component D (ie, the failed source component) as the first component.

[0130] Case 5: When server 120 determines that components A, C, and D fail, it determines components A, C, and D (i.e., the failed source components and derived components) as the first components, or determines component D (i.e., the failed source component) as the first component.

[0131] In the embodiment of the present application, when the first component fails, the server 120 may also output a first alarm prompt information, which is used to indicate that the first component fails. In this way, the user can repair the failure of the first component in time. In this way, and in the case where there is a trigger relationship between multiple alarm events of the vehicle, the first component that actually fails is traced back, and only the alarm information corresponding to the first component that actually fails is reported, which effectively reduces the situation of misreporting of alarm events, and thus effectively reduces the number of alarms of vehicle-mounted components. Among them, the first alarm prompt information can be any one of voice information, text information, or image information, etc., and the embodiment of the present application does not make specific restrictions. For example, the first component is a BMS, the user device 130 is a user's mobile phone, and the server 120 can control the mobile phone to display text prompt information related to the BMS failure. For another example, the first component is a BMS, and the user device 130 takes a car audio as an example, and the server 120 can control the car audio to display voice prompt information related to the BMS failure.

[0132] In some other possible embodiments of the present application, the server 120 may also obtain a second alarm event; if the alarm level of the second alarm event is higher than the first level, a second alarm message is output, and the second alarm message is used to indicate that a second component associated with the second alarm event has failed. Among them, "the alarm level of the second alarm event is higher than the first level" can be understood as the second alarm event being a high-risk alarm event. In this way, for high-risk alarm events, there is no need to perform fault detection on the second alarm event, and the corresponding alarm prompt information can be directly output. Among them, the first level can be, for example, level 2 or level 3. The second alarm event can be, for example, any event such as battery thermal runaway or brake failure.

[0133] The terminal device 110 below takes a vehicle as an example to introduce the construction process of the alarm path map provided in the embodiment of the present application.

[0134] Figure 4A FIG. 1 shows a schematic diagram of the architecture of the server 120. Figure 4AAs shown, a data storage system, a data processing system, a data analysis system, and a data visualization and management system may be deployed in the server 120 .

[0135] Among them, the data storage system is used to store the status data and alarm data of the vehicle-mounted components reported by the vehicle. The data processing system is used to clean and classify the alarm data to obtain the corresponding alarm events. The data analysis system uses the association rule mining algorithm to analyze the alarm events, generate the alarm path, and construct the alarm path map according to the alarm path. The alarm path map can be saved in the data storage system. The data visualization and management system is used to control the user device 130 to display the alarm path map, the alarm path map configuration interface, the alarm prompt information, etc.

[0136] based on Figure 4A The system architecture shown in FIG. 1 is a diagram of a process for constructing an alarm path map. The process can be implemented by the server 120, such as Figure 4B As shown, the process of the server 120 constructing the alarm path map may include the following steps:

[0137] S401. The server 120 obtains historical alarm data of a vehicle within a first time period.

[0138] S402: The server 120 analyzes the historical alarm data to obtain an alarm path map.

[0139] In S401 and S402, an alarm path map is constructed through historical alarm data of the vehicle in the first time period, so that the alarm path map has high timeliness.

[0140] In the embodiment of the present application, when S401 is specifically implemented, the server 120 may receive historical alarm data from the vehicle, or the server 120 may obtain historical alarm data from a data storage system in the server 120. The first time period may be preset or user-configured.

[0141] Exemplarily, the data visualization and management system in the server 120 may control the user device 130 to display Figure 5 The user interface schematic diagram shown in FIG. 1 shows a user interface in which a user can configure a first time period. After the user configures the first time period in the interface, the user device generates corresponding second configuration information and sends the second configuration information to the server 120. The server 120 receives the second configuration information, and the second configuration information is used to indicate the first time period. For example, if the user selects 1 day as the first time period, the server 120 obtains the alarm data within 1 day and constructs an alarm path map based on the alarm data within 1 day.

[0142] like Figure 6As shown, in the embodiment of the present application, when S402 is implemented, S402 may include the following steps:

[0143] S4021. The server 120 classifies the historical alarm data according to the attributes of the vehicle to obtain multiple data sets.

[0144] Among them, the attributes of the vehicle include at least one of the model, operation type, working condition, mileage, or version number. That is to say, the server 120 classifies the historical alarm data according to at least one of the model, operation type, working condition, mileage, or version number of the vehicle to obtain multiple data sets. Among them, due to the different configurations of different models, the components or architectures of different models may also be different. Therefore, the server classifies the historical alarm data according to the model of the vehicle, and then the alarm data of different models can be independently analyzed later, which helps to build an alarm path map adapted to different models.

[0145] The operation types of vehicles include operation type and non-operation type. The operation type is divided into multiple types according to different driving environments of vehicles, for example, the operation type can include mining operation, port operation, and urban operation, etc. Therefore, the server classifies the historical alarm data according to the operation type of the vehicle, and then the alarm data of different operation types can be analyzed independently in the future, which helps to build an alarm path map adapted to different driving environments.

[0146] The vehicle's operating conditions include charging, discharging, driving, etc. The vehicle's alarm data is different under different operating conditions, so the server classifies the historical alarm data according to the vehicle's operating conditions, and then the alarm data of different operating conditions can be independently analyzed later, which helps to build an alarm path map adapted to different operating conditions.

[0147] Mileage is used to represent the total mileage of a vehicle from the time it left the factory to the present. Since vehicles with lower mileage have a lower probability of failure, and vehicles with higher mileage have a higher probability of failure, the server classifies historical alarm data according to the mileage of the vehicle, and then can perform independent analysis on alarm data of different mileages, which helps to build an alarm path map adapted to vehicles of different mileages, so that the alarm data of vehicles of different mileages will not interfere with each other.

[0148] The version number is used to identify the software version in the vehicle (for example, the alarm mechanism version of the vehicle). Different version numbers may correspond to different alarm mechanisms. Therefore, the alarm data of the vehicle is classified according to the version number of the vehicle, so that the server can analyze the alarm data under different alarm mechanisms independently, which can effectively avoid the mutual interference caused by the alarm data under different alarm mechanisms.

[0149] For example, Figure 7 As shown, the server 120 classifies the historical alarm data according to the vehicle model, operation type, working condition, mileage, and version number, and obtains the following data sets: Data set one is the alarm data of vehicles with model X1, operation type, operation condition, charging condition, and mileage greater than 5000; Data set two is the alarm data of vehicles with model X1, operation type, non-operation, driving condition, and mileage greater than 5000; Data set three is the alarm data of vehicles with model K1, operation type, mining operation, driving condition, and mileage greater than 1000; Data set four is the alarm data of vehicles with model K1, operation type, port operation, driving condition, and mileage greater than 3000.

[0150] Each of the multiple data sets can be understood as a collection of multiple alarm events. For example, Figure 7 Data set 1 includes all alarm data of BMS and all alarm data of MCU.

[0151] S4022. The server 120 extracts multiple alarm events from multiple data sets.

[0152] In the specific implementation S4022, the server 120 extracts the alarm events in each of the multiple data sets, which may include but is not limited to the following implementations:

[0153] In a possible implementation, the server 120 may extract alarm events from each data set based on the first component domain and form a corresponding alarm event set, where an alarm event set includes multiple alarm events. Among them, an alarm event set may be associated with a component domain; an alarm event set may be uniquely identified by a fault identifier (such as an alarm name or a DTC code). The first component domain may be, for example, any one of an electrical domain, a chassis domain, an autonomous driving domain, an entertainment domain, and the like. For example, Figure 8 As shown, the server 120 can be based on the electrical domain. Figure 7 Alternatively, the server 120 may extract the alarm event set of the electrical domain from the data sets 1 to 4 obtained in the chassis domain. Figure 7 The alarm event set of the chassis domain is extracted from data sets 1 to 4 obtained.

[0154] In another possible implementation, the server 120 may extract alarm events from each data set based on the first component and form a corresponding alarm event set, where an alarm event set includes multiple alarm events. One alarm event set may be associated with one component. The first component may be, for example, a VCU or a BMS. The server 120 may extract alarm events from each data set based on the first component and form a corresponding alarm event set. An alarm event set includes multiple alarm events. Figure 7Alternatively, the server 120 may extract the alarm event set of the VCU from the data sets 1 to 4 obtained in the BMS. Figure 7 The alarm event sets of BMS are extracted from data sets 1 to 4 obtained in the experiment.

[0155] In another possible implementation, the server 120 can extract alarm events in each data set based on the first component and the first component domain, and form a corresponding alarm event set, where an alarm event set includes multiple alarm events. Among them, an alarm event set can be associated with a component and one or more component domains. For example, the first component is the VCU, the first component domain is the electrical domain, the chassis domain, the autonomous driving domain, and the entertainment domain, and the server 120 can extract the alarm events of the electrical domain, the chassis domain, the autonomous driving domain, and the entertainment domain from the alarm data of the VCU. For another example, the first component is the battery of the vehicle, and the first component domain is the electrical domain; the battery will supply power to other components, so the battery will generate alarm data in other domains, but the server 120 can extract the alarm data generated by the battery in other domains and use it as the alarm event of the battery in the electrical domain.

[0156] S4023. The server 120 analyzes multiple alarm events and generates multiple alarm paths.

[0157] The server 120 will consider the trigger relationship between multiple events when generating multiple alarm paths. The trigger relationship includes at least one of triggering at the start, triggering at the end, triggering within a first time period after the start, or triggering within a second time period after the end. The first time period may be, for example, 30 seconds, 1 minute, or 5 minutes, and the second time period may be, for example, 30 seconds, 2 minutes, or 3 minutes, etc., and the embodiments of the present application do not impose specific limitations.

[0158] For example, when alarm event A triggers alarm event B at the beginning, the alarm path 1 generated by the server 120 is alarm event A (source alarm) -> alarm event B (derived alarm).

[0159] For another example, if alarm event B is triggered within the first period of time after alarm event A starts, the alarm path 2 generated by the server 120 is alarm event A (source alarm) -> alarm event B (derived alarm).

[0160] For another example, when alarm event A ends and triggers alarm event B, the alarm path 3 generated by the server 120 is alarm event A (source alarm) -> alarm event B (derived alarm).

[0161] For another example, if alarm event B is triggered within the second time period after alarm event A ends, the alarm path 4 generated by the server 120 is alarm event A (source alarm) -> alarm event B (derived alarm).

[0162] S4024. The server 120 constructs an alarm path map based on multiple alarm paths.

[0163] like Fig. 9 As shown, in the specific implementation S4024, the server 120 can further screen the multiple alarm paths, and based on the screened alarm paths, form an alarm path set for each component domain, and construct an alarm path map based on the alarm path set for each component domain.

[0164] In a possible implementation, the server 120 may receive third configuration information from the user, the third configuration information being used to indicate the second threshold and / or target alarm level; the server 120 may filter multiple alarm paths in combination with the second threshold and / or target alarm level configured by the user, and construct an alarm path map based on the filtered alarm paths. The second threshold is the threshold of the confidence level of the alarm path.

[0165] Example 1: The server 120 may control the user device 130 to provide Fig. 10A In the user interface shown, the user can configure the second threshold of confidence in the interface, and then the server 120 can filter out the alarm path with a confidence greater than the second threshold from multiple alarm paths according to the second threshold. For example, the second threshold is 0.85, and the alarm set of the electrical domain includes alarm path 1-alarm path 10, wherein the confidence of alarm path 1-alarm path 5 is greater than 0.85, and the confidence of alarm path 6-alarm path 10 is less than 0.85, then the server 120 constructs an alarm path map based on alarm path 1-alarm path 5.

[0166] Example 2: The server 120 may control the user device 130 to provide Fig. 10B The user interface shown in the figure can be used to configure the target alarm level in the interface, and then the server 120 can filter out the alarm paths of the alarm events that meet the target alarm level from the multiple alarm paths. For example, if the target alarm level configured by the user is level 2, the server 120 can filter out the alarm paths associated with the alarm events whose alarm levels are not level 2 from the multiple alarm paths, and build an alarm path map based on these alarm paths.

[0167] Example 3: The server 120 may control the user device 130 to provide Fig. 10CIn the user interface shown, the user can configure the second threshold and the target alarm level in the interface, and then the server 120 can filter out the alarm paths whose confidence is greater than the second threshold and whose alarm events meet the target alarm level from multiple alarm paths according to the second threshold and the target alarm level. For example, if the second threshold is 0.85 and the target alarm level includes level 1 and level 2, the server 120 can filter out the alarm paths associated with the alarm events with an alarm level of level 1 and the alarm paths associated with the alarm events with an alarm level of level 2 from multiple alarm paths, and filter out the alarm paths with a confidence greater than 0.85 from the alarm paths associated with the alarm events with an alarm level of level 1 and the alarm paths associated with the alarm events with an alarm level of level 2, and build an alarm path map based on these alarm paths.

[0168] Furthermore, the server 120 may also control the user device 130 to provide Fig. 10D The user interface shown in the figure allows users to add or delete alarm paths in the interface. Correspondingly, when the user enters the corresponding operation in the interface, the user device 130 will receive the fourth configuration information and send the fourth configuration information to the server 120. The server 120 can receive the fourth configuration information and add or delete the alarm path in the alarm path map according to the fourth configuration information. In this way, the user can flexibly add or delete the alarm path of the alarm path map, so that the constructed alarm path map meets the needs of the user. For example, the user in Fig. 10D In the user interface shown in FIG. 1 , alarm path 1 and alarm path 6 are selected, and the user clicks the delete button, then the server 120 deletes alarm path 1 and alarm path 6 from the alarm path map. Fig. 10D In the user interface shown in FIG. 1 , alarm path 1 is selected, and the user clicks the Modify button. Then the server 120 can control the user device 130 to provide the following Fig.10E The user interface shown, the user can modify the alarm path 1 in this interface.

[0169] Based on the same technical concept, the embodiment of the present application also provides a detection device for executing the method in the above method embodiment. The relevant features can be found in the above method embodiment and will not be described in detail here. Fig.11 As shown, the detection device 1100 may include:

[0170] The processing unit 1101 is used to determine a target alarm path of the first alarm event according to an alarm path diagram of the vehicle; wherein each alarm path in the alarm path diagram is used to describe a trigger relationship between at least two alarm events of the vehicle;

[0171] The detection unit 1102 is used to perform fault detection on the target components associated with the target alarm path, and determine a first component that has a fault among the target components.

[0172] In one possible design, the device also includes an acquisition unit 1103; the acquisition unit 1103 is used to acquire a first alarm event; when the processing unit 1101 is used to determine the target alarm path of the first alarm event based on the alarm path map of the vehicle, it is specifically used to: determine the target alarm path based on the first alarm event and the alarm path map.

[0173] In one possible design, the device also includes a receiving unit 1104; the receiving unit 1104 is used to receive the user's first configuration information, and the first configuration information is used to indicate the component domain and / or component associated with the first alarm event; the processing unit 1101 is used to determine the target alarm path of the first alarm event according to the alarm path map of the vehicle, specifically for: based on the component domain and / or component associated with the first alarm event, determining the target alarm path in the alarm path map.

[0174] In a possible design, when the target alarm path includes at least two alarm paths, the target component is a component associated with the alarm path in the at least two alarm paths whose confidence meets the first condition.

[0175] In a possible design, the first condition is that the confidence of the alarm path is greater than a first threshold, and the first threshold is configured by the user.

[0176] In a possible design, the device also includes an acquisition unit 1103; the acquisition unit 1103 is used to acquire historical alarm data of the vehicle within a first time period; the processing unit 1101 is also used to analyze the historical alarm data to obtain an alarm path map.

[0177] In one possible design, the device also includes a receiving unit 1104; the receiving unit 1104 is used to receive second configuration information of the user, and the second configuration information is used to indicate the first time period.

[0178] In one possible design, when the processing unit 1101 is used to analyze historical alarm data and obtain an alarm path map, it is specifically used to: classify the historical alarm data according to the attributes of the vehicle to obtain multiple data sets; wherein the attributes of the vehicle include at least one of the model, operating type, operating condition, mileage, or version number; and construct an alarm path map based on the multiple data sets.

[0179] In one possible design, the device also includes a receiving unit 1104; the receiving unit 1104 is used to receive third configuration information from the user, and the third configuration information is used to indicate a second threshold and / or a target alarm level; wherein the confidence of each alarm path is greater than the second threshold, and / or the alarm event associated with each alarm path meets the target alarm level.

[0180] In one possible design, the device also includes a receiving unit 1104; the receiving unit 1104 is used to receive the user's fourth configuration information, and the fourth configuration information is used to add or delete an alarm path in the alarm path map.

[0181] In one possible design, the information of each alarm path includes at least one of the following: the confidence of each alarm path, the components or component domains associated with each alarm path, or the alarm levels of at least two alarm events associated with each alarm path, and the components or component domains corresponding to at least two alarm events associated with each alarm path.

[0182] In a possible design, the device also includes a prompt unit 1105, which is used to output a first alarm prompt information, and the first alarm prompt information is used to indicate that a failure occurs in the first component.

[0183] In one possible design, the device also includes an acquisition unit 1103 and a prompt unit 1105; the acquisition unit 1103 is used to acquire a second alarm event; the prompt unit 1105 is also used to output a second alarm message when the alarm level of the second alarm event is higher than the first level, and the second alarm message is used to indicate that a second component associated with the second alarm event has a fault.

[0184] It should be understood that the division of the units in the above device is only a division of logical functions, and in actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. In addition, the units in the device can be implemented in the form of a processor calling software; for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of the units of the device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside the device or a memory outside the device. Alternatively, the units in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units can be realized by designing the hardware circuits, and the hardware circuits can be understood as one or more processors; for example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units are realized by designing the logical relationship of the components in the circuit; for another example, in another implementation, the hardware circuit can be realized by a programmable logic device (PLD), taking a field programmable gate array (FPGA) as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of some or all of the above units. All units of the above devices can be realized in the form of a processor calling software, or in the form of hardware circuits, or in part by a processor calling software, and the rest by hardware circuits.

[0185] In the embodiment of the present application, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a CPU, a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP), etc.; in another implementation, the processor can realize certain functions through the logical relationship of the hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the processor loads a configuration document to implement the process of hardware circuit configuration, which can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (Neural Network Processing Unit, NPU) tensor processing unit (Tensor Processing Unit, TPU), deep learning processing unit (Deep learning Processing Unit, DPU), etc.

[0186] It can be seen that each unit in the above device can be one or more processors (or processing circuits) configured to implement the above method, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0187] In addition, all or part of the units in the above device can be integrated together, or can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of each unit of the device. The type of the at least one processor may be different, for example, including a CPU and an FPGA, a CPU and an artificial intelligence processor, a CPU and a GPU, etc.

[0188] In a simple embodiment, those skilled in the art can imagine that the communication devices in the above embodiments can all be used Fig.12 The form shown.

[0189] like Fig.12 The device 1200 shown includes at least one processor 1210 and a communication interface 1230. In an optional design, a memory 1220 may also be included.

[0190] The specific connection medium between the processor 1210 and the memory 1220 is not limited in the embodiment of the present application.

[0191] In such Fig.12 In the device, the processor 1210 can transmit data through the communication interface 1230 when communicating with other devices.

[0192] When the communication device uses Fig.12 When the form shown is Fig.12 The processor 1210 in the apparatus 1200 can call the computer-executable instructions stored in the memory 1220 so that the apparatus 1200 can execute any of the above method embodiments.

[0193] An embodiment of the present application also relates to a chip system, which includes a processor for calling a computer program or computer instructions stored in a memory so that the processor executes the method of any of the above embodiments.

[0194] In a possible implementation manner, the processor may be coupled to the memory through an interface.

[0195] In a possible implementation, the chip system may also directly include a memory, in which a computer program or computer instructions are stored.

[0196] For example, the memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM).

[0197] An embodiment of the present application also relates to a processor, which is used to call a computer program or computer instruction stored in a memory so that the processor executes the method described in any of the above embodiments.

[0198] For example, in the embodiment of the present application, the processor is an integrated circuit chip with signal processing capabilities. For example, the processor can be an FPGA, a general-purpose processor, a DSP, an ASIC or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system chip (system on chip, SoC), a CPU, a network processor (network processor, NP), a microcontroller (microcontroller unit, MCU), a PLD or other integrated chip, and can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0199] It should be understood that the embodiments of the present application may be provided as methods, systems, or computer program products.

[0200] In a possible implementation, an embodiment of the present application provides a computer-readable storage medium, which stores a program code. When the program code runs on the computer, the computer executes the above method embodiment.

[0201] In a possible implementation, an embodiment of the present application provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute the above method embodiment.

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

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

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

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

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

Claims

1. A detection method, characterized in that: include: Determining a target alarm path of a first alarm event according to an alarm path diagram of the vehicle; wherein each alarm path in the alarm path diagram is used to describe a triggering relationship between at least two alarm events of the vehicle; Fault detection is performed on target components associated with the target alarm path, and a first component having a fault is determined among the target components.

2. The method according to claim 1, characterized in that The method further comprises: acquiring a first alarm event; Determining a target alarm path for a first alarm event based on an alarm path map of the vehicle includes: determining the target alarm path based on the first alarm event and the alarm path map.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: receiving first configuration information from a user, the first configuration information being used to indicate a component domain and / or component associated with the first alarm event; Determining the target alarm path of the first alarm event according to the alarm path map of the vehicle includes: determining the target alarm path in the alarm path map based on component domains and / or components associated with the first alarm event.

4. The method according to any one of claims 1 to 3, characterized in that: When the target alarm path includes at least two alarm paths, the target component is a component associated with the alarm path of the at least two alarm paths whose confidence meets the first condition.

5. The method according to claim 4, characterized in that The first condition is that the confidence of the alarm path is greater than a first threshold, and the first threshold is configured by the user.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Acquiring historical alarm data of the vehicle within a first time period; The historical alarm data is analyzed to obtain the alarm path diagram.

7. The method according to claim 6, characterized in that The method further comprises: Second configuration information of a user is received, where the second configuration information is used to indicate the first time period.

8. The method according to claim 6 or 7, characterized in that: Analyzing the historical alarm data to obtain the alarm path diagram includes: Classifying the historical alarm data according to the attributes of the vehicle to obtain multiple data sets; wherein the attributes of the vehicle include at least one of a model, an operation type, a working condition, a mileage, or a version number; The alarm path diagram is constructed based on the multiple data sets.

9. The method according to any one of claims 1 to 8, characterized in that: The method further includes: receiving third configuration information from a user, the third configuration information being used to indicate a second threshold value and / or a target alarm level; The confidence level of each alarm path is greater than the second threshold, and / or the alarm event associated with each alarm path meets the target alarm level.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: Receive fourth configuration information from the user, where the fourth configuration information is used to add or delete an alarm path in the alarm path map.

11. The method according to any one of claims 1 to 10, characterized in that: The information of each alarm path includes at least one of the following: The confidence of each alarm path, the components or component domains associated with each alarm path, or the alarm levels of the at least two alarm events associated with each alarm path, and the components or component domains corresponding to the at least two alarm events associated with each alarm path.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: Outputting first alarm prompt information, wherein the first alarm prompt information is used to indicate that a failure occurs in the first component.

13. The method according to any one of claims 1 to 12, characterized in that: The method further comprises: Get the second alarm event; If the alarm level of the second alarm event is higher than the first level, the second alarm information is output, where the second alarm information is used to indicate that a second component associated with the second alarm event fails.

14. A detection device, characterized in that: include: A processing unit, configured to determine a target alarm path of a first alarm event according to an alarm path diagram of the vehicle; wherein each alarm path in the alarm path diagram is used to describe a trigger relationship between at least two alarm events of the vehicle; The detection unit is used to perform fault detection on the target components associated with the target alarm path, and determine a first component that has a fault among the target components.

15. The device according to claim 14, characterized in that The device also includes an acquisition unit; The acquisition unit is used to acquire the first alarm event; When the processing unit is used to determine the target alarm path of the first alarm event according to the alarm path map of the vehicle, it is specifically used to: determine the target alarm path according to the first alarm event and the alarm path map.

16. The device according to claim 14 or 15, characterized in that The device also includes a receiving unit; The receiving unit is used to receive first configuration information of a user, where the first configuration information is used to indicate a component domain and / or component associated with the first alarm event; The processing unit is used to determine the target alarm path of the first alarm event according to the alarm path map of the vehicle, and is specifically used to: determine the target alarm path in the alarm path map based on the component domain and / or component associated with the first alarm event.

17. The device according to any one of claims 14 to 16, characterized in that: When the target alarm path includes at least two alarm paths, the target component is a component associated with the alarm path of the at least two alarm paths whose confidence meets the first condition.

18. The device according to claim 17, characterized in that The first condition is that the confidence of the alarm path is greater than a first threshold, and the first threshold is configured by the user.

19. The device according to any one of claims 14 to 18, characterized in that: The device also includes an acquisition unit; The acquisition unit is used to acquire the historical alarm data of the vehicle within a first time period; The processing unit is also used to analyze the historical alarm data to obtain the alarm path diagram.

20. The device according to claim 19, characterized in that The device also includes a receiving unit; The receiving unit is used to receive second configuration information of a user, where the second configuration information is used to indicate the first time period.

21. The device according to claim 19 or 20, characterized in that The processing unit is used to analyze the historical alarm data to obtain the alarm path diagram, specifically for: Classifying the historical alarm data according to the attributes of the vehicle to obtain multiple data sets; wherein the attributes of the vehicle include at least one of a model, an operation type, a working condition, a mileage, or a version number; The alarm path diagram is constructed based on the multiple data sets.

22. The device according to any one of claims 14 to 21, characterized in that The device also includes a receiving unit; The receiving unit is used to receive third configuration information of the user, where the third configuration information is used to indicate a second threshold value and / or a target alarm level; The confidence level of each alarm path is greater than the second threshold, and / or the alarm event associated with each alarm path meets the target alarm level.

23. The device according to any one of claims 14 to 22, characterized in that The device also includes a receiving unit; The receiving unit is used to receive fourth configuration information of the user, and the fourth configuration information is used to add or delete an alarm path in the alarm path map.

24. The device according to any one of claims 14 to 23, characterized in that The information of each alarm path includes at least one of the following: The confidence of each alarm path, the components or component domains associated with each alarm path, or the alarm levels of the at least two alarm events associated with each alarm path, and the components or component domains corresponding to the at least two alarm events associated with each alarm path.

25. The device according to any one of claims 14 to 24, characterized in that The device also includes a prompting unit; The prompt unit is used to output first alarm prompt information, where the first alarm prompt information is used to indicate that a failure occurs in the first component.

26. The device according to any one of claims 14 to 25, characterized in that The device also includes an acquisition unit and a prompting unit; The acquisition unit is used to acquire a second alarm event; The prompt unit is further configured to output the second alarm information when the alarm level of the second alarm event is higher than the first level, wherein the second alarm information is configured to indicate that a second component associated with the second alarm event fails.

27. A communication device, characterized in that: The communication device comprises: A communication interface for communicating with other devices; A processor is coupled to the communication interface, so that the communication device executes the method according to any one of claims 1 to 13.

28. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 13.

29. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 13.

30. A chip, characterized in that: The invention comprises a processor, wherein the processor is coupled to a memory and is used to execute a computer program or instruction stored in the memory. When the computer program or instruction is executed, the method according to any one of claims 1 to 13 is implemented, or the method according to any one of claims 14 to 17 is implemented.

31. A vehicle, characterized in that: The method comprises means for implementing the method according to any one of claims 1 to 13.

Images