Computer-implemented method for verifying OBD compliance, computer program and / or computer-readable medium, data processing device

Abstract

A computer-implemented method (100) for verifying the OBD compliance (85) of messages (65) of a bus system (55) of a vehicle (50) with a vehicle diagnostic system (56), wherein the vehicle (50) has a first vehicle component (60) and a second vehicle component (61), and the bus system (55) connects the first vehicle component (60) as a sender (62) of a message (65) and the second vehicle component (61) as a receiver (63) of the message (65), wherein the method (100) comprises: - capturing (110) a technical message catalog (70) relating to the messages (65) together with a receiver relevance (71) relating to one of the messages (65) and a sender compliance (72) relating to the messages (65); - determining (120) a consistency measure (80) relating to one of the messages (65) based on the respective receiver relevance (71) relating to the message (65) and Transmitter compliance (72);and output (130) of the consistency measure (80) relating to the message (65) to indicate the OBD compliance (85) of the message (65).;

Description

The present disclosure relates to a computer-implemented method for checking an OBD compliance of messages of a bus system of a vehicle having a vehicle diagnostic system, wherein the vehicle has a first vehicle component and a second vehicle component, and the bus system connects the first vehicle component as transmitter of a message and the second vehicle component as receiver of the message to one another. The disclosure also relates to a computer program and / or computer readable medium and a data processing apparatus.Admission to a vehicle admission authority for operation and particularly sale, in, for example, a territorium, state, state group and / or market, may require evidence of compliance with various legal and / or normalized requirements.One of these requirements relates to legislation on vehicle diagnostic systems, also referred to as onboard diagnostics (OBD). For example, it is accordingly possible to demonstrate for a vehicle that emission-relevant signals from relevant control units of the vehicle are correspondingly sufficiently monitored and / or diagnosed and are displayed in the event of a fault. With complete monitoring, display and / or substitute reaction of the emission-relevant signals, a vehicle is considered to satisfy the requirement ("compliant") and is therefore saleable. A non-compliance ("non-compliance") gives the approval authority the possibility of non-approval and / or of penalty ("deficiency payment") per sold and / or in-traffic vehicle depending on the extent of the non-compliance.Vehicles must therefore be developed as far as possible to fulfil the requirement, so that the vehicle has only few non-fulfilment or signals with a non-fulfilment. Such non-fulfillments are to be given the approval authority with knowledge.The fundamental aspect of the disclosure is the prerequisite for a request to the OBD. In this case, features of fulfillment of an OBD request, a so-called OBD compliance, can be broken down into an OBD relevance, also receiver relevance, and an OBD compliance, also transmitter compliance, as features for fulfillment of the OBD request. Monitoring of certain system variables resulting from signals is assumed depending on the OBD relevance; the OBD compliance can be established by a corresponding OBD conformance.A positive OBD relevance of a signal, function module and / or control unit defines that this element is able to sufficiently influence the vehicle emissions in the event of a malfunction. A negative OBD relevance defines that a significant deterioration in emission cannot occur as a result of a malfunction of the signal, function module and / or control unit.A positive OBD conformance of a message of a vehicle component, i.e. of a signal of a function module and / or control unit, defines that this message is sufficiently monitored in accordance with the OBD request. Negative OBD conformance defines that there is no (or no sufficient) OBD monitoring for this type of message, wherein the specific request to the monitoring may be dependent on the message under consideration.The OBD relevance and OBD conformance are each evaluated in different ways and from different instances, for example automatically by a computerized method and / or manually by different experts. In this case, different evaluation results of the individual instances are to be combined to form a voiced overall image, which demonstrates the OBD compliance.US 2007 / 088472 A1 discloses a method for validating emission component conditions of a vehicle, comprising the steps of operatively loading drivable wheel hubs of the vehicle such that the vehicle drive wheel hubs can be driven without vehicle movement and running the vehicle through an associated drive cycle associated therewith. The method further comprises the steps of determining whether monitored emission components are in a standby state at the end of the drive cycle and monitoring for diagnostic trouble codes during and at the end of the drive cycle.In the event of an OBD requirement not being fulfilled, a so-called OBD non-compliance, an efficient process for finding an OBD compliance-based feature is to provide reassessment and resolution of the OBD non-compliance in order to establish the OBD compliance and to communicate the admission authority on the deadline to cause admission to maintain admission capability and / or reduce and / or avoid penalty payments.A bus system of a vehicle is particularly relevant here, wherein the vehicle has a first vehicle component and a second vehicle component, and the bus system connects the first vehicle component as transmitter of a message and the second vehicle component as receiver of the message to one another.On such bus systems, thousands of signals must typically be evaluated in order to establish an OBD compliance, which represents a non-imageable manual outlay for development parts of the sending first vehicle component and the receiving second vehicle component and for vehicle integration.DE 10 2022 105 248 A1, which is not disclosed on the filing date of the present patent application, relates to methods for determining whether at least one output signal of a control device of a vehicle is on-board diagnostic-compliant. The method comprises using a signal network which represents a signal flow in the control device, comprising at least one input signal and the at least one output signal. Furthermore, a check is provided as to whether a signal connection exists between the at least one input signal and the at least one output signal, as well as a check as to whether the at least one input signal is on-board diagnostic-compliant. Finally, an indication is made that the at least one output signal is on-board diagnostic-compliant, if there is a signal connection between the at least one input signal and the at least one output signal and if the at least one input signal is on-board diagnostic-compliant.Against the background of this prior art, it is an object of the present disclosure to specify a method which are each suitable for enrichment of the prior art. In particular, the object of the disclosure is to provide an efficient assessment of an OBD compliance for bus messages and / or to enable an OBD non-compliance to be effectively found and resolved.The object is achieved by the features of the independent claims. The dependent claims include further developments of the disclosure.The object is then achieved by a computer-implemented method for checking an OBD compliance of messages of a bus system of a vehicle having a vehicle diagnostic system, wherein the vehicle has a first vehicle component and a second vehicle component, and the bus system connects the first vehicle component as transmitter of a message and the second vehicle component as receiver of the message to one another. The method comprises: acquiring a technical message catalog relating to the messages together with a recipient relevance relating to the messages and a sender conformance relating to the messages; determining a consistency variable relating to the messages on the basis of the recipient relevance and sender conformance relating to the message in each case; and outputting the consistency variable relating to the message to indicate the OBD compliance of the message.The disclosure has recognized that messages of the bus system may be characterizable by attributes. Such attributes relate to the identity and / or identifier of the first vehicle component transmitting the message, the identity and / or identifier of the second vehicle component receiving the message, the recipient relevance of the second vehicle component and the sender conformance of the first vehicle component. In this case, the message catalog comprises, for example, a message identifier (identifier), a short description of the message and in each case information about the sender and about the recipient of the bus message. The respective recipient and the sender of a message are assigned to the message. The aforementioned information is stored in a data set called a message catalog and can thus be detected automatically.In addition to the message catalog, the recipient relevance and the sender conformance are recorded for the message. The receiver relevance is dependent on the behavior of the receiver. Transmitter conformance is dependent on the behavior of the transmitter. The recipient relevance and the sender conformance can have been determined by another automated method and / or by an expert.It has also been recognized that the receiver relevance and the transmitter conformance already have a meaningful conclusion on the OBD compliance. Therefore, a consistency size can be determined for each of the messages based on the recipient relevance and the sender conformance.In order to indicate the OBD compliance for each of the messages, the consistency variable associated with each of the messages may be output. According to the consistency size of a message, if the OBD compliance of the message is ensured, corresponding information can be recorded in approval documents or if the OBD compliance is not ensured, further measures for checking can be initiated.Optionally, the recipient relevance and the sender conformance of one of the messages is positive, negative or empty, respectively, and the consistency variable indicates whether the message is consistent, inconsistent, not relevant or to be checked. The previously mentioned details can be used to indicate whether the recipient relevance exists, i.e. is positive, does not exist, i.e. is negative, or no information about the recipient relevance is present, i.e. the recipient relevance is empty. It can be specified whether the transmitter conformance exists, i.e. is positive, does not exist, i.e. is negative, or no information about the receiver relevance is present, i.e. the receiver relevance is empty. This allows effective categorization of the receiver relevance and the transmitter conformance. The consistency size of a message can indicate whether the message is OBD-compliant, i.e. consistent, whether the message is not currently classified as an OBD-compliant, i.e. inconsistent, whether the message is not relevant for the OBD-compliance, i.e. not relevant, or whether the message requires a further check, i.e. is to be checked. In this case, in particular in the cases in which the consistency variable specifies that the message is inconsistent and / or is to be checked, further measures can be taken in order to check and / or establish the OBD compliance, if necessary. Messages for which the consistency variable indicates that the message is consistent can be automatically incorporated directly into approval documents.Optionally, the consistency size of one of the messages is determined to be consistent if the respective recipient relevance and sender conformance are positive. In this case, it can be automatically determined that the message is OBD-compliant, since the recipient relevance is given and the message is thus relevant for admission and the sender compliance is also given and it has thus been determined that the message is correspondingly sufficiently monitored and / or diagnosed. Thus, it can already be decided for the messages with positive recipient relevance and sender conformance that OBD compliance is present and the messages can be recorded in approval documents. This already allows a set of messages potentially to be further checked to be reduced by the messages with simultaneously positive recipient relevance and sender conformance.Optionally, the consistency variable of one of the messages is determined as not relevant if the respective recipient relevance is negative and / or the recipient relevance is empty and the sender conformance is positive. If the recipient relevance is negative, it can be automatically determined that the message does not have any relevance for the OBD compliance. If the recipient relevance is empty and the sender compliance is positive, then further checking for the OBD compliance is not required, since the OBD compliance is either given automatically if the recipient relevance is positive or the OBD compliance is irrelevant if the recipient relevance is negative. Thus, a set of potentially further to be checked messages can already be reduced by the messages with negative recipient relevance and the messages with empty recipient relevance and positive sender conformance.Optionally, the consistency variable of one of the messages is determined to be inconsistent if the respective recipient relevance is positive and the sender conformance is negative. In this case, it has been determined that the message can be inconsistent and thus not OBD compliant. As further measures, a manual detailed consideration can be taken by parties providing vehicle components, for example developers and / or manufacturers, in order to further check and / or establish the sender compliance and / or in order to further check or technically exclude the recipient relevance.Optionally, the consistency size of one of the messages is determined to be checked if the respective recipient relevance is positive and the sender conformance is empty, and / or if the respective recipient relevance is empty and the sender conformance is negative or empty. In the mentioned cases, it cannot be determined with certainty whether the message is to be evaluated as an OBD compliant. As further measures, a manual detailed consideration can be taken by parties providing vehicle components, for example developers and / or manufacturers, in order to further check and / or establish the sender compliance and / or in order to further check or technically exclude the recipient relevance.Optionally, the method comprises: acquiring a relevance check variable relating to one of the messages and / or a conformance check variable relating to one of the messages as a function of the consistency variable, determining a revised consistency variable relating to the corresponding message on the basis of the relevance check variable and / or the conformance check variable; and outputting the revised consistency variable relating to the message in order to specify the OBD compliance of the message. It was recognized that the consistency variable can be used to either place information relating to the message in approval documents or, in particular if the consistency variable specifies that the message is inconsistent or to be checked, can trigger a further check. The further test can then yield the relevance test variable and / or the conformance test variable. The revised consistency variable can be determined on the basis of the relevance check variable and / or the conformance check variable. In this case, the relevance check variable, the conformance check variable and the revised consistency variable can correspondingly comprise the details described above with reference to the recipient relevance, the sender conformance and the consistency variable. Thus, analogously to the consistency variable, the revised consistency variable can be determined and output.In other words, and with respect to a specific configuration described as not limiting to the present disclosure, the disclosure relates to determining OBD compliance for in-vehicle bus messages and eliminating inconsistencies. The core concept includes a tabular acquisition of all relevant bus sizes. Information on the message and on the sender and receiver; in the case of a plurality of senders and / or receivers of a single bus message: acquisition per receiver / sender tuple in a single line. For this purpose, various development documents can be incorporated, for example the bus message catalog and a text description of the bus messages. The receiver OBD relevance assessment (positive=yes, negative=no) is recorded in the corresponding table row-this assessment is usually initiated by a "tool". The sender OBD conformity assessment (positive=yes, negative=no) is recorded in the corresponding table row-this assessment is usually initiated by a "tool". In this case, the OBD relevance="yes" corresponds to a request for OBD monitoring and thus to a request for OBD conformance="yes", so that the system can be permitted as an OBD compliant. The definition of an OBD consistency variable can be determined by comparing the OBD relevance / conformance value pairs per row. The following cases result: a) in the case of relevance=yes, conformance=yes→ OBD-consistent, b) in the case of relevance=no→not relevant for OBD consistency, c) in the case of relevance=yes, conformance=no→ OBD-inconsistency, d) in the case of relevance= empty (empty), conformance=yes→not relevant for OBD-consistency e) in the case of relevance=yes, conformance=elevty→ OBD-consistency (there are no important values for the comparison) f) to check all other cases→ OBD-consistency (there are no important values for the comparison). The cases a), b), d) can be directly transferred into the approval documentation without further detailed observation. The cases e) and f) require a first analysis of the OBD relevance and / or OBD conformance by the OBD controller developers involved. Case c) is to be analyzed further in a manual detailed consideration by the OBD controller developers involved. In this case, a reduction in the manual outlay can be achieved by automatically forwarding the "case c)" bus messages to the developers concerned. Only case c) is forwarded - no other cases. The bus messages considered from case c) are checked manually once again: 1) If the tool-determined OBD relevance of the receiving party matches the historically present knowledge of OBD integration? 2) If the tool-determined OBD conformance of the sending party matches the historically present knowledge of OBD integration? 3) If the OBD consistency changes due to a change in values in 1) or 2)? If, after the manual checking of the bus messages from case c), an OBD consistency could still not be established for individual elements, the following discussion is carried out jointly: How complicated in terms of costs and / or implementation duration is a change in the OBD relevance? For this purpose, a function change can take place at the receiving control device and be rolled out. The affected InBus signal must then no longer be used in an OBD and / or emission context. How elaborate in terms of cost and / or implementation time is a change in OBD conformance? For this purpose, a function change can take place at the sending control device and be rolled out. The OutBus signal concerned must then completely meet the legal requirements for OBD monitoring. A decision is made as to which control device can produce the OBD consistency most easily. From this, an order for the function change to the control device with the lowest change expenditure can be made, depending on suppliers, time in the development process, cross-effects of the change, and others. With this last step, an OBD consistency of the "case c)" bus messages can be established for the present admission. As a result, the function change is caused to cancel out and the found cases are caused to communicate collectively in the permission documentation. From the generated overall discount, the delivery documentation for approval can be derived directly. After admission is made, all evaluated bus messages including their evaluation are archived. At the next admission time of the same control device, for example per model year, i.e. once annually, the archived table is continued. Thus, changes in OBD relevance and OBD conformance can be tracked and visualized in the follow-up permissions.According to one aspect of the invention, a computer program and / or a computer readable medium is provided. The computer program and / or the computer readable medium comprise instructions which, when the program or instructions are executed by a computer, cause the computer to carry out the method according to the invention and / or steps thereof. Optionally, the computer program and / or the computer-readable medium comprises instructions which, when the program or instructions are executed by a computer, cause the computer to carry out the method steps described as advantageous or optional in order to achieve a technical effect associated therewith.According to one aspect of the invention, a data processing apparatus is provided. The data processing device is configured to carry out the method described above. Optionally, the data processing device is configured to perform a method step described as advantageous or optional and / or to implement method features in order to achieve a technical effect associated therewith.One embodiment is described below with reference to the figures. FIG. 1 schematically illustrates a vehicle having an OBD compliance under test by a method according to an aspect of the disclosure; FIG. 2 schematically illustrates a flow diagram of a method according to an aspect of the disclosure; and FIG. 3 schematically illustrates an alternative diagram of a flow chart of a method according to an aspect of the disclosure.FIG. 1 schematically illustrates a vehicle 50 having an OBD compliance 85 to be tested by a method 100 according to an aspect of the disclosure. The vehicle 50 is a land vehicle and, in particular, a passenger car.Vehicle 50 includes a vehicle diagnostic system 56, a first vehicle component 60, a second vehicle component 61, and a bus system 55.Bus system 55 is a field bus, for example a CAN bus. Bus system 55 is configured to connect first vehicle component 60 and second vehicle component 61 to one another in terms of communication technology. For this purpose, bus system 55 is configured to allow a message 65 to be communicated between first vehicle component 60 and second vehicle component 61. In this case, the message 65 is communicated between the vehicle component 60 and the second vehicle component 61 via a signal connection 64 provided by the bus system 55. In the diagram according to FIG. 1, the first vehicle component 60 is designed as a transmitter 62 and the second vehicle component 61 is designed as a receiver 63. Thus, the first vehicle component 60 is configured to transmit the message 65, and the second vehicle component 61 is configured to receive the message 65 transmitted by the first vehicle component 60.The first vehicle component 60 and the second vehicle component 61 can each be, for example, a control unit, a sensor, an actuator and / or another device and / or software component that can be connected to the bus system 55 and is configured to communicate a message 65 via the bus system 55. The first vehicle component 60 and the second vehicle component 61 may be components of the vehicle 50 that have an effect on an emission of the vehicle 50 during operation of the vehicle 50.The vehicle diagnostic system 56, also referred to as an onboard diagnostic system or OBD system, is configured to monitor the bus system 55 and messages 65 communicated via the bus system 55. In this case, certain messages 65 may be relevant for satisfying OBD requirements, that is to say for what is known as an OBD compliance 85.The set of messages 65 transmitted via bus system 55 is stored in a message catalog 70. The message catalog 70 comprises attributes defining or describing the messages 65. For example, the message catalog 70 may include, for one of the messages 65, an identifier of the sender 62, an identifier of the recipient 63, a short designation of the message 65, a description of the message 65.In addition, messages 65 are described by OBD attributes, i.e., a recipient relevance 71 and a sender conformance 72. These can be derived from results of tool analyses and / or from experts. In this case, the message catalog 70 or information therefrom, in particular the above-mentioned information, the recipient relevance 71 and the sender conformance 72, can be maintained and / or extended in a common data set or data structure, a so-called library of the OBD attributes (see description of FIG. 3 ). The recipient relevance 71 and the sender conformance 72 are thus appended to the message catalog 70 or a portion thereof. Appending the recipient relevance 71 and the sender conformance 72 to the message catalog 70 serves to match matching recipient / sender pairings to their ascertained OBD attributes.FIG. 2 schematically illustrates a flow diagram of a method 100 according to an aspect of the disclosure. Method 100 is a computer-implemented method 100 for checking an OBD compliance 85 of messages 65 of a bus system 55 of a vehicle 50 having a vehicle diagnostic system 56, vehicle 50 having a first vehicle component 60 and a second vehicle component 61, and bus system 55 connecting first vehicle component 60 as transmitter 62 of a message 65 and second vehicle component 61 as receiver 63 of message 65 to one another. Such a vehicle 50 is described with reference to FIG. 1. FIG. 2 will be described with reference to FIG. 2.The method 100 comprises: acquiring 110 a technical message catalog 70 relating to the messages 65 with a recipient relevance 71 relating to one of the messages 65 and a sender conformance 72 relating to the messages 65.A consistency variable 80 relating to one of the messages 65 is determined 120 on the basis of the recipient relevance 71 and sender conformance 72 relating to the message 65, respectively. The consistency variable 80 of one of the messages specifies whether the message 65 is consistent, inconsistent, not relevant or to be checked.The consistency size 80 of one of the messages 65 is determined to be consistent if the respective recipient relevance 71 and sender conformance 72 are positive.The consistency variable 80 of one of the messages 65 is determined as not relevant if the respective recipient relevance 71 is negative and / or the recipient relevance 71 is empty and the sender conformance 72 is positive.The consistency variable 80 of one of the messages 65 is determined to be inconsistent if the respective recipient relevance 71 is positive and the sender compliance 72 is negative.The consistency size 80 of one of the messages 65 is determined to be checked if the respective recipient relevance 71 is positive and the sender conformance 72 is empty, and / or if the respective recipient relevance 71 is empty and the sender conformance 72 is negative or empty.The consistency variable 80 relating to the message 65 is output 130 in order to indicate the OBD compliance 85 of the message 65.A relevance check variable 73 relating to the messages 65 and / or a conformance check variable 74 relating to the messages 65 are detected 140 as a function of the consistency variable 80.A revised consistency variable 81 relating to the corresponding message 65 is determined 150 on the basis of the relevance check variable 73 and / or the conformance check variable 74.The revised consistency variable 81 relating to the message 65 is output 160 for indicating the OBD compliance 85 of the message 65. depending on the revised consistency variables 81, a repeated detection 140 of a relevance check variable 73 relating to the messages 65 and / or of a conformance check variable 74 relating to one of the messages 65 and a determination of a again revised consistency variable 81 can be carried out.FIG. 3 schematically illustrates an alternative diagram of a flow chart of a method 100 according to an aspect of the disclosure. FIG. 3 illustrates the method 100 described with reference to FIG. 2. FIG. 3 will be described with reference to FIGS. 1 and 2.In this case, FIG. 3 is divided into three columns, as indicated in each case by a dot-dashed line. The first and left column respectively relates to method steps of a data processing device 51. The second and middle column respectively relates to method steps relating to the transmitter 62 and performed by the data processing device 51. The third and right column marked with a dot-dashed line respectively relates to method steps relating to the receiver 63 and carried out by the data processing device 51. Between the second and third columns is another step, namely a check 135, which can be performed manually.The illustration of FIG. 3 begins with the signal connection 64, since the receiver 63 knows the message 65, the transmitter 62 of the message 65 and the receiver 63 of the message 65. The message catalog 70 is recorded 110; in this case, the recipient relevance 71 and the sender conformance 72 are additionally recorded for the message 65 in the message catalog 70.The consistency variable 80 is determined 120 on the basis of the recipient relevance 71 and the sender conformance 72 relating to the message 65, respectively. the recipient relevance 71 and the sender conformance 72 can be determined with computer assistance by an automatic tool with regard to the OBD compliance 85.The consistency variables 80 relating to the messages 65 are output 130 in order to specify the OBD compliance 85 of the messages 65.If the consistency variable 80 of the message 65 indicates that the message 65 is consistent, then a recording 170 in approval documents (see arrow downwards from the OBD compliance 85) takes place directly. If the consistency variable 80 of the message 65 indicates that the message 65 is not relevant, the method 100 for the message 65 is ended (see arrow from the OBD compliance 85 to the left).If the consistency variable 80 of the message 65 indicates that the message 65 is inconsistent or to be checked, a check 135 is carried out (see arrow from the OBD compliance 85 to the right). The test 135 results in a test result 82. The test result 82 comprises a compliance test variable 74 relating to the message 65 relating to the relevance test variable 73 and / or a compliance test variable 74 relating to the message 65. the relevance test variable 73 and / or the compliance test variable 74 result from changes to the vehicle components 50, 51 in order to establish the OBD compliance 85. The relevance check variable 73 and / or the conformance check variable 74 are captured 140 as a function of the consistency variable 80. If the recipient relevance 71 is negative, the check result 82 comprises the relevance check variable 73. if the transmitter conformance 72 is negative, the check result 82 comprises the conformance check variable 74.The test result 82 or the relevance test variable 73 and / or the conformance test variable 74 are transferred into the data structure for maintaining information of the message catalog 70, the data structure comprising the recipient relevance 71 and the sender conformance 72, a so-called library of the OBD attributes. In this case, the test result 82 or the relevance test variable 73 and / or the conformance test variable 74 is entered, for example, in a line relating to the message 65.A revised consistency variable 81 relating to the corresponding message 65 is determined 150 on the basis of the relevance check variable 73 and / or the conformance check variable 74.The revised consistency variables 81 relating to the messages 65 are output 160 for indicating the OBD compliance 85 of the messages 65. As described with reference to the consistency variable 80, a recording 170 in approval documents is directly carried out if the revised consistency variables 81 indicate that the message 65 is consistent. If the revised consistency variable 81 of the message 65 indicates that the message 65 is not relevant, the method 100 for the message 65 is ended. If the revised consistency variable 81 of the message 65 indicates that the message 65 is inconsistent or is to be checked, a check 135 is carried out again.Reference Sign (Part of Description)50 Vehicle 55 Bus system 56 Vehicle diagnostic system 60 First vehicle component 61 Second vehicle component 62 Transmitter 63 Receiver 64 Signal connection 65 Message 70 Message catalog 71 Receiver relevance 72 Transmitter conformance 73 Relevance checking variable 74 Conformance checking variable 80 Consistency variable 81 Revised consistency variable 82 Checking result 85 OBD compliance 100 Method 110 Capture 120 Determination 130 Output 135 Checking 140 Capture 150 Determination 160 Output 170 Capture

Claims

Computer-implemented method (100) for checking an OBD compliance (85) of messages (65) of a bus system (55) of a vehicle (50) with a vehicle diagnostic system (56), wherein the vehicle (50) has a first vehicle component (60) and a second vehicle component (61), and the bus system (55) connects the first vehicle component (60) to one another as transmitter (62) of a message (65) and the second vehicle component (61) to one another as receiver (63) of the message (65), wherein the method (100) has: - acquisition (110) of a technical message catalog (70) relating to the messages (65) together with a receiver relevance (71) relating to one of the messages (65) and a transmitter conformance (72) relating to the messages (65); determining (120) a consistency variable (80) relating to one of the messages (65) on the basis of the recipient relevance (71) and sender conformance (72) relating to the message (65) in each case; and outputting (130) the consistency variable (80) relating to the message (65) for indicating the OBD compliance (85) of the message (65).The computer-implemented method (100) of claim 1, wherein each of the recipient relevance (71) and the sender conformance (72) of one of the messages (65) is positive, negative, or empty and the consistency size (80) indicates whether the message (65) is consistent, inconsistent, non-relevant, or to check.The computer-implemented method (100) of claim 2, wherein the consistency size (80) of one of the messages (65) is determined to be consistent if the respective recipient relevance (71) and sender conformance (72) are positive.The computer-implemented method (100) of claim 2 or 3, wherein the consistency size (80) of one of the messages (65) is determined to be non-relevant if the respective recipient relevance (71) is negative and / or the recipient relevance (71) is empty and the sender conformance (72) is positive.The computer-implemented method (100) of any of claims 2 to 4, wherein the consistency size (80) of one of the messages (65) is determined to be inconsistent if the respective recipient relevance (71) is positive and the sender conformance (72) is negative.The computer-implemented method (100) of any of claims 2 to 5, wherein the consistency size (80) of one of the messages (65) is determined to be checked if the respective recipient relevance (71) is positive and the sender conformance (72) is empty, and / or if the respective recipient relevance (71) is empty and the sender conformance (72) is negative or empty.Computer-implemented method (100) according to one of the preceding claims, wherein the method (110) comprises: - detecting (140) a relevance checking variable (73) relating to one of the messages (65) and / or a conformance checking variable (74) relating to one of the messages (65) as a function of the consistency variable (80); - determining (150) a revised consistency variable (81) relating to the corresponding message (65) on the basis of the relevance checking variable (73) and / or the conformance checking variable (74); and - outputting (160) the revised consistency variable (81) relating to the message (65) for indicating the OBD compliance (85) of the message (65).Computer program and / or computer-readable medium comprising instructions which, when the program or instructions are executed by a data processing device (51), cause them to carry out the method (100) and / or the steps of the method (100) according to one of Claims 1 to 7Data processing device (51), wherein the data processing device (51) is configured to perform the method (100) according to any one of claims 1 to 7.

Images