METHOD AND COMPUTER PROGRAMS FOR A SURVEILLANCE INSTANCE

Description

[0001] The present invention relates to methods and computer programs for a monitoring entity and a communication component, a monitoring entity, a communication component, a system and a vehicle, in particular but not exclusively to a concept for monitoring communication components for event-based communication in a motor vehicle.

[0002] In automotive engineering, as well as in computer and communications technology in general, data buses are used to enable data communication between different components connected or coupled to a data bus. For example, two communication partners or communication components exchange messages via a data bus, with the communication being event-based. In contrast to cyclic communication, with event-based communication, messages are only exchanged when a corresponding event occurs. For example, on a motor vehicle bus, a "turn signal on" message (also known as a "request") is sent when the driver activates the turn signal, and a corresponding "turn signal off" message when the turn signal lever returns to its original position.

[0003] Disruptions can cause either the communication partner or the communication link (e.g., a data bus interruption) to fail. In this case, the question arises as to how such a failure can be detected. In event-based communication, there is no timeout monitoring, so this failure goes unnoticed without further action. From the perspective of a communication partner, there is no detectable difference between a failure and the non-occurrence of the event, since no message is sent in either case.

[0004] For a continuous target specification, a service-requesting device (also known as a "client") would renew its request before a maximum execution time expires. In the example above, the turn signal would be switched on for 10 seconds after receiving the switch-on message. However, if the turn signal lever were still activated after these 10 seconds, a new switch-on message would have to be sent to keep the turn signal active. If the turn signal lever were deactivated before the 10 seconds had elapsed, a switch-off message would have to be sent. This mechanism would prevent the turn signal from remaining activated indefinitely in the event of communication errors on the data bus, but the error itself would not be detected.

[0005] For safety-relevant functions, timeouts are typically less than one second. To accommodate this, the event-based communication described above would be converted to quasi-cyclical communication in order to comply with the timeouts. Since this would likely affect a large number of functions, a high bus load would result without providing any functional added value. Examples of such use cases include turn signals, warning lights, seat adjustment, lighting, ventilation, setpoint specifications (e.g., cruise control), fan controls, etc.

[0006] US Pat. No. 6,574,197 B1 discloses a network monitoring device arranged in a node connected to a network. A determination unit is configured to send a monitoring packet to a neighboring node upstream or downstream. It is determined that the neighboring node is disconnected from the network unless the determination unit receives a corresponding response packet. A notification unit informs the other nodes in the network about a disconnected node, if appropriate.

[0007] SILVA LM ET AL: "DIP : Distributed Diagnosis Protocol", MICROPROCESSING AND MICROPROGRAMMING, ELSEVIER SCIENCE PUBLISHERS, BV., AMSTERDAM, NL, Vol. 38, Nos. 1-5, September 1, 1993 (1993-09-01), pages 171-178, discusses a diagnostic protocol for checking the availability of processors in a distributed system. Each node maintains a network status table, and error detection is achieved through messages indicating a node's vitality. The signaling overhead of these messages is minimal, and the main advantage of the protocol is the reduced diagnostic latency when an error is detected. This is because the unavailability of a node can be the result of a processor crash or a network partition.

[0008] Document US 2004 / 100971 A1 describes a communication system in which a first node is connected to a plurality of second nodes to control the operation of the second nodes. The plurality of second nodes are arranged in one or more logical links, wherein the topology of the one or more logical links differs from the topology of the physical connection of the nodes. Each second node comprises means for sending status messages to its logical successor node and means for monitoring status messages sent by its second logical predecessor node to determine its status.

[0009] Patent publication EP 2144400 A1 discloses a distributed Ethernet system consisting of a plurality of switches connected in series to form a ring structure. After clock synchronization, each of the switches periodically performs ring detection and protocol engine detection in sequence according to a predefined software configuration and sends an error message when a ring connection error or a protocol engine error is detected.

[0010] There is therefore a need for an improved concept for detecting the above-mentioned error patterns without requiring all functions at the application level to implement their own time-out monitoring mechanisms.

[0011] This need is met by methods and computer programs for a monitoring entity and a communication component, a monitoring entity, a communication component, a system, and a vehicle according to the pending independent claims. Advantageous embodiments and further developments are the subject of the dependent claims.

[0012] Embodiments of the present invention are based on the core idea that monitoring instances can be used to monitor the functionality of communication components. The monitoring instances can communicate with each other cyclically, thus detecting a failure of a communication component or a data bus. The cyclic control information exchanged between different monitoring instances can be reduced compared to the control information that would have to be exchanged directly between the communication components for monitoring, especially when a monitoring instance monitors multiple communication components.

[0013] Embodiments provide a method for a monitoring instance for monitoring at least one communication component, wherein the communication component is configured to communicate with one or more other communication components in an event-based manner via a data bus. The method comprises regular checking of the function of the communication component by the monitoring instance and cyclical communication with at least one other monitoring instance assigned to another communication component in order to monitor the function of the communication component, the function of the other communication component, and the function of the data bus. The cyclical communication between the monitoring instances allows the monitoring of the communication between the communication components and the data bus.

[0014] Embodiments provide a method for a communication component to communicate with one or more other communication components via a data bus. The method includes event-based communication with the one or more other communication components via the data bus and cyclic communication with the monitoring instance. Embodiments can thus allow efficient monitoring of communication components.

[0015] In some embodiments, cyclic communication between monitoring instances occurs on the data bus, allowing the data bus to be indirectly monitored. A failure of cyclic communication with intact monitoring instances allows the conclusion that there is a malfunction on the data bus. In further embodiments, the method can further comprise cyclic communication between the monitoring instance and the communication component via a connection different from the data bus, for example, a local connection. The communication established for direct monitoring is then independent of the data bus, and its success does not depend on the transmission capacities and states of the data bus.

[0016] In some embodiments, the method may further comprise transmitting an error indication to at least one other monitoring instance when a malfunction or a communication error of the communication component is detected. In this respect, the communication required for monitoring can be limited to the monitoring instances and thus implemented efficiently. The method further comprises synchronizing with at least one other monitoring instance via the data bus. This can improve the efficiency of the cyclic communication. In some embodiments, the communication component may be registered with the monitoring instance. Analogously, the method for the communication component may comprise registering with the monitoring instance.This allows the monitoring instance and the method to be used more universally, for example, for various and multiple communication components. Embodiments can be used, for example, to monitor communication components and a data bus in a vehicle.

[0017] Embodiments further provide one or more computer programs for performing one or more of the methods described herein when the computer program runs on a computer, a processor, or a programmable hardware component.

[0018] A further embodiment is a monitoring instance for a communication component that is designed to communicate with one or more other communication components via a data bus. The monitoring instance comprises one or more interfaces for communication via the data bus and for communication with the communication component. The monitoring instance further comprises a control device that is designed to control the one or more interfaces and to cyclically communicate with the communication component and with at least one other monitoring instance of another communication component. In some embodiments, the control device can be designed to communicate with the communication component via a connection that is different from the data bus. Monitoring can thus be carried out independently of the data bus.

[0019] The control device can be configured to transmit an error indication to at least one other monitoring entity when a malfunction or communication error of the communication component is detected. Malfunctions can thus be brought to the attention of other monitoring entities. The control device is configured to synchronize with at least one other monitoring entity via the data bus and / or, in some embodiments, can be configured to register a communication component. The monitoring entity can be configured to monitor communication components and a data bus in a vehicle.

[0020] Embodiments also provide a communication component for communicating with one or more other communication components via a data bus. The communication component comprises one or more interfaces for communicating via the data bus and for communicating with a monitoring entity. The communication component further comprises a control device configured to control the one or more interfaces, to communicate with the one or more other communication components in an event-based manner, and to communicate cyclically with the monitoring entity. Analogous to the above description, the control device can be configured to perform a registration with the monitoring entity.

[0021] Embodiments also provide a system with at least two monitoring entities as described above and at least two communication components assigned to the monitoring entities as described above. Another embodiment is a vehicle with such a system.

[0022] Further advantageous embodiments are described in more detail below with reference to the exemplary embodiments shown in the drawings, to which exemplary embodiments are generally not limited. They show: Fig. 1 a flowchart of an embodiment of a method for a monitoring instance; Fig. 2 a flowchart of an embodiment of a method for a communication component; Fig. 3 an embodiment of a monitoring instance, an embodiment of a communication component and an embodiment of a system; Fig. 4 an architecture of a monitoring service in one embodiment; Fig. 5 a failure of a communication component in one embodiment; Fig. 6 a failure of a data bus in one embodiment; Fig. 7 a sequence of exchanged messages in one embodiment; Fig. 8 a sequence of exchanged messages in another embodiment; and Fig. 9 a sequence of exchanged messages in another embodiment.

[0023] Various embodiments will now be described in more detail with reference to the accompanying drawings, in which some embodiments are illustrated. Optional features or components are shown in dashed lines.

[0024] Although embodiments are susceptible to various modifications and variations, embodiments are illustrated in the figures as examples and will be described in detail herein. It should be understood, however, that embodiments are not intended to limit embodiments to the specific forms disclosed, but rather, embodiments are intended to cover all functional and / or structural modifications, equivalents, and alternatives within the scope of the invention.

[0025] Note that an element described as "connected" or "coupled" to another element may be directly connected or coupled to the other element, or there may be intervening elements. Conversely, when an element is described as "directly connected" or "directly coupled" to another element, no intervening elements are present. Other terms used to describe the relationship between elements should be interpreted similarly (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.).

[0026] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments. As used herein, the singular forms "a," "an," "another," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Furthermore, it is to be understood that terms such as "includes," "including," "has," "comprises," "comprising," and / or "having," as used herein, indicate the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more features, integers, steps, operations, elements, components, and / or groups thereof.

[0027] Fig. 1 illustrates a flowchart of an embodiment of a method 10 for a monitoring instance 30. Fig. 2 shows an associated flowchart of an embodiment of a method 20 for a communication component 40. Fig. 3 shows an overview of an embodiment of a system 80 with embodiments of monitoring instances 30, 60 and embodiments of communication components 40, 50.

[0028] Fig. 1 shows a method 10 for a monitoring instance 30 for monitoring at least one communication component 40. The communication component 40 is designed to communicate in an event-based manner via a data bus 70 with one or more other communication components 50. The method 10 comprises a regular checking 12 of the function of the communication component 40 by the monitoring instance 30. The method further comprises cyclical communication 14 with at least one other monitoring instance 60, which is assigned to another communication component 50, in order to monitor the function of the communication component 30, the function of the other communication component 50 and the function of the data bus 70.

[0029] Here and in the following, "regular" is understood to mean a rule-based temporal sequence. For example, a rule can stipulate that such communication takes place within a cycle, i.e., within a specified time period. Regular checking can therefore be carried out on the basis of a defined temporal basis, a clock rate, or a period, for example, every 10 ms, 20 ms, 50 ms, 100 ms, 200 ms, 500 ms, 1 s, 2 s, 5 s, etc. A certain tolerance is to be expected, adapted to practical conditions, and a (theoretically) perfect period cannot be assumed. In this respect, "regular" communication can also mean "periodic" or "cyclical" communication, in the sense that a maximum time period between two messages is not exceeded according to a specified probability. Cyclical communication can occur according to a guaranteed or at least highly predictable schedule.

[0030] Another rule would be tied to an event, so that a malfunction can be detected within a certain time with a high degree of certainty. In this case, the event occurs with a sufficiently high probability. Finally, a combination is also conceivable, namely that a check cycle is adapted depending on the events. For example, some communication components can be checked more frequently (so that a fault can be detected more quickly) if certain events have occurred. For example, a frost warning device may be monitored relatively rarely or not at all at temperatures above 20°C, whereas it is checked more frequently at lower temperatures.

[0031] Analogously, the Fig. 2 a method 20 for a communication component 40 for communicating with one or more other communication components 50 via a data bus 70. The method 20 comprises event-based communication 22 with the one or more other communication components 50 via the data bus 70 and cyclic communication 24 with the monitoring instance 30.

[0032] In exemplary embodiments, the communication components 40, 50 in a communication system 80 can therefore be implemented by monitoring instances 30, 60 assigned to the communication components 40, 50. Such systems 80 can be used, for example, in vehicles, e.g., motor vehicles, ships, trains, aircraft, trucks, passenger cars, two-wheelers, etc. In this case, control units that are entrusted with various functions communicate with each other. On the one hand, there are central control units where information is consolidated and evaluated, and on the other hand, control units are used that monitor, control, or regulate components such as lighting, indicators, brake lights, sensors, actuators, warning lamps, displays, input devices such as buttons or levers, etc. In the following, these control units are also referred to as communication components that communicate with each other via a data bus 70, as described in the Fig. 3 is shown. Fig. 3 shows a system 80 with two monitoring instances 30, 60 and two communication components 40, 50 that communicate with each other via a data bus 70. In exemplary embodiments, the data bus 70 can be, for example, the CAN (Controller Area Network) bus or another fieldbus.

[0033] As the Fig. 3 shows, the individual components 30, 40, 50, 60 each have one or more interfaces 32, 42, 52, 62 and each have a control device 34, 44, 54, 64, which are further coupled to one another. The one or more interfaces 32, 42, 52, 62 can, for example, correspond to one or more inputs or outputs for receiving or providing information or signals, for example in digital bit values, voltages, currents or electromagnetic waves, for example based on a code, within a module, between modules, or between modules of different entities. In this respect, the one or more interfaces 32, 42, 52, 62 are suitable for exchanging signals or information on the data bus 70 or between monitoring instances 30, 60 and communication components 40, 50, i.e. for sending and / or receiving.Additional components may be present or interconnected between the one or more interfaces 32, 42, 52, 62. Examples include amplifiers, filters, diplexers, duplexers, mixers, phase shifters, low-noise amplifiers (LNA), plugs, sockets, etc.

[0034] In exemplary embodiments, the control device 34, 44, 54, 64 can correspond to any controller or processor or a programmable hardware component. For example, a control device 34, 44, 54, 64 can also be realized as software that is programmed for a corresponding hardware component. In this respect, a control device 34, 44, 54, 64 can be implemented as programmable hardware with appropriately adapted software. Any processors, such as digital signal processors (DSPs), can be used. Exemplary embodiments are not limited to a specific type of processor. Any processor or even multiple processors or microcontrollers are conceivable for implementing the control module. Implementations in integrated form with other control units are also conceivable, for example in a control unit for a vehicle that additionally comprises one or more other functions.The method steps described herein can be executed in exemplary embodiments by the control devices 34, 44, 54, 64 or by the respective one or more interfaces 32, 42, 52, 62. In this respect, the method steps described can be carried out by the device components.

[0035] The Fig. 3 further illustrates with the double-sided arrows that appropriate communication can take place between the components or between components and data bus.

[0036] In exemplary embodiments, a first communication component 40 can, for example, be a control unit for a vehicle motion manager (VMM). This control unit can offer corresponding client functions. The clients, for example, other control units than the communication component 50 that manage a corresponding interface to the vehicle driver, can submit requests that can be valid for several seconds (e.g., trajectory) to, theoretically, minutes or even hours (e.g., target speed). However, if the customer function fails (or the communication fails), a replacement response must be provided promptly (less than one second).In this case, this function is performed by the monitoring instances 30, 60, which are directly assigned to the communication components 40, 50 and monitor them locally, for example by cyclic communication between the monitoring instance 30, 60 and the communication component 40, 50 via a connection different from the data bus 70.

[0037] The monitoring instances 30, 60 can, for example, communicate with each other cyclically via the data bus 70. If the data bus fails, this cyclic communication fails, and the malfunction of the data bus 70 can be detected promptly. If a malfunction occurs in one of the communication components 40, 50, this can be detected by the monitoring instances 30, 60 via the local interfaces and communicated with each other via the data bus 70.

[0038] In a further exemplary embodiment, warning lights (communication component 50) are activated and deactivated on an event-based basis by a customer function (communication component 40), with the monitoring instances 30, 60 promptly detecting any errors as described above. This can result in a reduction in communication on the data bus, since cyclic communication can be restricted to the monitoring instances 30, 60, and these can also monitor multiple communication components simultaneously without increasing the load on the data bus 70. This can lead to a lower message density or message size on the data bus 70 than would be the case if a warning light were actively suppressed by the associated respective customer function (e.g., brake warning light), which requires constant individual messages between the respective communication components, and the warning light is then activated when the customer function fails.

[0039] The Fig. 3 shows an embodiment of a monitoring instance 30 for at least one communication component 40, which is designed to communicate with one or more other communication components 50 via a data bus 70. The monitoring instance 30 comprises one or more interfaces 32 for communication via the data bus 70 and for communication with the communication component 40. The monitoring instance 30 comprises a control device 34, which is designed to control the one or more interfaces 32 and to communicate cyclically with the communication component 40 and with at least one other monitoring instance 60 of another communication component 50.

[0040] As already described above, the control device 34 of the monitoring instance 30 can be designed to communicate with the communication component 40 via a connection different from the data bus 70, for example via a local interface 32. Furthermore, the control device 34 is designed to transmit an error indication to at least one other monitoring instance 60 when a malfunction or a communication error of the communication component 40 is detected.

[0041] The Fig. 3 further illustrates an embodiment of a communication component 40 for communication with one or more other communication components 50 via a data bus 70. The communication component 40 comprises one or more interfaces 42 for communication via the data bus 70 and for communication with a monitoring instance 30. The communication component 40 further comprises a control device 44 which is designed to control the one or more interfaces 42, to communicate with the one or more other communication components 50 in an event-based manner and to communicate cyclically with the monitoring instance 30.

[0042] The embodiment of a system 80 in the Fig. 3 , comprises at least two monitoring instances 30, 60 as described above and at least two communication components 40, 50 assigned to the monitoring instances 30, 60 as described above. Another embodiment is a vehicle with such a system 80.

[0043] Fig. 4 shows an architecture of a monitoring service in one exemplary embodiment. The monitoring service is also referred to below as the watchdog service; analogously, the monitoring instance 30, 60 is also referred to as the watchdog. Fig. 4 shows on the left side a first control unit "SG 1", on which a client "foo" is implemented as a communication component 40 and a "Watchdog 1" as a monitoring instance 30. On the right side, a second control unit "SG 2" is shown, on which a second communication component 50 is implemented as (service) "bar" and a second monitoring instance 60 is implemented as "Watchdog 2". "foo" and "bar" are placeholders for any "clients" (customers) and services (services, customer functions). As the Fig. 4 As further shown, a plurality of additional control units may be present, with the monitoring instances 30, 60 communicating cyclically with each other via the dotted arrows. Communication between the monitoring instances 30, 60 and the associated communication components 40, 50 takes place locally (double-dashed arrows).

[0044] The clients (communication components 40, 50) are monitored cyclically on a local processor, also called "localhost" (SG 1, SG 2), so that the bus load is irrelevant. The monitoring service (watchdog service) for the two communication components 40, 50 is implemented via the two monitoring instances 30, 60. A local instance of the watchdog service (method 10, monitoring instances 30, 60) is implemented on each "SG 1, SG 2" participating in the event-based communication. The local instances of the watchdog service 30, 60 synchronize via bus 70. A "client," here a communication component 40, 50, can register with the watchdog service 30, 60. In the event of a communication error, the watchdog service 30, 60 informs the communication partner of the "client" 40, 50 as a fallback reaction.

[0045] Fig. 5 illustrates a failure of a communication component 40 in the embodiment described with reference to Fig. 4 The client "foo" 40 fails in this embodiment, as indicated by the lightning. The monitoring instance 30 "Watchdog 1" notices this due to the local cyclic communication with "client foo," which can also fail, for example, or via which "client foo" can report an error to the watchdog. "Watchdog 1" 30 can then transmit a corresponding message via the cyclic communication with "Watchdog 2" 60, which can then be forwarded by "Watchdog 2" to the "Service bar" 50. In this way, "Watchdog 1" 30 can notify the "Service bar" 50 of the error.

[0046] In this exemplary embodiment, the method 10 for the monitoring instance 30 comprises transmitting an error indication to at least one other monitoring instance 50 when a malfunction or a communication error of the communication component 40 is detected. In further exemplary embodiments, transmission to several additional monitoring instances 60 can also occur.

[0047] Fig. 6 shows a failure of a data bus 70 in one embodiment. The scenario is again assumed, which was already described in the Fign. 4 and 5 The lightning in Fig. 6 indicates that there is a disturbance or failure on the data bus 70. This also interrupts the cyclic communication between the monitoring instances 30, 60, so that both sides can notice the error and communicate it to their communication components 40, 50. The delay with which such an error can be noticed and communicated depends on the frequency of the cyclic communication on the data bus 70. Furthermore, synchronization of the individual monitoring instances 30, 60 can help to avoid additional delays. The method 10, which is carried out in a monitoring instance 30, 60, therefore comprises synchronization with at least one other monitoring instance 60 via the data bus 70. If the monitoring instances 30, 60 that are cyclically active on the data bus 70 are synchronized with one another, i.e., have a common time base or clock, communication on the data bus 70 can run more efficiently.the transmission capacities of the data bus are better utilized.

[0048] The control device 34 of the monitoring instance 30 is designed accordingly to synchronize itself with at least one other monitoring instance 60 via the data bus 70, or vice versa.

[0049] This can also be achieved by efficiently managing the capacities of the monitoring entity 30, 60 itself. To achieve this, the method 10 for the monitoring entity 30, 60 can provide for registration of the communication component 40, 50 with the monitoring entity 30, 60. The method 20 for the communication component 40, 50 can correspondingly further provide for registration with the monitoring entity 30, 60. The control device 34, 64 of the monitoring entity 30, 60 can be configured to register a communication component 40, 50. The control device 44, 54 of the communication component can be configured to register with the monitoring entity 30, 60.

[0050] Fig. 7 shows a sequence of exchanged messages in one embodiment, where the Fig. 7 shows the normal operation of the Watchdog service, where no errors occur. Fig. 7 shows the "client foo" 40 on the left as described above. In the middle, the monitoring service "Watchdog" is shown, which is implemented by the monitoring instances 30, 60 described above. Both communication components 40, 50 register for the watchdog service. In this exemplary embodiment, the "client foo" 40 can request a notification service with a time limit (timeout), whereby the time limit specifies the time after which a message about an error should be distributed, at the latest after the error has occurred. The direction of communication for bus monitoring is important or necessary, at least for some services, as will be explained below. In the exemplary embodiment shown, the cyclic communication between the "client foo" 40 and the watchdog service 30, 60 is implemented such that the "client foo" sends requests to the watchdog 30 at regular intervals (also called "timeout")."keep alive request", which is then answered by Watchdog 30. Like the . Fig. 7 As shown below, the service can also be canceled ("remove").

[0051] Fig. 8 shows a sequence of exchanged messages in another embodiment. Fig. 8 shows the scenario Fig. 7 and the exchanged messages in the error pattern according to Fig. 5 . Accordingly, the flash again shows the error at "Client foo" 40. This error occurs in the Fig. 7 The scenario described above occurs if the "client foo" 40 does not submit a request to the watchdog service within the set time limit. The watchdog service 30, 60 then distributes (multicast) a corresponding "Time-Out foo" message (time limit exceeded by "foo").

[0052] In the following example, if a bus error occurs, the watchdog service reports with information about which communication connections of the registered clients are affected. In other words, the watchdog service knows which communication paths the registered clients have with the services they use. If a bus error then occurs, the watchdog service can report via an event on both sides of the interruption which communication paths between clients and services are disrupted. Fig. 9 shows a sequence of exchanged messages in a further embodiment with a data bus error according to Fig. 6 . After detecting the error (indicated by the lightning), the watchdog service 30, 60 sends a corresponding "Time-Out foo" message (time limit exceeded by "foo") to "Service bar" 50 and a "Time-Out bar" message to "Client foo" 40.

[0053] In embodiments, the methods 10, 20 disclosed herein can be used to monitor communication components 40, 50 and a data bus 70 in a vehicle. Accordingly, the monitoring entities 30, 60 can be configured to monitor communication components 40, 50 and a data bus 70 in a vehicle. Embodiments can be used, for example, in passenger cars, trucks, railways, aircraft, or vehicles in general. For this purpose, embodiments can, for example, use central services for monitoring the communication buses at a topmost communication layer.

[0054] Further embodiments are computer programs for carrying out one of the methods described herein when the computer program runs on a computer, a processor, or a programmable hardware component. Depending on specific implementation requirements, embodiments of the invention can be implemented in hardware or in software. The implementation can be carried out using a digital storage medium, for example a floppy disk, a DVD, a Blu-ray disc, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, a hard disk, or another magnetic or optical storage device on which electronically readable control signals are stored that can interact or interact with a programmable hardware component in such a way that the respective method is carried out.

[0055] A programmable hardware component can be formed by a processor, a computer processor (CPU = Central Processing Unit), a graphics processor (GPU = Graphics Processing Unit), a computer, a computer system, an application-specific integrated circuit (ASIC = Application-Specific Integrated Circuit), an integrated circuit (IC = Integrated Circuit), a single-chip system (SOC = System on Chip), a programmable logic element or a field-programmable gate array with a microprocessor (FPGA = Field Programmable Gate Array).

[0056] The digital storage medium can therefore be machine- or computer-readable. Some embodiments thus comprise a data carrier having electronically readable control signals capable of interacting with a programmable computer system or a programmable hardware component such that one of the methods described herein is performed. One embodiment is thus a data carrier (or a digital storage medium or a computer-readable medium) on which the program for performing one of the methods described herein is recorded.

[0057] In general, embodiments of the present invention can be implemented as a program, firmware, computer program, or computer program product with program code or data, wherein the program code or data is effective to perform one of the methods when the program runs on a processor or a programmable hardware component. The program code or data can also be stored, for example, on a machine-readable medium or data carrier. The program code or data can be present, among other things, as source code, machine code, or bytecode, as well as other intermediate code.

[0058] The above-described embodiments are merely illustrative of the principles of the present invention. It is understood that modifications and variations of the arrangements and details described herein will be apparent to others skilled in the art. Therefore, it is intended that the invention be limited only by the scope of the following claims and not by the specific details presented in the description and explanation of the embodiments herein. Bezugszeichenliste

[0059] 10Procedure for monitoring instance 12Regular checking 14, 24Cyclic communication 20Procedure for communication component 22Event-based communication 30, 60Monitoring instance 32, 42, 52, 62One or more interfaces 34, 44, 54, 64Control device 40, 50Communication component 70Data bus 80System

Claims

1. Method (10) for a monitoring entity (30) for monitoring at least one communication component (40), wherein the communication component (40) is designed to communicate in an event-based manner via a data bus (70) with one or more other communication components (50), comprising the following steps: regular checking (12) of the function of the communication component (40) by the monitoring entity (30) via the data bus or a connection which differs from the data bus; and cyclic communication (14) with at least one other monitoring entity (60) assigned to another communication component (50) in order to monitor the function of the communication component (40), the function of the other communication component (50) and the function of the data bus (70), further comprising synchronizing with the other monitoring entity (60) via the data bus (70) to obtain a common time base.

2. Method (10) according to claim 1, wherein the cyclic communication takes place on the data bus (70).

3. Method (10) according to either of the preceding claims, further comprising cyclic communication between the monitoring entity (30) and the communication component (40) via a connection which differs from the data bus (70).

4. Method (10) according to any of the preceding claims, further comprising transmitting an error indication to at least one other monitoring entity (50) when a malfunction or a communication error of the communication component (40) is detected.

5. Method (10) according to any of the preceding claims, further comprising registering the communication component (40) with the monitoring entity (30).

6. Method (10) according to any of the preceding claims for monitoring communication components (40; 50) and a data bus (70) in a vehicle.

7. Method (20) for a communication component (40) for communicating with one or more other communication components (50) via a data bus (70), having event-based communication with the one or more other communication components (50) via the data bus (70); and cyclic communication, via a connection which differs from the data bus, with a monitoring entity (30) assigned to the communication component (40).

8. Method (20) according to claim 7, further comprising registering with the monitoring entity (30).

9. Computer program for carrying out one of the methods according to any of claims 1 to 8 when the computer program runs on a computer, a processor, or a programmable hardware component.

10. Monitoring entity (30) for at least one communication component (40) which is designed to communicate with one or more other communication components (50) via a data bus (70), having one or more interfaces (32) for communicating via the data bus (70) and for communicating with the communication component (40); and a control device (34) designed to control the one or more interfaces (32) and to carry out the method according to any of claims 1 to 6.

11. Communication component (40) for communicating with one or more other communication components (50) via a data bus (70), having one or more interfaces (42) for communicating via the data bus (70) and for communicating with a monitoring entity (30); a control device (44) designed to control the one or more interfaces (42) and to carry out the method according to any of claims 7 or 8.

12. Communication component (40) according to claim 11, wherein the control device (44) is designed to carry out a registration with the monitoring entity (30).

13. System (80) having at least two monitoring entities (30; 60) according to claim 10 and at least two communication components (40; 50) assigned to the monitoring entities (30; 60) according to any of claims 11 or 12.

14. Vehicle having a system (80) according to claim 13.