IDENTIFICATION FILTERING

Abstract

A control node (112) is introduced. The control node (112) is configured to be connected to at least one other control node (112) via a communication interface (114) that transmits signals between multiple control nodes (112). The signals include identifiers. The control node (112) includes an identifier filter (120). The identifier filter (120) is a hardware filtering device. The identifier filter (120) is configured to receive an identifier sent by another control node (112), to decide whether the identifier is relevant to the control node (112), and, if the identifier is relevant to the control node (112), to perform a task related to the identifier. Furthermore, a method for filtering identifiers, a controller-node network (110) and a use of the control node (112), the method for filtering identifiers or the controller-node network (110) are presented.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a controller node, a method for filtering identifiers, a controller node network, and a use thereof. BACKGROUND

[0002] Control nodes can be used to control a variety of different applications, e.g., in the automotive field, such as engine control electronics or others. Typically, multiple control nodes are interconnected within a network for controlling larger systems, e.g., an entire vehicle or a larger portion of it. As an example, each control node may control a different application within a vehicle, and the control node network may control a larger portion of the vehicle or even the entire vehicle. In an automotive application, a Local Interconnect Network (LIN) is typically used for such a purpose. The Local Interconnect Network may further typically complement a Controller Area Network (CAN). As an example, a master or controller of a Local Interconnect Network may also be connected to a higher-level Controller Area Network.

[0003] For communication, data frames exchanged between control nodes within the control node network may include headers and responses. The header may signal the intent of a new communication. It may also calibrate receive frequencies and prepare receiving control nodes for a response. The control nodes may receive the header and decode its meaning, which may be specifically carried by an identifier that is part of the header. An identifier may describe a response in terms of data length, message meaning, and direction of communication. Each control node in a control node network may be assigned multiple identifiers, e.g., depending on the control node's function within the control node network. As an example, a control node may be configured to control a specific application, e.g.,of a motor, and identifiers related to controlling that motor may be assigned to it.

[0004] Each received identifier must typically be evaluated by the control nodes within the control node network to determine whether or not it is of interest to that specific control node. Many identifiers may not be relevant to a specific control node, but may rather address another control node within the control node network. This evaluation process is usually performed by software in an interrupt request handler. Thus, each interrupt request typically increases the processor load, or in other words, the amount of computation performed by software. This is typically also the case for identifiers that are irrelevant to the respective control node but nevertheless issue such an interrupt request. Thus, there is a particular need to reduce this processor load.

[0005] Document DE 10 2019 111 564 A1 discloses a system and method for configuring a filter object for a controller area network. The method includes determining, by a processor, a plurality of message identifiers of messages to be captured by a filter object. The method also includes factoring a function representing the plurality of message identifiers to generate a simplified function. The method also includes configuring at least one filter object based on the generated simplified function.

[0006] Document EP 1430653 B1 discloses a CAN module with a buffer memory. The buffer memory comprises a data and address input and several addressable buffers, a data receive register coupled to the buffer memory, which receives data from a serial data stream, a filter register, a comparator that compares the value of the filter register with an identifier transmitted in the serial data stream and generates an acceptance signal, a buffer pointer coupled to the comparator, which receives the acceptance signal, and an address register that receives an address from the buffer pointer for addressing the buffer memory. The arrangement can dynamically assign any filter register to any buffer within the buffer memory.

[0007] Document DE 60109060 T2 discloses a method and apparatus for communicating with remote units via at least one data network and with at least one dedicated CPU. The message processing apparatus comprises a first execution unit for receiving a message to be processed and determining the type of processing to be performed on the received message, a second execution unit for performing the determined processing, and a third execution unit for displaying the result of the message processing for forwarding to a destination unit.

[0008] Document EP 1085722 A2 discloses a CAN microcontroller that supports a plurality of uniquely numbered message objects and includes a processor core running CAN applications, a plurality of message buffers associated with the respective message objects, and a CAN / CAL module. The CAN microcontroller further includes a plurality of individual message object registers associated with each message object, including at least one control register containing an interrupt enable control bit, a receive enable bit, and a transmit enable bit.The CAN microcontroller also includes several global message object control registers, including at least one message complete status register containing several status flag bits for the respective message objects, at least one interrupt flag register containing one interrupt flag bit for complete reception and one interrupt flag bit for complete transmission, and a message complete information register containing several message object identification bits and one status bit. SUMMARY

[0009] In a first aspect of the present disclosure, a controller node is presented. The control node is configured to be connected to at least one further control node via a communication interface that transmits signals between multiple control nodes. The signals include identifiers. The control node includes an identifier filter. The identifier filter is a hardware filtering device. The identifier filter is configured to receive an identifier sent from another control node, decide whether the identifier is relevant to the control node, and, if the identifier is relevant to the control node, perform a task related to the identifier.

[0010] In another aspect of the present disclosure, a method for filtering identifiers is presented. The method comprises the following: a) receiving an identifier at an identifier filter of a control node, wherein the identifier filter is a hardware filter device; b) deciding, using the identifier filter, whether the identifier is relevant for the control node; and c) if the identifier is relevant to the control node, performing a task related to the identifier.

[0011] In another aspect of the present disclosure, a controller node network is presented. The controller node network comprises a plurality of controller nodes. The controller node network further comprises a communication interface connecting the controller nodes. The communication interface is configured to transmit signals between the controller nodes. The signals comprise identifiers. At least one controller node comprises an identifier filter. The identifier filter is a hardware filtering device. The identifier filter is configured to receive an identifier sent from another controller node, decide whether the identifier is relevant to the controller node, and, if the identifier is relevant to the controller node, perform a task related to the identifier.

[0012] In a further aspect, a use of the control node and / or the method for filtering identifiers and / or the control node network for an automotive application is presented.

[0013] Those skilled in the art will recognize additional features and advantages upon reading the following detailed description and examining the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like reference numerals refer to similar or identical elements. The elements of the drawings are not necessarily to scale. The features of the various examples shown may be combined, provided they are not mutually exclusive. Fig. 1 schematically illustrates an example of a controller node network and controller nodes according to the present disclosure; Fig. 2 schematically illustrates an example of a tag filter according to the present disclosure; Fig. 3 schematically illustrates another example of a controller node network and controller nodes according to the present disclosure; and Fig. 4 illustrates a flowchart of an example method for filtering identifiers in accordance with the present disclosure. DETAILED DESCRIPTION

[0015] The examples described herein provide significant advantages over the prior art. The control nodes according to the present disclosure include tag filters, which are hardware filtering devices. Thus, a hardware control mechanism can limit the issuance of interrupt requests, which would otherwise increase processor load. Implementing the tag filter in hardware can reduce processor load and responsiveness. Furthermore, it can simplify the software architecture. Common subtasks executed by hardware in the background can provide increased responsiveness and data loss prevention.

[0016] Fig. 1 schematically illustrates an example of a controller node network 110. The control node network 110 includes a plurality of control nodes 112. Although Fig. 1 only explicitly shows four control nodes 112, the control node network 110 can of course in principle have any number of control nodes 112. The control nodes 112 can all be of the same hierarchy or can be at least partially of a different hierarchy. Thus, at least one of the control nodes 112 can be a master control node and at least one of the control nodes 112 can be a slave control node. The terms commander and responder can be used synonymously with the terms master and slave throughout the present disclosure. Thus, at least one control node 112 can be configured to control at least one further control node 112. Furthermore, at least one control node 112 can be configured to control an application, in particular an automotive application, e.g., an engine.At least one of the control nodes 112 may be or may include a microcontroller. However, as indicated, all control nodes 112 may, in principle, also be of the same hierarchy.

[0017] The control node network 110 further comprises a communication interface 114. The communication interface 114 connects the control nodes 112. Thus, the control node network 110 can be an interconnected group of control nodes 112. The communication interface 114 can be or can comprise a bus, in particular a serial bus. The control node network 110 can be a broadcast network, in particular a serial broadcast network. The communication interface 114 can be or can comprise at least one signal line, in particular a data line. In addition, the communication interface 114 can comprise a clock line. However, the communication interface 114 can also be implemented without a separate clock line. The communication interface 114 is configured to transmit signals between the control nodes 112. The signals comprise identifiers.The signals may also include additional components. An exemplary structure of the signals transmitted via the communication interface 114 is shown within the dashed box 116, as indicated by the arrow 118. In particular, the signals may be or may include data frames or at least parts thereof. A data frame may include a header, a configurable response spacing, and a response. Thus, the header and response may be separated by the response spacing.

[0018] The header can initiate communication. A control node 112 can send the header to the other control nodes 112 via the communication interface 114, e.g., when a task is commanded to another control node 112. The other control nodes 112 can all receive the header. The header can include a synchronization interrupt (sync interrupt), a synchronization field (sync field), and the identifier. The synchronization interrupt can be an indication that the control node 112 is starting to send data. The synchronization field can specify the frequency used to send the data. The identifier can specify the type of task to be performed or which of the control nodes 112 is addressed to perform the task. The control nodes 112 can receive and decode the identifier. Thus, each control node 112 can evaluate whether the identifier is relevant to it or not.If a control node 112 determines that the identifier is relevant to it, it can send a corresponding response via the communication interface 114. The response can be or include a transmission, e.g., of requested data. Additionally or alternatively, the response can be or include a reception, such as when rewriting a configuration of the control node 112. Furthermore, the response can include a checksum as a verification measure.

[0019] The identifier may, in particular, be a protected identifier. The protected identifier may include at least one protection measure, in particular at least one verification measure. Thus, the protected identifier may include a parity indicator, in particular at least one parity bit, in particular two parity bits. As an example, the protected identifier may include a total of ten bits, i.e., a start bit, a stop bit, two parity bits, and six identifier bits. The six identifier bits may result in a total of 64 available identifiers that can be sent via the communication interface 114. One available identifier may be reserved for a diagnostic request, one may be reserved for a diagnostic response, and two may be reserved for future use, leaving a total of 60 available identifiers. Thus, a total of 60 identifiers may be available for communication in the control node network 110.However, only a subset of the available identifiers may be relevant for each control node 112. Thus, each control node 112 may need to filter out the identifiers that are irrelevant to it. Instead of using an interrupt request handler implemented in software, this feature can also be implemented in hardware, reducing processor load.

[0020] At least one control node 112 includes an identifier filter 120. The identifier filter 120 is a hardware filter device. The identifier filter 120 is configured to receive an identifier sent from another control node 112. The identifier filter 120 is further configured to decide whether the identifier is relevant to the control node 112. If the identifier is relevant to the control node 112, the identifier filter 120 is configured to perform a task related to the identifier. An identifier relevant to the control node 112 may generally refer to a task that the control node 112 is configured to perform, e.g., controlling a specific application, such as a specific motor. In other words, if the control node 112 can perform a task, a corresponding identifier may be relevant thereto.If the control node 112 cannot perform the task, the corresponding identifier may be irrelevant to it. The identifier filter 120 may be specifically configured to exclude identifiers irrelevant to the control node 112 from issuing an interrupt request. Such an interrupt request may need to be handled by an interrupt request handler, which increases the processor load. Thus, by discarding irrelevant identifiers, or in other words, by preventing them from issuing an interrupt request, the processor load may be reduced. Thus, the identifier filter 120 may be configured to filter out identifiers irrelevant to the control node 112. An identifier irrelevant to the control node 112 may relate to a task that the control node 112 is not configured to perform.

[0021] The tasks may generally include at least one of the following: an operation task; an output task; a diagnostic task; and a configuration task. The operation task may include at least one of the following: a switching operation; a regulation operation; and a measurement operation. As an example, the task may be to turn a motor on or off or to measure motor data, e.g., temperature, pressure, or speed. Accordingly, the output task may include outputting measurement data or control data. The measurement data may be, for example, temperature data, pressure data, or speed data. The diagnostic task may include a self-check of the control node 112 or a check of the controlled application. The configuration task may include changing settings of the control node 112 or the controlled application.As already stated, the control nodes 112 can be used in particular for controlling automotive applications. However, other options besides those mentioned here as examples may, of course, also be generally possible.

[0022] Fig. 2 schematically illustrates an example of an identification filter 120. The identification filter 120 may be part of a control node 112 of the Fig. 1. The identifier filter 120 may comprise at least one identifier register 122. The identifier register 122 may be configured to indicate which identifiers are relevant for the respective control node 112. Thus, the identifier register 122 may be or comprise a lookup table or a list, in particular an enable list, wherein the lookup table or list comprises available identifiers and a corresponding relevance indication for each available identifier. The available identifiers may be identifiers generally used in the control node network 110. As already stated above, for example, a total of 60 identifiers may be available in the control node network. Thus, the identifier register 122 may comprise 60 entries for 60 available identifiers in the control node network. In general, of course, any number n of available identifiers may be possible.

[0023] As explained, each available identifier may be marked by a relevance indication. The relevance indication may generally be a tag that specifies whether the generally available identifier is relevant for the control node 112 having the identifier filter 120. In particular, the relevance indication may be or include at least one enable bit. In particular, the relevance indication may be a 0 as an enable bit, which may indicate that the corresponding available identifier is irrelevant for the control node 112, or a 1 as an enable bit, which may indicate that the corresponding available identifier is relevant for the control node 112. Thus, as an example and as in Fig. 2, a first generally available identifier may be marked with a 0, meaning that this available identifier may be irrelevant to the control node 112. A second available identifier may be marked with a 1, meaning that this available identifier may be relevant to the control node 112, and so on. The enable bits may be stored in a memory device, in particular in flip-flops. Thus, as an example, also considering the available identifier reserved for a diagnostic request, the available identifier reserved for a diagnostic response, and two available identifiers reserved for future use in addition to the 60 generally available identifiers, the identifier filter may comprise 64 flip-flops and may thus also be comparably area-sensitive.In particular, the identifier register 122 can reduce chip area compared to storing an individual list of relevant identifiers for each control node 112.

[0024] In terms of workflow, the control node 112, and in particular the identifier filter 120, may receive an identifier, e.g., after detecting a synchronization interruption and a synchronization field on the communication interface 114. The identifier filter 120 may then compare the received identifier with the entries in the identifier register 122. As stated, an identifier may, for example, in principle comprise ten bits, i.e., a start bit, a stop bit, two parity bits, and six identifier bits. The identifier filter 120 may, in particular, use the six identifier bits for the comparison. The received identifier may be a generally available identifier in the control node network 110. However, the received identifier does not necessarily have to be relevant to the respective control node 112, but rather to another control node 112 of the control node network 110.In such a case, it should be filtered out by the tag filter without issuing an interrupt request, which would increase the processor load. If the received tag is relevant to the control node 112, a corresponding enable bit in the tag register should be set to 1 so that the received tag is not discarded. Thus, if a result of the comparison between the received tag and the tag register 122 indicates that the corresponding enable bit is set to 1 and that the received tag is accordingly relevant to the control node 112, the control node 112 can perform the task related to the tag, e.g., turning an application on or off or outputting data.

[0025] Fig. Figure 3 schematically illustrates another example of a controller node network 110. At least to a large extent, this corresponds to Fig. 3 shown control node network 110 to the one in Fig. 1 shown control node network 110. Thus, for the description of the control node network 110 in Fig. 3 at least to a large extent on the description of the Fig. 1 illustrated control node network 110. Fig. 3 indicates in particular that the control node network 110 may include at least one master control node 312 and at least one slave control node 126. In particular, the control node network 110 may include a master control node 124 and a plurality of slave control nodes 126, in particular up to 15 slave control nodes 126. Although Fig. 3 only explicitly shows five slave control nodes 126, the control node network 110 can of course in principle have any number of slave control nodes 126. In particular, at least the Fig. 3 shown slave control node 126 in Fig. 1. In particular, the slave control nodes 126, or at least some of them, may have identifier filters 120. Thus, the slave control nodes 126 may be configured to filter out identifiers that are irrelevant to them using a hardware mechanism. The identifiers may, in particular, be sent by the master control node 124.

[0026] The master control node 124 can be the master for all slave control nodes 126. However, a multiple-master arrangement is of course also conceivable in principle. The control node network 110 can, in particular, be a Local Interconnect Network (LIN). As stated, the control node network 110 comprises a communication interface 316, in particular a serial bus. The communication interface 314 can connect the master control node 124 and the slave control nodes 126. The master control node 124 can further be connected to a Controller Area Network (CAN) or another backbone network, or at least be configured to be connected thereto. Thus, the control node network 110 can generally be one of several networks, in particular lower-hierarchy networks, connected by a backbone network.In particular, the control node network 110 can be one of several local connection networks in a vehicle. There, the control node network 110 can be used to connect applications in a part of the vehicle, e.g., motors or sensors in a door or seat. The control node network 110, or at least the master control node 124, can then also be part of a higher-hierarchy controller area network that connects the entire vehicle or at least a larger part of the vehicle. In general, the devices and methods presented here can be used in particular in an automotive application, such as for controlling an application in a vehicle, e.g., an engine. However, other uses are of course also conceivable.

[0027] Fig.4 illustrates a flowchart of an example method for filtering identifiers. The method comprises the following steps. The presented method steps may be performed in the order given. However, it should be noted that a different order may also be possible. The method may include additional method steps not listed. Furthermore, one or more of the method steps may be performed once or repeatedly. Furthermore, two or more of the method steps may be performed simultaneously or in an overlapping manner. a) (designated by reference numeral 128) receiving an identifier at an identifier filter 120 of a control node 112, wherein the identifier filter 120 is a hardware filter device; b) (designated by reference numeral 130) deciding, using the identifier filter 120, whether the identifier is relevant to the control node 112; c) (designated by reference numeral 132) if the identifier is relevant to the control node 112, performing a task related to the identifier; and optionally d) (designated by reference numeral 134) if the identifier is irrelevant to the control node 112, discarding the identifier.

[0028] In addition to the examples described above, the following examples are disclosed here: Example 1: A control node configured to be connected to at least one further control node via a communication interface that transmits signals between a plurality of control nodes, the signals comprising identifiers, the control node comprising an identifier filter, the identifier filter being a hardware filtering device and configured to: • Receiving an identifier sent by another control node; • Decide whether the identifier is relevant for the control node; and • if the identifier is relevant to the control node, performing a task related to the identifier. Example 2: The control node according to the preceding example, wherein the task comprises at least one of: an operation task; an output task; a diagnostic task; and a configuration task. Example 3: The control node according to any one of the preceding examples, wherein the task is an operation task comprising at least one of: a switching operation; a regulation operation; and a measurement operation. Example 4: The control node of any preceding example, wherein the task is an output task comprising outputting measurement data selected from the group consisting of: temperature data; pressure data; velocity data. Example 5: The control node according to any one of the preceding examples, wherein the control node is configured to control at least one application, in particular an automotive application, in particular an engine. Example 6: The control node according to any one of the preceding examples, wherein an identifier relevant to the control node relates to a task that the control node is configured to perform. Example 7: The control node according to any one of the preceding examples, wherein the identifier filter is configured to exclude identifiers that are irrelevant to the control node from issuing an interrupt request. Example 8: The control node according to any one of the preceding examples, wherein the identifier filter is configured to filter out identifiers that are irrelevant to the control node. Example 9: The control node according to any one of the preceding examples, wherein the control node is configured to act as a slave control node with respect to the further control node. Example 10: The control node according to any one of the preceding examples, wherein the control node is configured to be part of a control node network comprising a plurality of control nodes, in particular at least one master control node and at least one slave control node. Example 11: The control node according to any one of the preceding examples, wherein the control node is configured to be part of a control node network comprising a plurality of control nodes, in particular at least one master control node and at least one slave control node. Example 12: The control node according to the preceding example, wherein the control node network is a serial broadcast network. Example 13: The control node according to one of the two preceding examples, wherein the control node network is a Local Interconnect Network (LIN). Example 14: The control node according to any one of the preceding examples, wherein the identifier is part of a header. Example 15: The control node according to the preceding example, wherein the header further comprises a synchronization break and a synchronization field. Example 16: The control node according to one of the two preceding examples, wherein the header is part of a data frame. Example 17: The control node according to any one of the three preceding examples, wherein the data frame further comprises a response. Example 18: The control node of any of the four preceding examples, wherein the data frame further comprises a configurable response distance separating the header and the response. Example 19: The control node according to any one of the preceding examples, wherein the signals transmitted via the communication interface comprise data frames or at least parts thereof. Example 20: The control node according to any one of the preceding examples, wherein the identifier is a protected identifier, wherein the protected identifier has at least one protection measure, in particular at least one verification measure. Example 21: The control node according to the preceding example, wherein the protected identifier comprises a parity indicator, in particular at least one parity bit, in particular two parity bits. Example 22: The control node according to any one of the preceding examples, wherein the identifier filter comprises an identifier register indicating which identifiers are relevant to the control node. Example 23: The control node according to the preceding example, wherein the identifier register is a lookup table comprising available identifiers and a corresponding relevance indication for each available identifier. Example 24: The control node according to the preceding example, wherein the relevance indication comprises an enable bit for each available identifier. Example 25: The control node according to the preceding example, wherein the identification register comprises at least one storage device, in particular a flip-flop, wherein the enable bit is stored using the storage device. Example 26: The control node according to any one of the preceding examples, wherein the control node is a microprocessor. Example 27: A method for filtering identifiers, comprising: a) receiving an identifier at an identifier filter of a control node, wherein the identifier filter is a hardware filter device; b) deciding, using the identifier filter, whether the identifier is relevant for the control node; and c) if the identifier is relevant to the control node, performing a task related to the identifier. Example 28: The method according to the preceding example, wherein the control node is a control node according to any of the preceding examples relating to a control node. Example 29: The method according to any one of the preceding method examples, further comprising: d) if the identifier is irrelevant for the control node, discard the identifier. Example 30: A control node network that has the following: • a plurality of control nodes; and • a communication interface connecting the control nodes, the communication interface being configured to transmit signals between the control nodes, the signals comprising identifiers, wherein at least one control node comprises an identifier filter, wherein the identifier filter is a hardware filter device and is configured to: • Receiving an identifier sent by another control node; • Decide whether the identifier is relevant for the control node; and • if the identifier is relevant to the control node, performing a task related to the identifier. Example 31: The control node network according to the preceding example, wherein the control node having the identifier filter is a control node according to any of the preceding examples relating to a control node. Example 32: The control node network according to any one of the preceding examples relating to a control node network, wherein the control node network is a serial broadcast network. Example 33: The control node network according to any one of the preceding examples relating to a control node network, wherein the control node network is a Local Interconnect Network (LIN). Example 34: The control node network according to any one of the preceding examples relating to a control node network, wherein the control node having an identifier filter is a slave control node with respect to the further control node sending the identifier. Example 35: The control node network according to any one of the preceding examples relating to a control node network, wherein the control node network comprises a control node acting as a master control node with respect to all other control nodes of the control node network. Example 36: The control node network according to the preceding example, wherein the control node acting as a master control node with respect to all other control nodes is further connected to a Controller Area Network (CAN). Example 37: The control node network according to any one of the preceding examples relating to a control node network, wherein the communication interface comprises a bus, in particular a serial bus. Example 38: The control node network according to any one of the preceding examples relating to a control node network, wherein at least one of the control nodes is a microcontroller. Example 39: A use for an automotive application of at least one of a control node according to any one of the preceding examples relating to a control node, a method for filtering identifiers according to any one of the preceding method examples, and a control node network according to any one of the preceding examples relating to a control node network.

[0029] Although specific examples have been illustrated and described herein, those skilled in the art will recognize that a variety of alternative and / or equivalent implementations may be substituted for the specific examples shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the specific examples discussed herein. Therefore, this disclosure is intended to be limited only by the claims and their equivalents.

[0030] It should be noted that the methods and devices, including their preferred embodiments, as set forth in this document can be used independently or in combination with the other methods and devices disclosed in this document. Furthermore, the features set forth in the context of a device are also applicable to a corresponding method, and vice versa. Furthermore, all aspects of the methods and devices set forth in this document can be combined in any way. In particular, the features of the claims can be combined with one another in any way.

[0031] It should be noted that the description and drawings merely illustrate the principles of the proposed methods and systems. Those skilled in the art will be able to implement various arrangements that, although not explicitly described or shown herein, embody the principles of the disclosure and are included within its spirit and scope. Furthermore, all examples and embodiments set forth in the present document are primarily intended to be expressly provided for illustrative purposes only to assist the reader in understanding the principles of the proposed methods and systems. Furthermore, all statements herein that provide principles, aspects, and embodiments of the disclosure, as well as specific examples thereof, are intended to include their equivalents.

Claims

[1] A control node (112) configured to be connected to at least one further control node (112) via a communication interface (114) that transmits signals between a plurality of control nodes (112), wherein the control node (112) is configured to act as a slave control node (126) with respect to the further control node (112), wherein the signals comprise identifiers, wherein the control node (112) comprises an identifier filter (120), wherein the identifier filter (120) is a hardware filtering device and is configured to: • receiving an identifier sent from another control node (112); • Deciding whether the identifier is relevant to the control node (112); and • if the identifier is relevant to the control node (112), performing a task related to the identifier. [2] The control node (112) according to the preceding claim, wherein the task comprises at least one of: an operation task; an output task; a diagnostic task; a configuration task. [3] The control node (112) according to any one of the preceding claims, wherein an identifier relevant to the control node (112) relates to a task that the control node (112) is configured to perform. [4] The control node (112) according to any one of the preceding claims, wherein the identifier filter is configured to exclude identifiers irrelevant to the control node (112) from issuing an interrupt request. [5] The control node (112) according to any one of the preceding claims, wherein the control node (112) is configured to be part of a control node network (110) comprising a plurality of control nodes (112), in particular at least one master control node (124) and at least one slave control node (126). [6] The control node (112) of any preceding claim, wherein the identifier is part of a header, the header further comprising a synchronization break and a synchronization field, the header being part of a data frame, the data frame further comprising a response, the data frame further comprising a configurable response distance separating the header and the response. [7] The control node (112) according to one of the preceding claims, wherein the identifier is a protected identifier, wherein the protected identifier has at least one protection measure, in particular at least one verification measure. [8] The control node (112) according to the preceding claim, wherein the protected identifier comprises a parity indicator, in particular at least one parity bit, in particular two parity bits. [9] The control node (112) according to any one of the preceding claims, wherein the identifier filter (120) comprises an identifier register (122) that indicates which identifiers are relevant to the control node (112). [10] The control node (112) according to the preceding claim, wherein the identifier register (122) is a lookup table comprising available identifiers and a corresponding relevance indication for each available identifier. [11] The control node (112) according to the preceding claim, wherein the relevance indication comprises an enable bit for each available identifier. [12] A method for filtering identifiers, comprising: a) receiving an identifier at an identifier filter (120) of a control node (112) acting as a slave control node (126) with respect to another control node (112), the identifier filter (120) being a hardware filter device; b) deciding, using the identifier filter (120), whether the identifier is relevant for the control node (112); and c) if the identifier is relevant to the control node (112), performing a task related to the identifier. [13] A control node network (110) comprising: • a plurality of control nodes (112); and • a communication interface (114) connecting the control nodes (112), the communication interface (114) being configured to transmit signals between the control nodes (112), the signals comprising identifiers, wherein at least one control node (112) is configured to act as a slave control node (126) with respect to another control node (112), wherein the control node (112) comprises an identifier filter (120), wherein the identifier filter (120) is a hardware filter device and is configured to: • receiving an identifier sent from another control node (112); • Deciding whether the identifier is relevant to the control node (112); and • if the identifier is relevant to the control node (112), performing a task related to the identifier. [14] The control node network (110) according to the preceding claim, wherein the control node network (110) is a Local Interconnect Network (LIN). [15] The control node network (110) according to any one of the preceding claims relating to a control node network (110), wherein the control node network (110) comprises a control node (112) acting as a master control node (124) with respect to all other control nodes (112) of the control node network (110). [16] The control node network (110) according to the preceding claim, wherein the control node (112) acting as a master control node (124) with respect to all other control nodes (112) is further connected to a Controller Area Network (CAN). [17] The control node network (110) according to any one of the preceding claims relating to a control node network (110), wherein the communication interface (114) comprises a bus, in particular a serial bus. [18] The control node network (110) according to any one of the preceding claims relating to a control node network (110), wherein at least one of the control nodes (112) is a microcontroller. [19] A use for an automotive application of at least one of a control node (112) according to any one of the preceding claims relating to a control node (112), a method of filtering identifiers according to any one of the preceding method claims, and a control node network (110) according to any one of the preceding claims relating to a control node network (110).

Images