System and method for dynamically improving a vehicle diagnostic system

Abstract

The invention comprises a system and a method for simply and dynamically improving a vehicle diagnostic system in a vehicle. The system comprises at least one vehicle. The vehicle comprises an input unit arranged for receiving an input regarding a vehicle malfunction, a control unit arranged for creating a snapshot of electrical and / or electronic vehicle components after receiving the input via the input unit. The vehicle comprises a feedback unit arranged for collecting feedback regarding the vehicle malfunction, wherein collecting the feedback comprises dividing the feedback into a predetermined problem description structure, the feedback unit is arranged for processing the feedback and deriving a severity of the problem from the feedback, integrating the collected feedback into the snapshot. The vehicle comprises a communication unit arranged for forwarding the created snapshot to a backend.

Description

Technical Field

[0001] This invention relates to a system and method for dynamically improving vehicle diagnostic systems. Background Technology

[0002] Vehicle diagnostic systems are known. This involves systems that can include a wide range of technical methods and applications to accurately assign diagnostic results to faults in electrical and electronic components of a vehicle during fault analysis. A drawback of such diagnostic systems is that faults in electrical and electronic components are described using functions and are only identified when they exceed predetermined or predefined threshold ranges. Each fault is assigned a specific fault code, error code, or diagnostic fault code (DTC). Another drawback is that only known faults assigned specific fault codes are identified. This can lead to situations where a customer notices disturbances in the vehicle, but these disturbances are not identified as faults by the vehicle diagnostic system because the threshold is not exceeded and / or the fault is not identified as a fault due to the absence of a corresponding fault code. Summary of the Invention

[0003] The objective of this invention is to provide a solution that enables better dynamic detection of faults in vehicles and thus improves vehicle diagnostic systems.

[0004] According to the present invention, this task is solved by the features of the present invention.

[0005] The aforementioned task is solved by a system for simply and dynamically improving a vehicle diagnostic system, the system comprising at least one vehicle, wherein the vehicle includes:

[0006] An input unit configured to receive input regarding vehicle malfunctions;

[0007] A control unit configured to create a snapshot of electrical and / or electronic vehicle components upon receiving input via an input unit; and

[0008] A communication unit is configured to transmit the created snapshot to the backend.

[0009] The system includes at least one vehicle. The term "vehicle" within the scope of this document includes a moving means of transport used for transporting people (passenger transport), goods (freight transport), or tools (machinery or auxiliary equipment). The term "vehicle" particularly includes motor vehicles and motor vehicles that can be at least partially electrically driven (electric vehicles, hybrid vehicles).

[0010] The vehicle can be controlled by a driver. Alternatively, the vehicle can be at least semi-autonomous. The terms "autonomous driving vehicle" or "autonomous driving" within the scope of this document can be understood as driving with automatic longitudinal or lateral guidance, or autonomous driving with automatic longitudinal and lateral guidance. Automated driving can, for example, involve extended driving on highways or limited driving within a stopped or queued area. The term "autonomous driving" includes automated driving with any level of automation. Exemplary levels of automation are assisted, semi-autonomous, highly automated, or fully automated driving. Such levels of automation are defined by the German Federal Highway Research Institute (BASt) (see BASt publication *Forschung kompakt*, 2012 / Issue 11). In assisted driving, the driver continuously provides longitudinal or lateral guidance, and the system accordingly takes over other functions to a certain extent. In semi-autonomous driving, the system takes over longitudinal and lateral guidance for a certain period of time and / or under special circumstances, wherein the driver must continuously monitor the system as in assisted driving. In highly automated driving, the system takes over longitudinal and lateral guidance for a certain period of time, and the driver does not need to continuously monitor the system; however, the driver must be capable of taking over vehicle guidance for a certain period of time. In fully automated driving, the system can automatically complete driving in all situations for specific application scenarios; for such applications, a driver is no longer needed. The aforementioned four levels of automation correspond to SAE-Level 1 to 4 of the standard SAE J3016 (SAE: Society of Automotive Engineers). In addition, SAE-Level 5 is defined in SAE J3016 as the highest level of automation, which is not included in the definition of BASt. SAE-Level 5 corresponds to driverless driving, where the system can automatically handle all situations throughout the driving process, just like a human driver.

[0011] The vehicle includes an input unit. The input unit may be, for example, part of the vehicle's infotainment system. The input unit can be operated via voice and / or touch and / or button operation and / or any other feasible operation method. The input unit is configured to receive input regarding vehicle malfunctions. For example, when a vehicle malfunction is identified concerning the vehicle's electronic and / or electrical components, the vehicle user can input information about the malfunction via the input unit. This can be done in a very comfortable manner. For example, an application or app pre-installed in the vehicle can be provided, allowing the identified vehicle malfunction to be input via voice input and / or touch input via a touchscreen and / or other suitable input methods.

[0012] The vehicle includes a control unit. The control unit is configured to create a snapshot of the electrical and / or electronic vehicle components after receiving input about a vehicle malfunction via an input unit. The snapshot can be a suitable data structure and can include the current state of the electrical and / or electronic vehicle components at the point in time when the input about the vehicle malfunction is received via the input unit. This is particularly advantageous because the vehicle user may not have information about the electrical and / or electronic components responsible for the discovered vehicle malfunction. Therefore, creating a snapshot of all electrical and / or electronic vehicle components at the point in time the vehicle user discovers the malfunction allows for analysis of this snapshot in subsequent processes. The vehicle's electrical and / or electronic components can include the entire vehicle or automotive electronics, i.e., the entire area of ​​electronics within the vehicle. These can include all controllers distributed throughout the vehicle. Controllers can include those associated with the vehicle's instrument cluster, motor control, driver assistance systems, airbag systems, alarm devices, multimedia systems, etc.

[0013] The vehicle includes a feedback unit. The feedback unit is configured to collect feedback regarding vehicle malfunctions; wherein collecting feedback includes categorizing the feedback into a predetermined problem description structure; wherein the feedback unit is configured to process the feedback and deduce the severity of the problem from the feedback; and wherein the collected feedback is integrated into a snapshot.

[0014] Furthermore, the vehicle may include a feedback unit or feedback module. The feedback unit is configured to collect further information or data about vehicle malfunctions by the vehicle's user or driver. For example, a predefined session can be executed via input / output units in the vehicle, such as the vehicle's infotainment system. Therefore, further disturbances regarding the detected vehicle malfunction, particularly those perceived by the vehicle's user or driver, can be detected. Feedback collected by the feedback unit, or feedback data collected by the feedback unit, can be integrated into a snapshot.

[0015] The feedback unit may include, for example, a voice conversation system to provide feedback from the vehicle user or driver regarding perceived disturbances related to a perceived vehicle malfunction. Within the scope of this document, a voice conversation system is a system through which a person can converse in natural language and thus use natural language as an input and / or output medium. Collecting feedback through a voice conversation system that may be part of the vehicle's infotainment system is particularly advantageous because feedback can be obtained without the vehicle user or driver needing to use operating elements to input feedback. This avoids distracting the vehicle user or driver from road traffic. Alternatively, the feedback unit may include an input and output unit that may be part of the vehicle's infotainment system. Here, feedback regarding vehicle malfunctions may be collected via a window, for example, through touch input, input via operating elements, etc.

[0016] Collecting feedback may involve dividing the feedback into predetermined or predictable problem description structures. A problem description structure may include one or more of the following elements:

[0017] - The location or vehicle part where the problem was discovered, such as the brakes, transmission, etc.;

[0018] - Signs or clues about the problem, such as smoke, noise, etc.;

[0019] - The situation or condition in which the problem occurs, such as when the motor / engine starts, during braking, etc.;

[0020] - Frequency of the problem.

[0021] The feedback unit can deduce the severity or degree of the problem from the processing of the feedback, where the severity can be classified into different areas, such as when the health of vehicle occupants and / or other traffic participants is threatened, then it is serious, or when it involves interference with traffic condition information in the vehicle's navigation module, then it is minor.

[0022] Examples of vehicle users or drivers providing feedback on traffic conditions via a voice conversation system when problems occur include:

[0023] - "There is a section of road closure that has not yet been announced";

[0024] - "Why isn't this road closure showing up?"

[0025] - "Why isn't this incident being shown?"

[0026] - "Why didn't you foresee this accident?"; etc.

[0027] Examples of vehicle users or drivers providing feedback on mechanical problems via a voice conversation system include:

[0028] - "It makes a strange noise every time I start the car";

[0029] - "I hear a strange noise every time I start the motor / engine";

[0030] - "Every time I park, the motor / engine makes a knocking noise";

[0031] - "Every time I turn off the motor / engine, it makes a knocking noise";

[0032] - "The motor / engine sometimes makes a panting noise while driving"; etc.

[0033] Therefore, the feedback unit can deduce the following conclusion from the feedback "Whenever I turn off the motor / engine, the motor / engine emits knocking noise":

[0034] - Location or vehicle component where the problem was discovered: motor / engine;

[0035] - Signs or clues about the problem: knocking noise;

[0036] - The problem occurs when the motor / engine stops;

[0037] - Frequency of the problem: Every time the motor / engine stops;

[0038] - Severity of the problem: Moderately serious problem, you should go to the workshop immediately.

[0039] Similar to the previous example, the problem description input via other feasible input schemes can also be categorized through the feedback unit.

[0040] Therefore, in addition to technical condition data of the vehicle's electrical and / or electronic components, it is advantageous to detect interferences related to vehicle malfunctions detected by the vehicle's user or driver, integrate these interferences into a snapshot, and then transmit them to the backend for possible fault diagnosis. The user's or driver's detection of vehicle malfunctions offers a significant advantage over conventional vehicle diagnostic systems in identifying vehicle malfunctions and / or their causes. By classifying feedback via a feedback unit, a unified data structure describing the problem can be implemented and transmitted to the backend for possible fault diagnosis. Therefore, snapshots and feedback can be advantageously merged or integrated into a unified overall data structure.

[0041] The system includes a backend. The backend may include at least one backend server and / or part of a cloud computing or IT infrastructure that provides storage, computing power, and / or application software as a service (service provider) via the Internet.

[0042] The vehicle includes a communication unit. This communication unit can be a unit located within the vehicle, configured to establish communication connections with other communication participants, such as backend and / or mobile terminals. The communication unit may include a participant identity module, a user identity module, or a SIM card, used to establish communication connections via a mobile radio system. The participant identity module explicitly identifies the communication unit within the mobile radio network. Communication connections may involve data connections (e.g., packet switching) and / or wired communication connections (e.g., line switching). Communication can be performed according to the cellular Vehicle To X (C-V2X) paradigm based on LTE version 14, 4G, and / or 5G standards. Furthermore, the communication unit can communicate via other radio interfaces, such as WLAN, independent of the availability of the mobile radio network or the sufficient capacity of currently available mobile radio networks. For this purpose, IST-G5 or IEEE 802.11p can be used in vehicle-to-vehicle (V2V) communication. Thus, the vehicle can receive data from other communication participants or forward data to other communication participants through the communication unit.

[0043] The communication unit is configured to relay the created snapshots to the backend.

[0044] Therefore, data regarding vehicle malfunctions identified or detected by vehicle users can advantageously be detected and relayed to the backend for further fault detection or handling, regardless of defined or undefined fault codes for one or more electronic or electrical vehicle components and regardless of whether the threshold required for the defined fault code has been exceeded. This can significantly improve known vehicle diagnostic systems, as fault conditions are often undetectable by these systems, even if the vehicle user notices the fault or fault condition. This, in particular, enhances the safety of all road users.

[0045] Snapshots of electrical and / or electronic vehicle components preferably include:

[0046] - The current state of all electrical and / or electronic vehicle components; and / or

[0047] - The vehicle identification number; and / or

[0048] - Vehicle battery status; and / or

[0049] - Vehicle maintenance schedule; and / or

[0050] - The vehicle's geographical location; and / or

[0051] - The vehicle's current environmental conditions; and / or

[0052] - The vehicle's current mileage; and / or

[0053] - Feedback regarding vehicle malfunctions; and / or

[0054] - Receive the timestamp of the input time point through the input unit; and / or

[0055] - Software versions installed and running in a vehicle or in its electrical and / or electronic vehicle components.

[0056] The current state of all electrical and / or electronic vehicle components, especially the current state of these vehicle components at the point in time when the input is received.

[0057] The vehicle identification number (VIN) of a vehicle can be used to identify the associated vehicle, for example, when further processing a snapshot by the back end and / or by service personnel.

[0058] The vehicle's geographical location can be determined, for example, through a location determination unit on the vehicle side. The location determination unit can be configured to determine or collect the vehicle's current location data using a navigation satellite system. The navigation satellite system can refer to any common or future Global Navigation Satellite System (GNSS) used to determine location and navigation by receiving signals from navigation satellites and / or pseudo-satellites. Examples include the Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Galileo positioning system, and / or BeiDou navigation satellite system. In the GPS example, the location determination unit may include a GPS module configured to determine the vehicle's current GPS location data at a time point input via an input unit.

[0059] Current environmental conditions may include, for example, the current outside temperature, current weather conditions, road conditions, etc. These can be detected at the time point input by the input unit and integrated into the snapshot in a manner known by existing technology using appropriate sensors (e.g., temperature sensors, rain sensors, external cameras, etc.).

[0060] The backend is preferably configured to evaluate the received snapshots. Appropriate machine learning algorithms can be used to evaluate the received snapshots through the backend. Models created using machine learning methods, such as supervised or unsupervised learning, for a large number of vehicles, can, for example, identify one or more electronic and / or electrical components responsible for a vehicle malfunction from the received snapshots. Alternatively, if the specific electronic and / or electrical component responsible for the malfunction cannot be identified, the snapshot can be forwarded to service personnel or remote assistance personnel. These personnel can then contact the vehicle's user to obtain further information about the malfunction and / or suggest a service date. Alternatively, workshop and / or problem management teams can also use the snapshot data to identify solutions to problems. External service personnel can also benefit from the snapshots. This allows for timely and individual handling of vehicle malfunctions and establishes direct communication channels with vehicle users. By accumulating the collected snapshots in the backend—for example, using appropriate algorithms—patterns can be identified, thereby enabling technological improvements for a large number of vehicles. This creates the possibility that, among the identified vehicle malfunctions, other vehicles potentially related to the identified malfunctions can be identified, in which the malfunctions can be eliminated, for example, through targeted software updates.

[0061] According to the second aspect, the fundamental task is also addressed through a method for simply and dynamically improving vehicle diagnostic systems, which includes:

[0062] The vehicle receives input about vehicle malfunctions through its input unit.

[0063] Create snapshots of electrical and / or electronic vehicle components through the vehicle's control unit;

[0064] Feedback on vehicle malfunctions is collected through the vehicle's feedback unit;

[0065] The collection of feedback includes dividing the feedback into a predetermined problem description structure;

[0066] The feedback unit is configured to process feedback and deduce the severity of the problem from the feedback.

[0067] Integrate the collected feedback into the snapshot; and

[0068] The created snapshot is transmitted to the backend via the vehicle's communication unit.

[0069] Snapshots of electrical and / or electronic vehicle components preferably include:

[0070] - The current state of all electrical and / or electronic vehicle components; and / or

[0071] - The vehicle identification number; and / or

[0072] - Vehicle battery status; and / or

[0073] - Vehicle maintenance schedule; and / or

[0074] - The vehicle's geographical location; and / or

[0075] - The vehicle's current environmental conditions; and / or

[0076] - The vehicle's current mileage; and / or

[0077] - Feedback regarding vehicle malfunctions; and / or

[0078] - Receive the timestamp of the input time point through the input unit; and / or

[0079] - Software versions installed and running in a vehicle or in its electrical and / or electronic vehicle components.

[0080] Backend optimization settings are used to evaluate the received snapshots.

[0081] These and other tasks, features, and advantages of the present invention will become clear from the following detailed description of the preferred embodiments and the accompanying drawings. It will be apparent that, although the embodiments are described separately, the various features of the embodiments can be combined to form additional embodiments. Attached Figure Description

[0082] Figure 1 This schematically illustrates a system for simply and dynamically improving vehicle diagnostic systems;

[0083] Figure 2 An exemplary method for simply and dynamically improving a vehicle diagnostic system is shown;

[0084] Figure 3 An exemplary snapshot is shown;

[0085] Figure 4 An example is shown showing the input and feedback regarding vehicle malfunctions. Detailed Implementation

[0086] Figure 1 A system 100 for simply and dynamically improving a vehicle diagnostic system in a vehicle 110 is schematically shown.

[0087] System 100 includes at least one vehicle 110. Vehicle 110 includes an input unit 112. Input unit 112 may be, for example, part of the infotainment system of vehicle 110. Input unit 112 may be operated by means of voice operation and / or touch operation and / or button operation and / or any other feasible operation scheme. Input unit 112 is configured to receive input regarding vehicle malfunctions. A user of vehicle 110 may, for example, input information about a vehicle malfunction related to electronic and / or electrical components of vehicle 110 via input unit 112. This can be done in a very comfortable manner. For example, an application or app pre-installed in the vehicle may be provided, by means of which the identified vehicle malfunction can be input via voice input and / or touch input via a touchscreen and / or other suitable input.

[0088] Vehicle 110 includes a control unit 114. Control unit 114 is configured to create a snapshot 300 of the electrical and / or electronic vehicle components after receiving input about a vehicle malfunction via input unit 112. Snapshot 300 may be a suitable data structure and includes the current state of the electrical and / or electronic vehicle components at the point in time when input about the vehicle malfunction is received via input unit 112. This is advantageous because the user of vehicle 110 may not have information about the electrical and / or electronic components responsible for the discovered vehicle malfunction. Therefore, creating a snapshot 300 of all electrical and / or electronic vehicle components at the point in time when the user of vehicle 110 discovers the vehicle malfunction allows for analysis in a later process. The electrical and / or electronic components of vehicle 110 may include all vehicle or automotive electronics, i.e., the entire area of ​​electronics within vehicle 110. These electrical and / or electronic components may include all controllers distributed throughout vehicle 110. The controller may include controllers related to the instrument cluster in vehicle 110, motor control in vehicle 110, driver assistance systems in vehicle 110, airbag systems in vehicle 110, alarm devices in vehicle 110, and multimedia systems in vehicle 110.

[0089] In addition, vehicle 110 may include a feedback unit 118. Feedback unit 118 is configured to collect further information or data about vehicle malfunctions from the user or driver of vehicle 110, as referenced below. Figure 4As explained in more detail, predefined sessions can be executed, for example, through the input and output unit 112 in vehicle 110, such as the infotainment system of vehicle 110. Therefore, further interference regarding the detected vehicle malfunction can be detected—particularly by the user of vehicle 110 or the driver. Feedback collected through feedback unit 118, or feedback data collected through the feedback unit, can be integrated into snapshot 300.

[0090] Feedback unit 118 may include, for example, a voice conversation system to collect feedback from the user or driver of vehicle 110 regarding perceived disturbances related to a perceived vehicle malfunction. A voice conversation system, within the scope of this document, is a system through which a person can converse in natural language and thus use natural language as an input and / or output medium. Collecting feedback via a voice conversation system—which may be part of the infotainment system of vehicle 110—is particularly advantageous because feedback can be obtained without the user or driver needing to use operating elements to input feedback. This avoids distracting the user or driver from road traffic. Alternatively, feedback unit 118 may include an input and output unit, which may be part of the infotainment system of vehicle 110. Here, feedback regarding vehicle malfunctions may be collected via a window, for example, through touch input, input via operating elements, etc.

[0091] The collection of feedback may include dividing the feedback into predetermined or predictable problem description structures through feedback unit 118. The problem description structure may include one or more of the following elements:

[0092] - The location or vehicle part where the problem was discovered, such as the brakes, transmission, etc.;

[0093] - Signs or clues about the problem, such as smoke, noise, etc.;

[0094] - The situation or condition in which the problem occurs, such as when the motor starts or during braking;

[0095] - Frequency of the problem.

[0096] Feedback unit 118 can deduce the severity or degree of the problem from the processing of feedback, wherein the severity can be classified into different areas, such as serious when the health of vehicle occupants and / or other traffic participants is threatened, or minor when it involves interference with traffic condition information in the navigation module of vehicle 110.

[0097] Examples of how users or drivers of vehicle 110 can provide feedback on traffic conditions via a voice chat system when problems occur include:

[0098] - "There is a road closure that has not yet been displayed";

[0099] - "Why isn't this road closure showing up?"

[0100] - "Why isn't this incident being shown?"

[0101] - "Why didn't you foresee this accident?"; etc.

[0102] Examples of feedback on mechanical problems provided by the user or driver of vehicle 110 via a voice conversation system include:

[0103] - "It makes a strange noise every time I start the car";

[0104] - "I hear a strange noise every time I start the motor / engine";

[0105] - "The motor makes a knocking noise every time I park."

[0106] - "Every time I turn off the motor, it makes a knocking noise."

[0107] - "The motor sometimes makes a panting noise while running"; etc.

[0108] Therefore, the feedback unit 118 can derive the following conclusion from the feedback "The motor makes a knocking noise whenever I turn it off":

[0109] - Location or vehicle component where the problem was discovered: motor;

[0110] - Signs or clues about the problem: knocking noise;

[0111] - The problem occurs when the motor stops;

[0112] - Frequency of the problem: Every time the motor stops;

[0113] - Severity of the problem: Moderately serious problem, you should go to the workshop immediately.

[0114] Similar to the previous example, the problem description input via other feasible input schemes can also be classified through the feedback unit 118.

[0115] Therefore, in addition to the technical condition data of the electrical and / or electronic components of vehicle 110, interferences concerning vehicle malfunctions detected by the user or driver of vehicle 110 can be advantageously detected and integrated into snapshot 300 and subsequently transmitted to backend 120 (see below) for possible fault diagnosis. The user's or driver's detection of vehicle malfunctions offers significant advantages over conventional vehicle diagnostic systems in identifying vehicle malfunctions and / or their causes. By classifying the feedback via feedback unit 118, a unified data structure describing the problem can be implemented and transmitted to backend 120 for possible fault diagnosis. Therefore, snapshot 300 and feedback can advantageously be merged or integrated into a unified overall data structure.

[0116] Snapshot 300 of electrical and / or electronic vehicle components may include:

[0117] - The current status of all electrical and / or electronic vehicle components 301; and / or

[0118] - Vehicle Identification Number (VIN) 302 for vehicle 110; and / or

[0119] - Battery status 303 for vehicle 110; and / or

[0120] - Maintenance procedure 304 for vehicle 110; and / or

[0121] - The geographic location of vehicle 110 is 305; and / or

[0122] - The current environmental conditions of vehicle 110 306; and / or

[0123] - The current mileage of vehicle 110 is 307; and / or

[0124] - Feedback regarding vehicle malfunctions via 308; and / or

[0125] - The timestamp 309 of the time point of receiving input via the input unit 112 of vehicle 110; and / or

[0126] - Software version 310 installed and running in vehicle 110 or in the vehicle's electrical and / or electronic components.

[0127] The current state of all electrical and / or electronic vehicle components 301 includes, in particular, the current state of these vehicle components at the point in time when input about a vehicle malfunction is received.

[0128] The vehicle identification number or vehicle identification number (VIN) 302 of vehicle 110 can be used to identify the associated vehicle, for example, when further processing the snapshot by backend 120 and / or by service personnel.

[0129] The geographic location 305 of vehicle 110 can be determined, for example, by a vehicle-side location determination unit (not shown). The location determination unit can be configured to determine or detect the vehicle's current location data using a navigation satellite system. The navigation satellite system can refer to any common and future Global Navigation Satellite System (GNSS) used to determine location and navigation by receiving signals from navigation satellites and / or pseudo-satellites. Examples include the Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Galileo positioning system, and / or BeiDou navigation satellite system. In the GPS example, the location determination unit may include a GPS module configured to determine the vehicle 110's current GPS location data at the time point input via input unit 112.

[0130] The current environmental conditions 306 may include, for example, the current external temperature, current weather conditions, road conditions, etc. These can be detected at the time point input through the input unit 112 and integrated into the snapshot 300 in a manner known in the prior art using suitable sensors (e.g., temperature sensors, rain sensors, external cameras, etc.).

[0131] An exemplary snapshot 300 is further referenced below. Figure 3 To explain in more detail.

[0132] System 100 includes backend 120. Backend 120 may include at least one backend server and / or part of a cloud computing or IT infrastructure that provides storage, computing power and / or application software as a service (service provider) via the Internet.

[0133] Vehicle 110 includes a communication unit 116. The communication unit 116 may be a communication unit disposed within vehicle 110, configured to establish a communication connection with other communication participants, such as backend 120 and / or mobile terminals. The communication unit 116 may include a participant identity module or user identity module or SIM card, configured to establish a communication connection via a mobile radio system. The participant identity module explicitly identifies the communication unit 116 within the mobile radio network. The communication connection may involve data connections (e.g., packet switching) and / or wired communication connections (e.g., line switching). Communication may be conducted according to the Vehicle To X (C-V2X) paradigm based on LTE standard version 14, 4G standards, and / or 5G standards. Furthermore, the communication unit 116 may communicate via other radio interfaces, such as WLAN, independent of the availability of the mobile radio network or sufficient capacity of currently available mobile radio networks. For this purpose, IST-G5 or IEEE 802.11p may be used in vehicle-to-vehicle (V2V) communication. Therefore, the vehicle can receive data from other communication participants or transmit data to other communication participants through the communication unit 116.

[0134] The communication unit 116 is configured to transmit the created snapshot to the backend 120.

[0135] Therefore, data regarding vehicle faults identified or detected by the user of vehicle 110 can advantageously be detected and relayed to backend 120 for further fault detection or handling, regardless of defined or undefined fault codes for one or more electronic or electrical vehicle components and regardless of whether the threshold required for a defined fault code has been exceeded. This can significantly improve known vehicle diagnostic systems, as fault conditions are often undetectable by these systems, even if the vehicle user detects the fault or fault condition. This, in particular, improves the safety of all road users.

[0136] Backend 120 can be configured to evaluate the received snapshots.

[0137] The received snapshots can be evaluated at the backend 120 using appropriate machine learning algorithms. A model of a large number of vehicles 110, created using machine learning methods, such as supervised or unsupervised learning, can, for example, identify one or more electronic and / or electrical components responsible for a vehicle malfunction from the received snapshots 300. Alternatively, if the specific electronic and / or electrical component responsible for the malfunction cannot be identified, the snapshot 300 can be relayed to service personnel or remote assistance personnel. These personnel can then contact the user of the vehicle 110 to obtain further information about the malfunction and / or suggest service dates for the vehicle 110. Alternatively, the workshop and / or problem management team can also use the snapshot data to identify solutions to problems. External service personnel can also benefit from the snapshots. This allows for timely and individual handling of vehicle malfunctions and establishes direct communication channels with the users of the vehicle 110. By accumulating the collected snapshots at the backend 120, patterns can be identified, for example, using appropriate algorithms, thereby enabling the potential for technological improvements to a large number of vehicles 110. This creates the possibility that, among the identified vehicle malfunctions, other vehicles 110 potentially related to the identified malfunctions can be identified, for example, by eliminating the malfunctions through targeted software updates.

[0138] Figure 2 A method 200 for simply and dynamically improving a vehicle diagnostic system is shown, which can be implemented by, as referenced... Figure 1 The system described is implemented 100%.

[0139] The method 200 includes:

[0140] The vehicle 110 receives input from 210 regarding vehicle malfunctions via its input unit 112;

[0141] A snapshot 300 of electrical and / or electronic vehicle components is created by the control unit 114 of vehicle 110;

[0142] Feedback on vehicle malfunctions is collected by the feedback unit 118 of vehicle 119;

[0143] The collection of feedback includes dividing the feedback into a predetermined problem description structure;

[0144] The feedback unit 118 is configured to process feedback and deduce the severity of the problem from the feedback.

[0145] The collected feedback is integrated into snapshot 300 from 250; and

[0146] The created snapshot 300 is relayed to the backend 120 via the communication unit 116 of vehicle 110.

[0147] Snapshot 300 of electrical and / or electronic vehicle components may include:

[0148] - The current status of all electrical and / or electronic vehicle components 301; and / or

[0149] - Vehicle Identification Number 302 for vehicle 110; and / or

[0150] - Battery status 303 for vehicle 110; and / or

[0151] - Maintenance procedure 304 for vehicle 110; and / or

[0152] - The geographic location of vehicle 110 is 305; and / or

[0153] - The current environmental conditions of vehicle 110 306; and / or

[0154] - The current mileage of vehicle 110 is 307; and / or

[0155] - Feedback regarding vehicle malfunctions via 308; and / or

[0156] - Receive the timestamp 309 of the input time point via input unit 112; and / or

[0157] - Software version 310 installed and running in vehicle 110 or in the electrical and / or electronic vehicle components of vehicle 110.

[0158] Backend 120 can be configured to evaluate the received snapshot 300.

[0159] Figure 3 As shown in the reference Figure 1 and 2 The exemplary snapshot 300 is as described.

[0160] An exemplary snapshot 300 includes the current state 30 of all electrical and / or electronic vehicle components, the vehicle identification number 302 of vehicle 110, the battery state of vehicle 110, the maintenance process of vehicle 110, the geographical location of vehicle 110, the current environmental conditions of vehicle 110, the current mileage of vehicle 110, feedback on vehicle malfunctions, timestamps of the time points when inputs are received via input unit 112, and software versions 310 installed and running in vehicle 110 or in the electrical and / or electronic vehicle components of vehicle 110.

[0161] Snapshot 300 is stored in storage unit 320 along with additional (problematic) snapshots of vehicle 110 and / or a number of other vehicles. Backend 120 may include storage unit 320 or access that storage unit for purposes such as referenced. Figure 1 The one or more snapshots described herein shall be processed in the manner described.

[0162] Figure 4 For reference Figure 1 and 2 The example illustrates inputs and feedback regarding vehicle malfunctions, as described above. The collected feedback can be obtained through methods such as those described in the reference. Figure 1 The feedback unit 118 described above is categorized and integrated with snapshot 300 into a unique, unified data structure.

[0163] Window 410 shows the input and output unit 112 of vehicle 110, which may be part of the vehicle's infotainment system. Window 420 shows an area where apps pre-installed in vehicle 110 are displayed via input and output unit 112. These apps include App 411, which is used as described in reference... Figure 1 Enter information about vehicle malfunctions as described.

[0164] After activating App 411 via input such as voice input, touch input, or via the operating unit, window 412 opens. Snapshot 300 is created by activating the possible input 412 to "register it" (through one of the aforementioned suitable input options). This allows for notifying the vehicle user of vehicle malfunctions in a particularly quick, efficient, and uncomplicated manner.

[0165] The feedback unit 118 is activated by activating possible input 413 "Provide more details" or "Provide more details" (one of the aforementioned suitable input options), so as to refer to Figure 1 As described, collect feedback on vehicle malfunctions. In this case, inquire for further information, initially asking where the problem occurs on the vehicle. Feedback collection can be expanded in a flexible manner.

Claims

1. A system (100) for simply and dynamically improving a vehicle diagnostic system, the system comprising at least one vehicle (110), wherein, The vehicle (110) includes: An input unit (112) is configured to receive input regarding vehicle malfunctions; Control unit (114), the control unit is configured to create a snapshot (300) of electrical and / or electronic vehicle components after receiving input via input unit (112). Feedback unit (118), wherein the feedback unit is configured to collect feedback on vehicle malfunctions; The collection of feedback includes dividing the feedback into a predetermined problem description structure; The feedback unit (118) is configured to process feedback and deduce the severity of the problem from the feedback; and The collected feedback is integrated into a snapshot (300); and A communication unit (116) is configured to transmit the created snapshot (300) to the backend (120). The snapshot (300) of the electrical and / or electronic vehicle components includes: - The vehicle identification number (302) of the vehicle (110); and / or - The battery status (303) of the vehicle (110); and / or - The maintenance process (304) of the vehicle (110); and / or - The geographic location (305) of the vehicle (110); and / or - The current mileage (307) of the vehicle (110); and / or - Software version (310) installed and running in the vehicle (110) or in the electrical and / or electronic vehicle components of the vehicle (110). The problem description structure includes the following elements: - The location or vehicle part where the problem was discovered; - The situation or conditions under which the problem occurred; - Frequency of the problem.

2. The system (100) according to claim 1, wherein, A snapshot (300) of the electrical and / or electronic vehicle components includes: - The current state of all electrical and / or electronic vehicle components (301); and / or - The current environmental conditions (306) of the vehicle (110); and / or - Feedback regarding vehicle malfunctions (308); and / or - The timestamp (309) of the input time point is received via the input unit (112).

3. The system (100) according to claim 1 or 2, wherein, The backend (120) is configured to evaluate the received snapshot (300).

4. A method (200) for simply and dynamically improving a vehicle diagnostic system, the method comprising: The vehicle (110) receives (210) input regarding vehicle malfunctions via its input unit (112); Create (220) a snapshot (300) of electrical and / or electronic vehicle components via the control unit (114) of the vehicle (110). Feedback on vehicle malfunctions is collected (240) via the feedback unit (118) of the vehicle (110); The collection of feedback includes dividing the feedback into a predetermined problem description structure; The feedback unit (118) is configured to process feedback and deduce the severity of the problem from the feedback. The collected feedback is integrated (250) into a snapshot (300); and The created snapshot (300) is transmitted (230) to the backend (120) via the communication unit (116) of the vehicle (110). The snapshot (300) of the electrical and / or electronic vehicle components includes: - The vehicle identification number (302) of the vehicle (110); and / or - The battery status (303) of the vehicle (110); and / or - The maintenance process (304) of the vehicle (110); and / or - The geographic location (305) of the vehicle (110); and / or - The current mileage (307) of the vehicle (110); and / or - Software version (310) installed and running in the vehicle (110) or in the electrical and / or electronic vehicle components of the vehicle (110). The problem description structure includes the following elements: - The location or vehicle part where the problem was discovered; - The situation or conditions under which the problem occurred; - Frequency of the problem.

5. The method (200) according to claim 4, wherein, A snapshot (300) of the electrical and / or electronic vehicle components includes: - The current state of all electrical and / or electronic vehicle components (301); and / or - The current environmental conditions (306) of the vehicle (110); and / or - Feedback regarding vehicle malfunctions (308); and / or - The timestamp (309) of the input time point is received via the input unit (112).

6. The method (200) according to claim 4 or 5, wherein, The backend (120) is configured to evaluate the received snapshot (300).

Images