Function component and method for providing information about a function component error

By implementing a functional component that recognizes and propagates a distinct error code for root errors in a vehicle's networked system, the challenge of identifying the source of multiple error messages is addressed, ensuring efficient and reliable fault analysis.

DE102024101652A1Pending Publication Date: 2025-07-24BAYERISCHE MOTOREN WERKE AG
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
DE102024101652
Authority / Receiving Office
DE · DE
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-01-22
Publication Date
2025-07-24

AI Technical Summary

Technical Problem

In a vehicle system with networked functional components, identifying the root cause of errors is challenging due to the high number of error messages received from individual components, making it difficult to pinpoint the actual source of the issue.

Method used

A functional component is designed to receive an error message from another component, recognize a subsequent error, and send a distinct error code to an error manager, propagating the root error code throughout the system to facilitate efficient and reliable fault analysis.

Benefits of technology

This approach allows for accurate identification of the root cause of errors by propagating a single error code, reducing redundant error messages and enhancing maintenance efficiency and user comfort.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

A functional component for a vehicle is described, comprising a system with a plurality of different functional components, each of which is configured to provide a function in the vehicle. The functional component is configured to receive an error message from a first functional component, wherein the error message indicates a first error code for a first error. The functional component is further configured to detect that the first error leads to a subsequent error of the functional component, and to send an error message to an error manager of the system to inform the error manager of the subsequent error of the functional component, wherein the error message indicates the first error code for the first error.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] The invention relates to a method and a corresponding functional component which are designed to inform an error manager of a system with several networked functional components about an error of a functional component of the system.

[0002] A vehicle typically has a plurality of different functional components, in particular control units, each of which is designed to provide a function within the vehicle. Examples of functional components include sensors, actuators, and / or communication modules. The different functional components can be at least partially interconnected. In particular, a functional component can utilize the functions provided by one or more other functional components to itself provide a function within the vehicle.

[0003] During vehicle operation, the individual functional components typically provide status information to a vehicle fault manager regarding the status of the respective functional component. The status information of a faulty functional component can, in particular, include an error code for a fault in the functional component.

[0004] In a system of interconnected functional components, a failure in one functional component can lead to subsequent failures in a relatively large number of other functional components in the system. As a result, the system's function manager receives a relatively high number of error messages and error codes from the individual functional components in the set of functional components, making it difficult to determine the cause of the error messages.

[0005] This document deals with the technical task of enabling efficient and reliable fault analysis in a system of networked functional components of a vehicle.

[0006] The problem is solved by each of the independent claims. Advantageous embodiments are described, among other things, in the dependent claims. It should be noted that additional features of a patent claim dependent on an independent patent claim can form a separate invention, independent of the combination of all features of the independent patent claim, without the features of the independent patent claim or only in combination with a subset of the features of the independent patent claim, which invention can be made the subject of an independent claim, a divisional application, or a subsequent application. This applies equally to technical teachings described in the description, which can form an invention independent of the features of the independent patent claims.

[0007] According to one aspect, a functional component for a (motor) vehicle is described, wherein the vehicle comprises a system with a plurality of different functional components, wherein the individual functional components are each configured to provide a function in the vehicle. The system can, for example, have 10 or more, or 50 or more, or 100 or more different functional components. The individual functional components can each be a control unit of the vehicle. The functional component of the system described according to the aspect is also referred to in this document as the second functional component.

[0008] The system can be configured such that the (second) functional component provides a function that builds on the functions of one or more (first) functional components of the system. As a result, a failure of a first functional component of the system can lead to a subsequent failure of the (second) functional component and possibly to an impairment of the function provided by the (second) functional component.

[0009] The (second) functional component is configured to receive an error message from a first functional component, wherein the error message specifies a first error code for a first error. As already explained, the (second) functional component can be configured to use the function provided by the first functional component to provide the function of the (second) functional component. The first error can thus lead to a subsequent error of the (second) functional component and possibly to an impairment of the function provided by the (second) functional component.

[0010] The first error may be a fault in the first functional component itself. The original error within the system may thus lie within the first functional component. Alternatively, the first error may be a fault in another functional component of the system that provides a function used by the first functional component. The original error within the system may thus lie within the other functional component of the system.

[0011] The (second) functional component is further configured to detect that the first error leads to a subsequent error of the functional component. The subsequent error can be identified by a second error code that differs from the first error code.

[0012] As already explained, the functional component can be configured to provide a function in the vehicle based on the first function provided by the first functional component. A subsequent error of the first error can be identified as the fact that, due to the first error, the function based on the first function cannot be provided by the vehicle component, or cannot be provided without errors.

[0013] Furthermore, the (second) functional component is configured to send an error message to the system's error manager to inform the error manager of the subsequent error of the functional component. The error message sent to the error manager indicates the first error code for the first error. On the other hand, the error message sent by the (second) functional component to the error manager preferably does not indicate the second error code for the subsequent error of the (second) vehicle component.

[0014] The (second) function provided by the (second) functional component can be used by one or more other functional components of the system. The (second) functional component can be configured to also send the error message to one or more other functional components of the system. The error message sent to the one or more other functional components specifies the first error code for the first error (but preferably not the second error code).

[0015] By propagating the first error code, the error manager is enabled to identify the root cause of error messages in the system in an efficient and reliable manner.

[0016] According to a further aspect, a (road) motor vehicle (in particular a passenger car or a truck or a bus or a motorcycle) is described which comprises one or more of the functional components described in this document.

[0017] In particular, the vehicle may comprise a system with a plurality of different functional components, each configured to provide a function in the vehicle. One or more second functional components (in particular all functional components) of the plurality of different functional components may each be configured as described in this document.

[0018] The system may comprise an error manager, wherein the error manager is configured to receive an error message from a first functional component of the system, which error message indicates a first error code for a first error in the first functional component. The error manager is further configured to receive an error message from each of the one or more second functional components of the system, each of which indicates that the respective second functional component has a second error. The individual error messages from the one or more second functional components nevertheless each indicate the first error code for the first error in the first functional component.

[0019] The error manager can be configured to determine, based on the first error code in the error messages of the first functional component and the one or more second functional components, that the first error is the cause of the second errors of the one or more second functional components. Propagating the first error code through the one or more second functional components thus enables efficient and reliable error analysis.

[0020] Furthermore, the fault manager can be configured to output fault information relating to the first fault via a user interface of the vehicle in response to the determination. On the other hand, fault information relating to the second fault of one or more functional components can be prevented from being output via the user interface of the vehicle. This can increase the quality of maintenance and comfort of the vehicle.

[0021] According to one aspect, a method is provided for providing information relating to a fault of a functional component of a system having a plurality of different functional components, each configured to provide a function in a vehicle. The method comprises receiving, at the functional component, an error message from a first functional component, wherein the error message indicates a first error code for a first fault. Furthermore, the method comprises detecting that the first error leads to a subsequent fault of the functional component, wherein the subsequent fault is identified by a second error code (which is different from the first error code).The method further comprises sending, from the functional component, an error message to an error manager of the system to inform the error manager of the subsequent error of the functional component, wherein the error message indicates the first error code for the first error.

[0022] It should be noted that the aspects described in connection with a functional component, in particular the claims described in connection with a functional component, are also to be applied to the method as corresponding method features.

[0023] According to another aspect, a software (SW) program is described. The SW program can be configured to be executed on a processor (e.g., on a vehicle control unit) and thereby to carry out the method described in this document.

[0024] According to a further aspect, a storage medium is described. The storage medium can comprise a software program configured to be executed on a processor and thereby to carry out the method described in this document.

[0025] It should be noted that the methods, devices, and systems described in this document can be used both alone and in combination with other methods, devices, and systems described in this document. Furthermore, any aspects of the methods, devices, and systems described in this document can be combined in a variety of ways. In particular, the features of the claims can be combined in a variety of ways. Furthermore, features listed in parentheses are to be understood as optional features.

[0026] The invention will be described in more detail below using exemplary embodiments. Fig. 1 an exemplary vehicle with a variety of functional components; Fig. 2 an exemplary system with networked functional components; and Fig. 3 a flowchart of an exemplary method for providing an error message for a fault of a functional component.

[0027] As stated at the beginning, this document is concerned with enabling efficient and reliable fault analysis in a system with networked functional components. In this context, Fig. 1 shows a vehicle 100 with a plurality of different functional components 102, each configured to provide a function in the vehicle 100. Examples of functions include: a sensor function, a communication function, a drive function, a display function, and / or a comfort function. The different functional components 102 can be at least partially interconnected. In particular, individual functional components 102 can be configured to provide their respective functions based on the functions provided by one or more other functional components 102.

[0028] The vehicle 100 further comprises a (central) error manager 101. The individual functional components 102 can each be configured to send status information relating to the status of the respective functional component 102 to the error manager 101. The status information of a functional component 102 can, in particular, include an error message for an error that has occurred in the functional component 102.

[0029] The error manager 101 can be configured to evaluate the status information of the individual functional components 102. If an error message relevant to the use of the vehicle 100 occurs, a corresponding error message can be output to the user of the vehicle 100 via a user interface 104 of the vehicle 100 in order to inform the user accordingly.

[0030] As explained at the beginning, due to the networking of the functional components 102, an error in a specific functional component 102 (which can be referred to, for example, as the source component) can lead to the error manager 101 receiving different error messages from a relatively large number of different functional components 102, wherein the individual error messages each indicate an error in the respective functional component 102. The different error messages can each indicate the error code of the error detected in the respective functional component 102. The error in the source component 102 can thus lead to the error manager 101 receiving a relatively large number of different error codes, from which the actual cause of the error, i.e. the error in the source component 102, cannot be easily determined.

[0031] Fig. 2 shows an exemplary system 200 with networked functional components 102. The system 200 includes a first functional component 211, which provides a specific first function that is utilized by one or more second functional components 212 of the system 200. Each of the one or more second functional components 212 can provide a second function (based on the first function).

[0032] If a (first) error occurs in the first functional component 211, an error message 202 can be sent from the first functional component 211 to the one or more second functional components 212. The error message 202 can be sent to all second functional components 212 of the system 200 that use the first function of the first functional component 211. If necessary, the error message 202 can be sent to all functional components 102, 211, 212 of the system 200. Furthermore, the error message 202 can be sent directly to the error manager 101. The error message 202 of the first functional component 211 can specify the first error code 203 for the first error of the first functional component 211.

[0033] The error message 202 of the first functional component 211 is received by a second functional component 212. Furthermore, the second functional component 212 detects that (due to the first error of the first functional component 211) a second error of the second functional component 212 exists. The second error of the second functional component 212 is identified by a second error code that differs from the first error code for the first error of the first functional component 212.

[0034] The second functional component 212 is configured to send an error message 202 in response to the detected second error of the second functional component 212. The error message 202 can be sent to • the zero, one or more functional components 102 of the system 200 that utilize the second function of the second functional component 212; and / or • all functional components 102, 211, 212 of the system 200; and / or • to the error manager 101.

[0035] The error message 202 of the second functional component 212 indicates (instead of or in addition to the second error code) the first error code 203 of the first error of the first functional component 211 (since the first error led to the second error of the second functional component 212).

[0036] Correspondingly, all second functional components 212 affected by the first error of the first functional component 211 can send an error message 202 indicating the first error code for the first error of the first functional component 211. As a result, the error manager 101 receives different error messages 202 from different functional components 211, 212, each indicating the same (i.e., the first) error code 203, thus providing a direct indication of the common cause of the error messages 202.

[0037] As already explained above, in a system 200 with networked functional components 102, 211, 212, an original error in a first functional component 211 in the system 200 can affect one or more other (second) functional components 212, with the one or more second functional components 212 each triggering its own error response and its own error (with an error message 202). As a result, the error manager 101 of the system 200 receives a multitude of different error messages 202 without being able to directly identify the original error.

[0038] As described in this document, the central error manager 101 can further collect all errors (ie, error messages 202) in the system 200. A first functional component 211, which has a functional limitation, reports the error to all networked (second) functional components 212 using an error message 202. The error message 202 indicates the error code 203 of the error of the first functional component 211.

[0039] If the information, i.e., error message 202, of the original error arrives in a second functional component 212, which reacts to the original error of the first functional component 211, this information is communicated further (and possibly not the respective second functional component's own error). Thus, all functional limitations point (possibly only) to the original error, and the presence of a relatively large number of different error information items at the error manager 101 is avoided.

[0040] The error of the first functional component 211 can thus be propagated to several second functional components 212 (e.g., control units) (e.g., along a chain of functional components 211, 212). If the received error on the receiving component 212 is also responsible for a functional degradation, this received error (i.e., the received error code 203) is forwarded with the degradation information. Thus, the original error propagates to the central error memory of the error manager 101.

[0041] Fig.3 shows a flowchart of a (possibly computer-implemented) method 300 for providing information relating to a fault of a (second) functional component 102, 212 of a system 200 having a plurality of different functional components 102, 211, 212, wherein the individual functional components 102, 211, 212 are each configured to provide a function in a (motor) vehicle 100. The method 300 can be executed by a (second) functional component 102, 212 of the system 200.

[0042] The method 300 includes receiving 301, at the (second) functional component 102, 212, an error message 202 from a first functional component 102, 211, wherein the error message 202 indicates a first error code 203 for an error. The first error code 203 can identify a first error of the first functional component 102, 211. Alternatively, the first error code 203 can identify an error of another functional component 102 of the system 200 that provides a function used by the first functional component 102, 211.

[0043] The error may impair the first function provided by the first functional component 102, 211, which in turn may impair the function of the (second) functional component 102, 212 (provided on the basis of the first function).

[0044] The method 300 includes detecting 302 (by the (second) functional component 102, 212) that the error leads to a subsequent error of the functional component 102, 212. The subsequent error of the (second) functional component 102, 212 may be identified by a second error code (which differs from the first error code 203). The subsequent error may be such that the subsequent error impairs the function provided by the (second) functional component 102, 212.

[0045] Furthermore, the method 300 includes sending 303 an error message 202 from the (second) functional component 102, 212 to the error manager 101 of the system 200 to inform the error manager 101 of the subsequent error (and the functional impairment) of the functional component 102, 212. The error message 202 of the (second) functional component 102, 212 indicates the first error code 203 for the error. Thus, the error manager 101 can be informed efficiently and reliably about the origin or cause of error messages 202 of the system 200.

[0046] The measures described in this document can achieve particularly efficient and reliable error analysis in a system 200 with networked functional components 102, 211, 212.

[0047] The present invention is not limited to the embodiments shown. In particular, it should be noted that the description and figures are intended only to illustrate the principle of the proposed methods, devices, and systems by way of example.

Claims

[1] Functional component (102, 212) for a vehicle (100), comprising a system (200) with a plurality of different functional components (102, 211, 212), each configured to provide a function in the vehicle (100); wherein the functional component (102, 212) is configured, - to receive an error message (202) from a first functional component (102, 211); wherein the error message (202) indicates a first error code (203) for a first error; - to detect that the first error leads to a subsequent error of the functional component (102, 212); wherein the subsequent error is identified by a second error code that differs from the first error code (203); and - sending an error message (202) to an error manager (101) of the system (200) to inform the error manager (101) of the subsequent error of the functional component (102, 212); wherein the error message (202) indicates the first error code (203) for the first error. [2] Functional component (102, 212) according to claim 1, wherein - the first error is an error of the first functional component (211); or - the first error is an error of a further functional component (102) of the system (200) which provides a function which is used by the first functional component (211). [3] Functional component (102, 212) according to one of the preceding claims, wherein the functional component (102, 212) is arranged - on the basis of a first function provided by the first functional component (102, 211), to provide a function in the vehicle (100) based on the first function; and - to recognize as a subsequent error of the first error that, due to the first error, the function based on the first function cannot be provided by the vehicle component (102, 212) or cannot be provided without error. [4] Functional component (102, 212) according to one of the preceding claims, wherein the error message (202) sent by the functional component (102, 212) to the error manager (101) does not indicate the second error code for the subsequent error. [5] Functional component (102, 212) according to one of the preceding claims, wherein the functional component (102, 212) is a control unit of the vehicle (100). [6] Vehicle (100) comprising, - a system (200) having a plurality of different functional components (102, 211, 212), each configured to provide a function in the vehicle (100); and - one or more second functional components (102, 212) of the plurality of different functional components (102, 211, 212) are each designed according to one of the preceding claims. [7] Vehicle (100) according to claim 6, wherein - the system (200) comprises an error manager (101); and - the error manager (101) is set up, - to receive an error message (202) from a first functional component (102, 211) of the system (200) indicating a first error code (203) for a first error of the first functional component (102, 211); and - to receive an error message (202) from each of the one or more second functional components (102, 212) of the system (200), each indicating that the respective second functional component (102, 212) has a second error; wherein the error message (202) of the one or more second functional components (102, 212) each indicates the first error code (203) for the first error of the first functional component (102, 211). [8] Vehicle (100) according to claim 7, wherein the error manager (101) is arranged - to determine, on the basis of the first error code (203) in the error messages (202) of the first functional component (102, 211) and the one or more second functional components (102, 212), that the first error is the cause of the second errors of the one or more second functional components (102, 211); and - in response to determining, - outputting error information relating to the first error via a user interface (104) of the vehicle (100); and / or - to prevent error information relating to the second errors of the one or more functional components (102, 212) from being output via the user interface (104) of the vehicle (100). [9] Method (300) for providing information relating to a fault of a functional component (102, 212) of a system (200) having a plurality of different functional components (102, 211, 212), each configured to provide a function in a vehicle (100); wherein the method (300) comprises - receiving (301), at the functional component (102, 212), an error message (202) from a first functional component (102, 211); wherein the error message (202) indicates a first error code (203) for a first error; - detecting (302) that the first error leads to a subsequent error of the functional component (102, 212); wherein the subsequent error is identified by a second error code; and - sending (303) from the functional component (102, 212) an error message (202) to an error manager (101) of the system (200) to inform the error manager (101) of the subsequent error of the functional component (102, 212); wherein the error message (202) indicates the first error code (203) for the first error.

Citation Information

Patent Citations

  • Troubleshooting in a system

    DE102018200429A1