Apparatus and method for processing data unit

By introducing a hardware circuit inspection device into the data unit processing device, flexible and efficient security inspection of protocol data units is achieved, the problems of insufficient inspection flexibility and hardware protection in the prior art are solved, and the security of the equipment is improved. Processing capability.

CN118975198APending Publication Date: 2024-11-15ROBERT BOSCH GMBH
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202380032226.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-01
Filing Date
2023-03-31
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

It is difficult for existing data unit processing equipment to effectively conduct flexible and efficient security checks, especially when facing multiple protocol data units, it is difficult to achieve efficient hardware-based inspections and protection against software attacks.

Method used

A device is designed with an input interface and an optional output interface, equipped with a checking device of hardware circuits, capable of performing non-state-based and state-based security checks, and selectively checking the protocol through bit flags and control information Data unit, supports flexible processing and routing of data units of different protocols.

Benefits of technology

It realizes efficient security checks and processing of protocol data units, improves the flexibility and security of the equipment, and can effectively prevent software-based attacks. It is suitable for a variety of protocol data units, including SOME/IP and other types of protocol data units. .

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975198A_ABST
    Figure CN118975198A_ABST
Patent Text Reader

Abstract

A device for processing data units, for example protocol data units, has a first number of input interfaces for receiving protocol data units; and optionally, a second number of output interfaces for outputting protocol data units; and an inspection device which is designed to inspect the at least one received protocol data unit, the inspection device being designed to at least temporarily perform at least one of the following inspections: a) a non-state-based inspection; and b) checking based on the state.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to an apparatus for processing a data unit.

[0002] The present disclosure also relates to a method for processing a data unit. Summary of the invention

[0003] An exemplary embodiment relates to a device for processing data units, such as protocol data units, the device having: a first number of input interfaces for receiving protocol data units; and optionally, a second number of output interfaces for outputting protocol data units; and a checking device, such as a firewall device, which is designed to check at least one received protocol data unit, such as subjecting the at least one received protocol data unit to a security check, wherein the checking device is designed to at least temporarily perform at least one of the following checks: a) a non-state-based, such as a non-state-oriented, such as a stateless check, such as with respect to the at least one received protocol data unit; b) a state-based, such as a state-oriented, such as a stateful check, such as with respect to the at least one received protocol data unit. Thus, in other exemplary embodiments, the flexibility regarding the checks can be increased.

[0004] In other exemplary embodiments, the first number is greater than or equal to one. In other exemplary embodiments, the second number is greater than or equal to one.

[0005] In a further exemplary embodiment, it is provided that the checking device is designed as a hardware circuit, for example as a pure hardware circuit. This enables efficient hardware-based checking, for example according to prescribable (and / or learnable) firewall rules or security rules, for example regarding protocol data units that can potentially be processed by the device. Furthermore, software-based attacks on the hardware checking device or hardware firewall are ineffective.

[0006] In other exemplary embodiments, it is provided that the checking device is designed to selectively check the at least one received protocol data unit, for example based on first control information, such as a bit flag. In other words, the checking device can, for example, temporarily check the received protocol data unit, for example based on control information that can be provided by another component of the device, and the checking device, for example, temporarily does not perform a check of the protocol data unit. In other exemplary embodiments, for example, by the device or another component of the device (in addition to the checking device), it can be controlled whether, for example, a specific protocol data unit is to be checked, for example, a protocol data unit corresponding to at least one specifiable standard. Alternatively or in addition, by the checking device, it can be controlled whether, for example, a specific protocol data unit is to be checked.

[0007] In other exemplary embodiments, it is provided that the checking device is designed to check at least some of the received protocol data units, for example all received protocol data units.

[0008] In other exemplary embodiments, it is provided that the checking device is designed to: subject at least some of the received protocol data units to a non-state-based check; and, for example based on the result of the non-state-based check, subject at least some of the received protocol data units to a state-based check.

[0009] In other exemplary embodiments, it is provided that the checking device is designed to check protocol data units that are associated with at least one protocol operating on layer 5 of the ISO / OSI reference model, for example at least one service-oriented protocol, such as protocol data units associated with the Scalable Service-Oriented Middleware over IP protocol, i.e., the SOME / IP protocol.

[0010] In other exemplary embodiments, protocol data units associated with at least one other protocol and / or other types of protocol data units, such as L-PDU, I-PDU, N-PDU, S-PDU, can also be checked.

[0011] In other exemplary embodiments, it is provided that the checking device is designed to check, during the checking, for example during a non-state-based checking, at least one of the following elements, for example header data, for example header data, for example at least one of the following elements of a protocol data unit associated with the SOME / IP protocol:

[0012] a) a message identification, such as a message ID (Message ID), for example, being associated with at least one assignable valid message identification or message ID, wherein the at least one assignable valid message identification can be organized, for example, in the form of a table, wherein, for example, the message ID is checked to determine whether the message ID is an assignable valid message ID;

[0013] b) a service identifier, such as a service ID (wherein, for example, the check on the service ID includes: determining whether the service ID is a valid service ID that can be specified);

[0014] c) method ID (Method ID) (wherein, for example, the method ID is checked to determine whether the method ID is a valid method ID that can be specified);

[0015] d) a length, for example relating to a prescribable length (wherein, for example, a check of the length includes determining, for example, whether the length corresponds to a prescribable (for example, valid) length);

[0016] e) a request identification, such as a request ID (Request-ID), for example related to a specifiable value (wherein, for example, the check of the request ID includes: determining whether the request ID is a valid request ID that can be specified);

[0017] f) a client identification, such as a client ID (Client-ID) (wherein, for example, the checking of the client ID includes: determining whether the client ID is a valid client ID that can be specified);

[0018] g) a session identifier, such as a session ID (wherein, for example, the checking of the session ID includes: determining whether the session ID is a valid session ID that can be specified);

[0019] h) protocol version (e.g. by determining whether the protocol version corresponds to a valid protocol version that can be specified);

[0020] i) an interface version, such as Interface Version (e.g. by determining whether the interface version corresponds to a valid interface version that can be specified);

[0021] j) a type, such as a message type, such as a Message Type (eg by determining whether the message type corresponds to a valid message type that can be specified);

[0022] j) a return value, such as a return code, such as a Return Code (eg by determining whether the Return Code corresponds to a valid return code that can be specified).

[0023] In other exemplary embodiments, it is provided that the checking device is designed, for example within the framework of a condition-based check, to check:

[0024] a) whether a response message, such as a Response Message, is received after sending a request message, such as a request message associated with a response message, such as a RequestMessage; and / or

[0025] b) whether the received response message, such as Response Message, is associated with a previously sent request message; and / or

[0026] c) Whether the received response message is received within a specifiable response time, the response time being related to sending a request message associated with the response message.

[0027] In other exemplary embodiments, it is provided that the checking device is designed to determine the message type of at least one SOME / IP message associated with at least one received protocol data unit, wherein, for example, the message type has at least one of the following elements: a) REQUEST; b) REQUEST_NO_RETURN; c) NOTIFICATION; d) RESPONSE; e) ERROR; f) TP_REQUEST; g) TP_REQUEST_NO_RETURN; h) TP_NOTIFICATION; i) TP_RESPONSE; j) TP_ERROR.

[0028] In other exemplary embodiments, it is provided that the checking device is designed to determine a service type of at least one SOME / IP message associated with at least one received protocol data unit, wherein, for example, the service type has at least one of the following elements: a) RPC, i.e., remote procedure call; b) Fire & Forget; c) Notify.

[0029] In other exemplary embodiments, it is provided that the checking device is designed to, for example, based on the at least one received protocol data unit, perform a state-based and / or state-oriented evaluation of at least one SOME / IP service, for example a state-based and / or state-oriented evaluation of remote procedure calls, which have, for example, request elements and / or response elements.

[0030] In other exemplary embodiments, it is provided that the checking device is designed to at least temporarily also carry out a non-state-based and / or non-state-oriented evaluation, for example a non-state-based and / or non-state-oriented evaluation of a SOME / IP service.

[0031] In other exemplary embodiments, it is provided that the checking device is designed to discard or not discard the at least one received protocol data unit, for example leaving it unchanged, for example based on the checking, for example when the result of the checking can infer an attack attempt or a malicious data unit.

[0032] In other exemplary embodiments, it is provided that the checking device is designed to: for example, based on the checking, for example, when the result of the checking can infer that there is no attack attempt or no malicious data unit, not discard the at least one received protocol data unit, for example, forward the at least one received protocol data unit, for example, for output, for example, to another unit.

[0033] In other exemplary embodiments, it is provided that the checking device is designed to modify or influence the at least one received protocol data unit and / or the output of the at least one received protocol data unit, for example via an output interface, for example in order to cause a unicast output or a multicast output.

[0034] In other exemplary embodiments, it is provided that the inspection device is designed to perform at least one of the following elements:

[0035] a) attack identification, such as intrusion detection, and / or attack identification and attack prevention, such as intrusion detection and prevention;

[0036] b) marking the at least one received protocol data unit, e.g. based on the checking and / or based on a result of the checking;

[0037] c) outputting and / or forwarding the at least one received protocol data unit, for example by means of a multicast mechanism, for example to at least one software component, for example for evaluation or execution, for example further evaluation or execution, of an attack identification, for example software-based attack identification;

[0038] d) outputting and / or forwarding the at least one received protocol data unit, e.g. by means of a unicast mechanism, e.g. to at least one software component or the at least one software component, e.g. for evaluation or execution, e.g. further evaluation or execution, of attack identification, e.g. software-based attack identification;

[0039] e) determining and / or evaluating service identification messages, such as service discovery messages, which are based on a network protocol, such as a connectionless network protocol, such as a user datagram protocol, UDP;

[0040] f) Determining and / or evaluating a protocol data unit of the AUTOSARI PDU type, for example for a check, for example a safety check.

[0041] In other exemplary embodiments, it is provided that the device has a processing device, which is designed to: based on the PDU identifier associated with the received protocol data unit, perform a search in at least one first search tree, the first search tree having an assignment of each PDU identifier to a connection identifier representing at least one data connection, wherein, for example, the search can be performed before the check and / or after the check and / or at least partially overlapped with the check in time. In other exemplary embodiments, the search can be used, for example, for routing, for example forwarding, of data units.

[0042] In other exemplary embodiments, for example, if the checking occurs before the searching, the searching may be performed, for example, based on the results of the checking.

[0043] In other exemplary embodiments, for example, if the check occurs after the search, the check can be performed, for example, based on the result of the search, for example, based on the connection identifier, and / or based on information associated with the connection identifier. Thereby, in other exemplary embodiments, for example, it can be achieved that for a specific connection identifier, the relevant data unit is checked by means of the checking device, wherein, for example, for other connection identifiers, the relevant data unit is not checked by means of the checking device.

[0044] In other exemplary embodiments, it is provided that the device is designed to determine, based on the received protocol data unit, a connection identifier associated with the received protocol data unit, wherein, for example, the determination can be performed before the check and / or after the check and / or at least partially overlap in time with the check.

[0045] In a further exemplary embodiment, it is provided that the processing device has at least one hardware component which is designed to carry out the search in the first search tree and / or to determine a connection identifier associated with the received protocol data unit. For example, a hardware-based search can be carried out particularly quickly and efficiently and - like a hardware-based (firewall) check of data units - is insensitive to software-based attack attempts.

[0046] In other exemplary embodiments, it is provided that the first search tree is a binary tree.

[0047] In other exemplary embodiments, it is provided that the processing device has at least one software component, wherein the software component is designed to execute at least one of the following elements:

[0048] a) at least temporarily forming a first search tree;

[0049] b) at least temporarily modifying, for example balancing, the first search tree;

[0050] c) receiving at least one protocol data unit from the checking device (e.g. if, based on the result of the checking of the protocol data unit by the checking device, it is concluded that a software-based checking of the protocol data unit, e.g. a further software-based checking, should be performed);

[0051] d) Evaluating, e.g., performing attack identification, e.g., software-based attack identification.

[0052] In a further exemplary embodiment, it is provided that the at least one software component is designed to execute a specifiable reaction if a connection identifier associated with the received protocol data unit cannot be determined for the received protocol data unit, for example if a connection identifier associated with the received protocol data unit is not present in the first search tree for the received protocol data unit, wherein the specifiable reaction has, for example, at least one of the following elements:

[0053] a) discarding the received protocol data unit;

[0054] b) assigning a connection identifier, for example a configurable connection identifier, to the received protocol data unit;

[0055] c) setting or inserting first information or first control information for the received protocol data unit, for example in the form of a bit flag, wherein the first information and / or the first control information, for example, indicates that the received protocol data unit should be subject to inspection, for example by means of an inspection device, such as a firewall device.

[0056] In other exemplary embodiments, it is provided that the checking device is designed to evaluate the first information and / or the first control information and, based thereon, to carry out or not to carry out a check of the relevant data unit.

[0057] In other exemplary embodiments, it is provided that the device has at least one memory for at least temporarily storing one or more protocol data units or parts of one or more protocol data units.

[0058] In a further exemplary embodiment, it is provided that the device has a regulating device which is designed to change a PDU identifier associated with a received protocol data unit, for example to normalize it.

[0059] In other exemplary embodiments, it is provided that at least one data structure of the search tree, such as a node structure, has an attribute that indicates whether a security check, such as a security check by means of the checking device, should be performed for the relevant protocol data unit or for the protocol data unit associated with the connection identifier. For example, the attribute can correspond to the first information or the first control information.

[0060] In other exemplary embodiments, it is provided that the checking device is designed to use a connection identifier associated with a received protocol data unit or the connection identifier associated with the received protocol data unit, for example to determine a service and / or identifier associated with, for example, at least one received protocol data unit.

[0061] Further exemplary embodiments relate to a method, for example a computer-implemented method, for processing a data unit, for example a protocol data unit, for a device, for example according to at least one of the preceding claims, comprising:

[0062] a first number of input interfaces for receiving protocol data units; and optionally a second number of output interfaces for outputting protocol data units; and a checking device, such as a firewall device, which is designed to check at least one received protocol data unit, such as to subject it to a security check, wherein the method comprises:

[0063] receiving at least one protocol data unit;

[0064] By means of the checking device, at least one received protocol data unit is checked, wherein the checking device at least temporarily performs at least one of the following checks:

[0065] a) a non-state-based, e.g. non-state-oriented, e.g. stateless, checking, e.g. with respect to the at least one received protocol data unit;

[0066] b) A status-based, eg state-oriented, eg stateful, check, eg with respect to the at least one received protocol data unit.

[0067] In other exemplary embodiments, it is provided that the method has at least one of the following elements:

[0068] a) outputting at least one protocol data unit, e.g. based on the checking;

[0069] b) discarding at least one protocol data unit, for example based on the checking.

[0070] In other exemplary embodiments, it is provided that the checking device subjects at least some of the received protocol data units to a non-state-based check and, for example based on the result of the non-state-based check, subjects at least some of the received protocol data units to a state-based check.

[0071] In other exemplary embodiments, it is provided that the checking device modifies or influences the at least one received protocol data unit and / or the output of the at least one received protocol data unit, for example via an output interface.

[0072] In other exemplary embodiments, it is provided that the inspection device performs at least one of the following elements:

[0073] a) Attack identification, such as intrusion detection;

[0074] b) marking the at least one received protocol data unit, e.g. based on the checking and / or based on a result of the checking;

[0075] c) outputting and / or forwarding the at least one received protocol data unit, for example by means of a multicast mechanism, for example to at least one software component, for example for evaluation or execution, for example further evaluation or execution, of an attack identification, for example software-based attack identification;

[0076] d) outputting and / or forwarding the at least one received protocol data unit, e.g. by means of a unicast mechanism, e.g. to at least one software component or the at least one software component, e.g. for evaluation or execution, e.g. further evaluation or execution, of attack identification, e.g. software-based attack identification;

[0077] e) determining and / or evaluating service identification messages, such as service discovery messages, which are based on a network protocol, such as a connectionless network protocol, such as a user datagram protocol, UDP;

[0078] f) Determining and / or evaluating a protocol data unit of the AUTOSARI PDU type, for example for a check, for example a safety check.

[0079] In other exemplary embodiments, it is provided that the method has at least one of the following elements:

[0080] a) receiving data, for example in the form of data frames;

[0081] b) determining an endpoint associated with the reception of data, for example an input interface associated with the reception of data, for example a socket, for example a User Datagram Protocol (UDP) socket, for example by means of a ternary content addressable memory TCAM (or for example by means of a tree structure, for example a search tree);

[0082] c) decomposing, for example splitting, the data frame into at least one protocol data unit, for example, an S-PDU;

[0083] d) assigning an identifier characterizing the endpoint to the at least one protocol data unit;

[0084] e) checking, for example, by means of the device or the checking device, at least one of the following elements of at least one protocol data unit, for example, an S-PDU: e1) a message identifier, for example, a message ID, e2) a request identifier, for example, a request ID, e3) a protocol version, e4) an interface version, for example, an Interface Version, e5) a type, for example, a message type, for example, a Message Type;

[0085] f) Based on the check, f1) output or forward the data, for example in the form of a data frame, or f2a) discard the data, for example the data frame and / or f2b) increment a counter.

[0086] In other exemplary embodiments, it is provided that the method has at least one of the following elements:

[0087] a) receiving data, for example in the form of data frames;

[0088] b) determining an endpoint associated with receiving data, for example an input interface associated with receiving data, such as a socket, for example a Controller Area Network (CAN) socket, for example by means of a ternary content addressable memory (TCAM);

[0089] c) decomposing the data frame into at least one protocol data unit, such as an I-PDU;

[0090] d) assigning an identifier characterizing the endpoint to the at least one protocol data unit;

[0091] e) checking, for example, by means of the device or the checking means, at least one of the following elements of at least one protocol data unit, for example an I-PDU: e1) a message identifier, for example a message ID, e2) a length;

[0092] f) Based on the check, f1) output or forward the data, for example in the form of a data frame, or f2a) discard the data, for example the data frame and / or f2b) increment a counter.

[0093] Further exemplary embodiments relate to a device for carrying out the method according to these embodiments.

[0094] Other exemplary embodiments relate to a computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform at least some of the steps of the methods described in accordance with these embodiments.

[0095] Other exemplary embodiments relate to a computer program comprising instructions which, when executed by a computer, cause the computer to carry out at least some of the steps of the methods described in accordance with these embodiments.

[0096] Further exemplary embodiments relate to a data carrier signal which transmits and / or represents a computer program according to these embodiments.

[0097] Further exemplary embodiments relate to a gateway, for example an automotive gateway, which has at least one device according to the embodiments.

[0098] Other exemplary embodiments relate to the use of the apparatus according to these embodiments and / or the method according to these embodiments and / or the computer-readable storage medium according to these embodiments and / or the computer program according to these embodiments and / or the data carrier signal according to these embodiments and / or the gateway according to these embodiments for at least one of the following elements:

[0099] a) processing data units, such as data units of a vehicle (such as a motor vehicle), such as protocol data units;

[0100] b) determining, for example searching for, a connection identifier associated with the received protocol data unit, for example by means of a hardware component;

[0101] c) managing at least one search tree;

[0102] d) performing a hardware-based search for a connection identifier of a data unit, for example a data unit of a gateway for an automotive application, for example a protocol data unit, wherein the search can be performed with a logarithmic workload, for example;

[0103] e) routing or communicating data units, such as data units of a vehicle (such as a motor vehicle), such as protocol data units, wherein, for example, these data units may be of different types;

[0104] f) assigning a connection identifier, for example a protocol-independent connection identifier;

[0105] g) performing multicast transmission;

[0106] h) determining whether, for a specifiable received data unit (eg protocol data unit), no connection identifier is provided, eg registered, eg whether the connection identifier is not contained in a search tree;

[0107] i) software-based processing of received data units (e.g. protocol data units) for which no connection identifier is provided, e.g. registered, e.g. contains a connection identifier in a search tree;

[0108] j) checking the at least one received protocol data unit, for example performing a security check;

[0109] k) hardware-based firewall inspection of protocol data units associated with at least one protocol operating at layer 5 of the ISO / OSI reference model, such as at least one service-oriented protocol, such as protocol data units associated with the Scalable Service-Oriented Middleware over IP (SOME / IP) protocol;

[0110] 1) Selectively applying a routing function, such as a forwarding function, and / or a firewall function to the protocol data unit. BRIEF DESCRIPTION OF THE DRAWINGS

[0111] Further features, applications and advantages of the invention are apparent from the following description of exemplary embodiments of the invention, which are shown in the figures of the accompanying drawings. All described or illustrated features form the subject matter of the invention by themselves or in any combination, regardless of their summary in the claims or their reference back to them and regardless of their expression or presentation in the description or in the drawings.

[0112] In the attached picture:

[0113] Figure 1 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0114] Figure 2A A simplified flow chart according to an exemplary embodiment is schematically shown;

[0115] Figure 2B A simplified flow chart according to an exemplary embodiment is schematically shown;

[0116] Figure 2CSchematically shows a simplified block diagram according to an exemplary embodiment;

[0117] Figure 2D A simplified flow chart according to an exemplary embodiment is schematically shown;

[0118] Figure 3 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0119] Figure 4 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0120] Figure 5 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0121] Figure 6 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0122] Figure 7 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0123] Figure 8 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0124] Fig. 9 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0125] Fig.10 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0126] Fig.11 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0127] Fig.12 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0128] Fig.13 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0129] Fig.14 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0130] Fig.15 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0131] Fig.16 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0132] Fig.17A simplified flow chart according to an exemplary embodiment is schematically shown;

[0133] Fig.18 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0134] Fig.19 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0135] Fig. 20 A simplified flow chart according to an exemplary embodiment is schematically shown;

[0136] Fig.21 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0137] Fig. 22 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0138] Fig.23 Schematically illustrates aspects of application according to exemplary embodiments;

[0139] Fig.24A A simplified flow chart according to an exemplary embodiment is schematically shown;

[0140] Fig. 24B A simplified flow chart according to an exemplary embodiment is schematically shown;

[0141] Fig.25A A simplified flow chart according to an exemplary embodiment is schematically shown;

[0142] Fig.25B A simplified flow chart according to an exemplary embodiment is schematically shown;

[0143] Fig.26 Schematically shows a simplified block diagram according to an exemplary embodiment;

[0144] Fig. 27 A simplified signaling diagram according to an exemplary embodiment is schematically shown. DETAILED DESCRIPTION

[0145] For an exemplary embodiment, see Figure 1, relates to a device 100 for processing a data unit PDU-1, such as a protocol data unit, the device having: a first number of input interfaces 110 for receiving the protocol data unit PDU-1; and optionally, a second number of output interfaces 120 for outputting the protocol data unit; and an inspection device 125, such as a firewall device (hereinafter referred to as "firewall"), which is designed to inspect at least one received protocol data unit PDU-1, such as subjecting the at least one received protocol data unit to a security inspection, wherein the inspection device 125 is designed to: at least temporarily perform at least one of the following inspections: a) for example, a non-state-based, such as a non-state-oriented, such as a stateless inspection, with respect to the at least one received protocol data unit PDU-1; b) for example, a state-based, such as a state-oriented, such as a stateful inspection, with respect to the at least one received protocol data unit PDU-1. Thus, in other exemplary embodiments, the flexibility regarding the inspection can be increased.

[0146] In other exemplary embodiments, the first number is greater than or equal to one. In other exemplary embodiments, the second number is greater than or equal to one.

[0147] exist Figure 2A , a flow chart of a corresponding method according to an exemplary embodiment is shown, wherein block 10 represents the reception of at least one protocol data unit PDU-1, and wherein block 12 represents an optional check. Block 12a exemplarily represents a non-state-based check, and block 12b exemplarily represents a state-based check. Blocks 14, 15 exemplarily represent optional further operations of the device 100, for example based on the check 12.

[0148] In other exemplary embodiments, it is provided that the checking device 125 is designed as a hardware circuit, for example a pure hardware circuit, i.e., for example without software. This enables an efficient hardware-based checking 12, for example according to prescribable (and / or learnable or (hard) programmable) firewall rules or security rules, for example with respect to protocol data units PDU-1 that can potentially be processed by the device 100. In addition, software-based attacks on the hardware checking device 125 or the hardware firewall are ineffective.

[0149] In other exemplary embodiments, it is provided that the inspection device 125 ( Figure 1) is designed to selectively check the at least one received protocol data unit PDU-1, for example based on the first control information SI-1, for example a bit flag or which can be represented by a bit flag. In other words, the checking means 125 can, for example, temporarily check the received protocol data unit PDU-1, for example based on the fact that it can be detected by another component 130 of the device 100 (see below). Figure 7 ) provides control information SI-1, and the checking device 125 does not perform the checking of the protocol data unit temporarily, for example. In other exemplary embodiments, for example, by the device 100 or another component 130 ( Figure 7 ) (in addition to the checking device 125), it is possible to control, for example, whether a specific protocol data unit, for example a protocol data unit corresponding to at least one specifiable standard, is to be checked. Alternatively or additionally, it is possible to control, for example, whether a specific protocol data unit is to be checked by the checking device 125 itself.

[0150] In other exemplary embodiments, it is provided that the checking device 125 is designed to check at least some of the received protocol data units PDU- 1 , for example all received protocol data units.

[0151] In other exemplary embodiments, see Figure 2B , it is stipulated that: the inspection device 125 ( Figure 1 ) is designed to subject at least some received protocol data units to non-state-based inspection 12a ( Figure 2A ), see Figure 2B and, for example, based on the result of the non-state-based check 12a, 1200 ERG-12a, subjecting at least some of the received protocol data units to a state-based check 12b, see in accordance with Figure 2B Block 1202 of . Exemplarily, based on the check 12b , 1202 of the state, a further result ERG- 12b is obtained, which in other exemplary embodiments can be evaluated together with the result ERG- 12a , for example.

[0152] In other exemplary embodiments, it is provided that the checking device 125 is designed to check protocol data units that are associated with at least one protocol operating on layer 5 of the ISO / OSI reference model, for example at least one service-oriented protocol, such as protocol data units associated with the Scalable Service-Oriented Middleware over IP protocol, i.e., the SOME / IP protocol.

[0153] In other exemplary embodiments, it is provided that the checking device 125 is designed to (also) check data units associated with other, possibly higher or lower ISO / OSI layers.

[0154] In other exemplary embodiments, see Figure 2A For example, by means of the checking device 125, protocol data units associated with at least one other protocol and / or other types of protocol data units, such as L-PDU, I-PDU, N-PDU, S-PDU, can also be checked.

[0155] Figure 2C A simplified block diagram according to an exemplary embodiment is schematically shown, which represents an exemplary header data format, such as a header format, such as a header data format of the SOME / IP protocol, wherein row ZE1 indicates a bit state, such as a bit offset, wherein area BER1 represents a SOME / IP header, and wherein area BER2 represents a data field represented by a length H2.

[0156] In other exemplary embodiments, see Figure 2C , it is stipulated that: the inspection device 125 ( Figure 1 ) is designed to: during the check 12, for example during the non-state-based check 12a, check at least one of the following elements, for example header data, for example header data, for example at least one of the following elements of a protocol data unit associated with the SOME / IP protocol:

[0157] a) a message identifier H1 (e.g., having 32 bits), e.g., a message ID (Message ID), e.g., associated with at least one assignable valid message identifier or message ID, wherein the at least one assignable valid message identifier can be organized, for example, in the form of a table, wherein, for example, a check of the message ID includes: determining whether the message ID H1 is an assignable valid message ID;

[0158] b) a service identifier H1a, such as a service ID (wherein, for example, the check on the service ID H1a includes: determining whether the service ID H1a is a valid service ID that can be specified);

[0159] c) method ID H1b (wherein, for example, the checking of the method ID H1b includes: determining whether the method ID H1b is a valid method ID that can be specified);

[0160] d) a length H2, for example, which is related to a prescribable length (wherein, for example, the length H2 is checked by determining whether the length H2 corresponds to a prescribable (for example, valid) length);

[0161] e) a request identifier H3, such as a request ID, for example having 32 bits, for example being associated with a specifiable value (wherein, for example, the check on the request ID H3 includes: determining whether the request ID H3 is a valid request ID that can be specified);

[0162] f) a client identification H3a, such as a client ID (wherein, for example, the checking of the client ID H3a includes: determining whether the client ID H3a is a valid client ID that can be specified);

[0163] g) a session identifier H3b, such as a session ID (wherein, for example, the checking of the session ID H3b includes: determining whether the session ID H3b is a valid session ID that can be specified);

[0164] h) a protocol version H4 (for example by means of determining whether the protocol version corresponds to a valid protocol version that can be specified), for example having 8 bits;

[0165] i) an interface version H5, for example Interface Version (for example by means of determining whether the interface version corresponds to a valid interface version that can be specified), for example having 8 bits;

[0166] j) Type H6, for example a message type, for example a Message Type (for example by means of determining whether the message type corresponds to a valid message type that can be specified), for example having 8 bits;

[0167] j) Return value H7, for example a return code, for example a Return Code (for example by determining whether the return code corresponds to a valid return code that can be specified), for example having 8 bits.

[0168] In other exemplary embodiments, see Figure 2D , it is stipulated that: the inspection device 125 ( Figure 1) is designed to: for example within the framework of the state-based check 12b, check 1210: a) whether a response message RESP-MSG, such as Response Message, has been received after sending a request message, such as a request message associated with the response message RESP-MSG, such as Request Message; and / or b) whether the received response message RESP-MSG, such as Response Message, is associated with a previously sent request message; and / or c) whether the received response message RESP-MSG was received within a predeterminable response time, which response time is related to sending the request message associated with the response message RESP-MSG. Optional block 1212 represents: evaluating the result of the check 1210, such as according to whether at least one of the criteria a), b), c) exists.

[0169] In other exemplary embodiments, see Figure 3 , it is provided that: the checking device 125 is designed to: determine 22 a message type SOME / IP-N-TYP of at least one SOME / IP message associated with at least one received protocol data unit PDU-1, wherein, for example, the message type SOME / IP-N-TYP has at least one of the following elements: a) REQUEST; b) REQUEST_NO_RETURN; c) NOTIFICATION; d) RESPONSE; e) ERROR; f) TP_REQUEST; g) TP_REQUEST_NO_RETURN; h) TP_NOTIFICATION; i) TP_RESPONSE; j) TP_ERROR. According to Figure 3 Optional block 20 represents the reception of a protocol data unit PDU-1, for example in accordance with Figure 2A Block 10 is similar.

[0170] In other exemplary embodiments, it is provided that the checking device 125 is designed to determine 24 a service type SOME / IP-D-TYP of at least one SOME / IP message associated with at least one received protocol data unit PDU-1, wherein, for example, the service type SOME / IP-D-TYP has at least one of the following elements: a) RPC, i.e., remote procedure call; b) Fire & Forget; c) Notify.

[0171] In other exemplary embodiments, according to Figure 3 Block 22 and / or in accordance with Figure 3 Block 24 may be, for example, Figure 2APart of inspection 12.

[0172] In other exemplary embodiments, see Figure 4 , it is stipulated that: the inspection device 125 ( Figure 1 ) is designed to: for example, based on the at least one received protocol data unit PDU-1, execute 28 ( Figure 4 ) a state-based and / or state-oriented evaluation of at least one SOME / IP service, such as a state-based and / or state-oriented evaluation of a remote procedure call, such as having a request element and / or a response element, see Figure 4 Block 26 exemplarily represents the reception of a protocol data unit PDU-1.

[0173] In other exemplary embodiments, it is provided that the inspection device 125 ( Figure 1 ) is designed to at least temporarily also perform a non-state-based and / or non-state-oriented evaluation, such as a non-state-based and / or non-state-oriented evaluation of a SOME / IP service and / or other services and / or protocols or data units associated therewith, see block 12a ( Figure 2A ).

[0174] In other exemplary embodiments, see Figure 5 , it is stipulated that: the checking device 125 is designed to: for example, based on the check 32, discard 34 (for example, when the result ERG of the check 32 can infer an attack attempt or a malicious data unit) or not discard 38 the at least one received protocol data unit PDU-1, for example, keep it unchanged (for example, when the result ERG of the check 32 can infer that there is no attack attempt or no malicious data unit).

[0175] In other exemplary embodiments, it is provided that the checking device 125 is designed to: for example, based on the checking 32, for example, when the result of the checking 32 ERG can infer that there is no attack attempt or no malicious data unit, not discard the at least one received protocol data unit PDU-1, for example, forward 36 the at least one received protocol data unit, for example, for output (see, for example, according to Figure 1 120, 120a), for example, output to another unit. Figure 5 Optional block 30 exemplarily represents the reception of a protocol data unit PDU-1.

[0176] In other exemplary embodiments, it is provided that the checking device 125 is designed to modify or influence the output of the at least one received protocol data unit PDU-1 and / or the at least one received protocol data unit, for example via the output interface 120a ( Figure 1 ) output, for example to cause unicast output or multicast output.

[0177] In other exemplary embodiments, see Figure 6 , it is provided that: the inspection device 125 is designed to perform at least one of the following elements:

[0178] a) attack identification 40, such as intrusion detection, and / or attack identification and attack prevention, such as intrusion detection and prevention;

[0179] b) marking 41 the at least one received protocol data unit PDU-1, for example based on the checking 12, 32 and / or based on a result ERG of the checking;

[0180] c) by means of a multicast mechanism, for example to at least one software component 134 (see below) Figure 7 ), outputting and / or forwarding 42 the at least one received protocol data unit PDU-1, for example for evaluation or execution, for example further evaluation or execution, of attack identification, for example software-based attack identification;

[0181] d) outputting and / or forwarding 43 the at least one received protocol data unit PDU-1, for example to at least one software component or the at least one software component 134, by means of a unicast mechanism, for example for evaluation or execution, for example further evaluation or execution, of an attack identification, for example software-based attack identification;

[0182] e) determining 44 and / or evaluating 45 service identification messages, such as service discovery messages, which are for example based on a network protocol, such as a connectionless network protocol, such as based on a user datagram protocol, UDP;

[0183] f) Determining 46 and / or evaluating 47 a protocol data unit of the AUTOSAR I-PDU type, for example for a check, such as a safety check.

[0184] In other exemplary embodiments, see Figure 7 , Figure 8 , Fig. 9, it is provided that: the device 100a has a processing device 130, which is designed to: based on the PDU identifier associated with the received protocol data unit PDU-1, in at least one first search tree B-1 ( Figure 7 , Figure 8 ) performs a search in 200( Fig. 9 ), the first search tree having an assignment Z of each PDU identifier MSG-ID, for example a message identifier, for example a message ID, to a connection identifier VB-ID characterizing at least one data connection, wherein, for example, the search 200 can be performed in the check 12 ( Figure 2A ) is performed before and / or after the check and / or at least partially overlapped with the check in time. In other exemplary embodiments, the search 200 can be used for routing, such as forwarding, of data units, for example.

[0185] In other exemplary embodiments, for example, if the examination 12 occurs before the search 200 , the search 200 may be performed, for example, based on the result ERG of the examination 12 .

[0186] In other exemplary embodiments, for example, if the check 12 occurs after the search 200, the check 12 can be performed, for example, based on the result of the search, for example, based on the connection identifier VB-ID, and / or based on information associated with the connection identifier VB-ID. Thereby, in other exemplary embodiments, for example, it can be achieved that for a specific connection identifier, the check 12 of the relevant data unit PDU-1 is performed by means of the check device 125, wherein, for example, for other connection identifiers, the check of the relevant data unit is not performed by means of the check device 125.

[0187] In other exemplary embodiments, it is provided that the device 100a is designed to: determine 202 ( Fig. 9 ) a connection identifier VB-ID associated with the received protocol data unit PDU-1, wherein, for example, the determination 202 can be performed before the check 12 and / or after the check and / or at least partially overlapping in time with the check.

[0188] In a further exemplary embodiment, it is provided that the processing device 130 has at least one hardware component 132 which is designed to perform a search 200 in the first search tree B-1 and / or to determine 202 a connection identifier VB-ID associated with the received protocol data unit PDU-1. For example, a hardware-based search can be carried out particularly quickly and efficiently and - like a hardware-based (firewall) check 12 of data units - is insensitive to software-based attack attempts.

[0189] In other exemplary embodiments, it is provided that the first search tree B- 1 is a binary tree.

[0190] In other exemplary embodiments, it is provided that the first search tree B-1 is a ternary tree or an n-ary tree, where n>3.

[0191] In other exemplary embodiments, it is provided that the device 100a is designed to: based on the connection identifier VB-ID-1 associated with the received protocol data unit PDU-1, send a signal to at least one specific output interface 120a of the second number of output interfaces 120 (see Figure 1 , Figure 7 ), outputting the received protocol data unit PDU-1 and / or data derived or derivable therefrom, see Fig. 9 Optional block 204.

[0192] In other exemplary embodiments, it is provided that at least part of the functions of the checking device 125 are implemented by means of a hardware component 132, see Figure 7 In other exemplary embodiments, the inspection device 125 can also be completely integrated into the hardware component 132.

[0193] In other exemplary embodiments, the inspection device 125 may also be designed and / or arranged independently of the hardware component 132 of the processing device 130 .

[0194] In other exemplary embodiments, it is provided that the processing device 130 has at least one software component 134, wherein the software component 134 is designed to execute at least one of the following elements:

[0195] a) Temporarily form at least 210 ( Fig.10 ) The first search tree B-1;

[0196] b) at least temporarily modifying 212, for example balancing, the first search tree B-1, wherein, for example, a balanced first search tree B-1' is obtained;

[0197] c) (e.g. if, based on the result ERG of the check 12, 32 of the protocol data unit by the checking device 125, it is concluded that a software-based check of the protocol data unit, e.g. a further software-based check, should be performed) receiving 214 at least one protocol data unit PDU-1 from the checking device 125;

[0198] d) Evaluation 216, such as performing attack identification, such as software-based attack identification.

[0199] In other exemplary embodiments, see Fig.11, Fig.12 , it is provided that: the at least one software component 134 is designed to: if for the received protocol data unit PDU-1, a connection identifier associated with the received protocol data unit cannot be determined, for example if for the received protocol data unit, a connection identifier associated with the received protocol data unit does not exist in the first search tree B-1, then execute 222 a specifiable reaction R, wherein, for example, the specifiable reaction R has at least one of the following elements:

[0200] a) discard 225( Fig.12 ) received protocol data unit;

[0201] b) assigning 226 a connection identifier VB-ID-CFG, for example a configurable connection identifier, to the received protocol data unit;

[0202] c) setting or inserting 227 first information I1 or first control information SI-1 for the received protocol data unit, for example in the form of a bit flag, wherein the first information I1 and / or the first control information SI-1, for example, indicates that the received protocol data unit should be checked 12, for example by means of the checking device 125, for example a firewall device. Fig.11 Block 220 represents the reception of protocol data unit PDU-1.

[0203] In other exemplary embodiments, it is provided that the checking device 125 is designed to evaluate the first information I1 and / or the first control information SI-1, and based thereon, perform or not perform a check 12 of the relevant data unit. For example, if the bit flag corresponding to the information I1, SI-1 is set, the checking device 125 can check the relevant data unit, and if the bit flag corresponding to the information I1, SI-1 is not set, the checking device 125 does not check the relevant data unit.

[0204] In other exemplary embodiments, see Fig.13 , it is stipulated that: equipment 100, 100a ( Figure 1 , Figure 7 ), for example, the at least one software component 134 is designed to: for example, based on the first search tree B-1, generate 230 ( Fig.13 ) a second search tree B-2, and / or manage 232, for example modify the second search tree, wherein, for example, a modified second search tree B-2' can be obtained.

[0205] In other exemplary embodiments, it is provided that the first search tree B-1 and / or the second search tree B-2 are red-black trees.

[0206] In other exemplary embodiments, it is provided that the first search tree B-1 is a binary tree, for example, without color information (for example red / black); and the second search tree B-2 is a red-black tree. This enables an efficient, for example hardware-based search in the first search tree B-1, for example with the aid of at least one hardware component 132, wherein, for example, no color information exists for the search, while in other exemplary embodiments, for example, in order to efficiently manage the second search tree B-2, the second search tree B-2 is designed as a red-black tree.

[0207] In other exemplary embodiments, it is provided that the device 100 is designed to organize the first search tree B- 1 and / or the second search tree B- 2 at least temporarily in the form of at least one table.

[0208] In other exemplary embodiments, see Fig.14 , it is provided that the devices 100, 100a are designed to at least partially overlap in time

[0209] a) based on the received protocol data unit PDU-1, for example by means of the at least one hardware component 132, for example by means of performing the search in the first search tree B-1 by the at least one hardware component 132, determining 240 a connection identifier VB-ID-1 associated with the received protocol data unit PDU-1; and

[0210] b) For example, with the aid of at least one software component 134, for example, based on the first search tree B-1 (for example, by copying the first search tree B-1), generate 242 a second search tree or the second search tree B-2, and / or manage 244, for example, modify the second search tree or the second search tree (for example, transform it into a red-black tree and / or change the elements or structure of the search tree).

[0211] In other exemplary embodiments, see Fig.15 , it is provided that: the device 100, 100a is designed to perform at least one of the following elements:

[0212] a) at least temporarily, e.g. selectively, using 250 the first search tree B-1 or the second search tree B-2, e.g. in order to determine a connection identifier VB-ID-1 associated with the received protocol data unit PDU-1;

[0213] b) transferring 251 the content and / or structure of the second search tree B-2 to the first search tree B-1 (e.g., in order to make the search tree B-2, B-2' modified, e.g., by means of the software component 134, e.g., balanced, into the first search tree B-1 which can be searched, e.g., by means of the hardware component 132);

[0214] c) Transferring 252 the content and / or structure of the first search tree B-1 to the second search tree B-2 (eg, in order to prepare modifications that may be performed, for example, by means of software component 134).

[0215] In other exemplary embodiments, see Fig.16 , it is provided that the device 100, 100a, for example at least one software component 134, is designed to, for example by means of second information I2, for example to at least one hardware component 132, signal 255 at least one of the following elements:

[0216] a) The search should be performed using the first search tree B-1;

[0217] b) the search should be performed using the second search tree B-2;

[0218] c) completing the modification of the first search tree B-1 and / or the second search tree B-2, such as inserting at least one node and / or balancing the relevant search trees.

[0219] In other exemplary embodiments, it is provided that the device 100 , for example the at least one hardware component 132 , is designed to use 256 the first search tree B- 1 or the second search tree B- 2 to perform the search based on the signaling 255 .

[0220] In other exemplary embodiments, it is provided that the device 100, 100a, for example the at least one hardware component 132, is designed to: activate 257 the first search tree B-1 or the second search tree B-2 for performing a search between two searches, for example consecutive searches, for example for searching or performing a search in the future, for example by: specifying 257a which of the two search trees should be used thereafter to search or perform a search.

[0221] In other exemplary embodiments, see Fig.17 , it is provided that the device 100 , 100a is designed to control 261 or regulate 262 the rate at which the protocol data units are output via at least one output interface of the second number of output interfaces. Fig.17 Block 260 in , for example, represents the reception of protocol data units, for which, in further exemplary embodiments, the mentioned rate is controlled 261 or regulated 262 .

[0222] Fig.18 A simplified block diagram of a device 100b according to an exemplary embodiment is schematically shown. In other exemplary embodiments, the device may have the same Figure 1 The device 100 and / or the Figure 7 The device 100a has the same function as the device 100a. Fig.18Block E1 represents a search device, which can be implemented in hardware, for example, by means of Figure 7 The hardware component 132 of the present invention may be equivalent to the hardware component.

[0223] Block E2 represents the first search tree B-1 ( FIG. 71 ), which can be organized in the form of a first table. For example, in other exemplary embodiments, the first table can be called a “working table”. Block E3 represents the second search tree B-2 ( Fig.13 ), for example, can be organized in the form of a second table, for example, in other exemplary embodiments, the second table can be called a "shadow table".

[0224] In a further exemplary embodiment, the device 100b has a multiplexing device E23, via which the search device E1 can selectively access the first table E2 or the second table E3, for example, to perform a search, see Fig. 9 Block 200. In other exemplary embodiments, the selection of the first table E2 or the second table E3 can be realized, for example, by means of a control signal a1, in other exemplary embodiments, for example, the search device E1 can form this control signal and / or output this control signal to the multiplexing device E23.

[0225] In other exemplary embodiments, it is provided that the device 100b has at least one memory for at least temporarily storing one or more protocol data units PDU-1 ( Figure 1 ), for example received protocol data units or parts of one or more protocol data units. The device 100b for example has a first buffer memory E5, which can for example at least temporarily store incoming protocol data units or protocol data units received or receivable by the device 100b, for example according to the FIFO (first in first out) principle. Optionally, the first buffer memory E5 can also at least temporarily perform desegmentation of the received protocol data units.

[0226] In other exemplary embodiments, the device 100b has a second buffer memory E6, which can be used, for example, to "delay" at least one received protocol data unit, i.e., for example, to temporarily store a received protocol data unit or at least a part of a received protocol data unit, for example until the protocol data unit is output, for example, at a possibly specifiable later time point.

[0227] In other exemplary embodiments, the second buffer memory E6 is designed to delay the received protocol data unit until the search device E1 has determined the connection identifier VB-ID-1 associated with the received protocol data unit PDU-1, for example by a search in the first search tree B-1, E2, for example performed with the aid of hardware component 132, E1.

[0228] In other exemplary embodiments, the memory capacity or memory size of the second buffer memory E6 can be specified based on the maximum search duration in the first search tree B-1. For example, in other exemplary embodiments, when using the first binary search tree B-1, it can be assumed that the maximum search duration is proportional to the logarithm of the number of nodes of the search tree, such as the logarithmic dual (ld), and is proportional to the number of clock cycles required to read and evaluate the nodes of the search tree.

[0229] In other exemplary embodiments, it is provided that the device 100b has a regulating device E4, which is designed to change the PDU identifier associated with the received protocol data unit, for example to normalize it. To this end, Fig. 20 A simplified flow chart according to a further exemplary embodiment is shown by way of example, wherein block 265 represents the optional reception of a protocol data unit PDU-1, wherein block 266 represents the change of a PDU identifier MSG-ID associated with the received protocol data unit, wherein, for example, a changed PDU identifier MSG-ID' is obtained. Optional block 267 represents further processing of the changed PDU identifier MSG-ID' according to a further exemplary embodiment, such as performing a search in a first search tree B-1, E2 based on the changed PDU identifier MSG-ID'.

[0230] In further exemplary embodiments, the control device E4 is designed to form a search vector a2 which can be forwarded to the search device E1 , for example.

[0231] In other exemplary embodiments, the search vector a2 may have at least one of the following elements:

[0232] a) a PDU identifier MSG-ID associated with the received protocol data unit PDU-1;

[0233] b) information rxbus, which characterizes an input interface, for example a virtual input interface, which corresponds, for example, to a virtual device identifier of a virtual device via which the protocol data unit PDU-1 was received;

[0234] c) Information items rembus which, for example, characterize for at least one type of received protocol data unit PDU- 1 , for example for the L-PDU type, a remote receive bus of the L-PDU.

[0235] In other exemplary embodiments, the search vector a2, also referred to as "searchVector", may also have the above three elements a), b), and c): searchVector = {rxbus, rembus, msgid}, wherein msgid represents the PDU identifier MSG-ID.

[0236] In other exemplary embodiments, the search device E1 is designed to compare the search vector a2 with reference vectors of the first table E2 , wherein the reference vectors define, for example, a format or one of a plurality of possible formats.

[0237] In other exemplary embodiments, for example, based on the corresponding input interface 110 via which the protocol data unit PDU-1 is received, one or more of the following formats can be used for the PDU identifier MSG-ID:

[0238] a) For example, a protocol data unit associated with the CAN (Controller Area Network) protocol or a CAN bus, such as an I-PDU type (Interaction Layer Protocol Data Unit, for example according to AUTOSAR);

[0239] b) 11-digit standard ID;

[0240] c) 29-bit extended ID;

[0241] d) 32-bit message ID, such as the message ID of the CAN-XL acceptance field;

[0242] e) I-PDU associated with a LIN (local interconnect network) bus;

[0243] f)AUTOSAR Dynamic I-PDU Multiplexing using UDP or CAN as transport layer (ASAR sockets in TUNETH_DEV or CAN sockets in TUNCAN_DEV);

[0244] g) SomeIP S-PDU multiplexing (SomeIP socket in TUNETH_DEV or CAN socket in TUNCAN_DEV);

[0245] h) AVTP P1722 L-PDU multiplexing (AVB socket in TUNETH_DEV).

[0246] In other exemplary embodiments, the regulating device E4 is designed to form a search vector a2, for example a compatible search vector, for example by normalizing the above-mentioned format of the PDU identifier MSG-ID, wherein, for example, a normalized search vector a2' is obtained. For example, the search vector a2 and / or the normalized search vector a2 may have 32 bits.

[0247] In a further exemplary embodiment, the functionality of the regulating device E4 can be represented, for example, by the following pseudo code (“Pseudocode 1”).

[0248]

[0249]

[0250] In other exemplary embodiments, the variable "noSearch" provided in the pseudo code 1 above can be used to indicate whether the search should be performed by the search device E1. In other exemplary embodiments, information associated with the variable noSearch can be transmitted to the search device E1 by the adjustment device E4, for example, as described in accordance with Fig.18 Arrow a3.

[0251] In other exemplary embodiments, the variable "validMsg" provided in the pseudo code 1 above may be used so that valid and invalid messages or data frames may be distinguished.

[0252] In other exemplary embodiments, the query "--AVBTP General Purpose control message elseif tlv.messageType == CLF_TLV_P1722_GPC" contained in the pseudo code 1 above may cause: for PDU identifiers with AVBTP or CLF_TLV_P1722_GPC format / type, no search is performed. For example, in other exemplary embodiments, for this type of PDU identifier, a configurable connection identifier VB-ID-CFG may be specified (e.g., see Fig.12 226), i.e., for example, no previous search is required.

[0253] In other exemplary embodiments, provision may be made for the configurable connection identifier VB-ID-CFG or the configurable connection identifier to be used for such a PDU identifier for which no search is performed.

[0254] In a further exemplary embodiment it is provided that the device 100b has a device E7 for modifying header data, which is designed, for example, to selectively discard the protocol data unit PDU-1, for example when the search of the search device E1 yields no results, for example based on a control a4 of the search device E1.

[0255] In other exemplary embodiments, the device 100b has a third buffer memory E8, which can at least temporarily store the protocol data units to be output and, optionally, can at least temporarily perform segmentation.

[0256] In a further exemplary embodiment, the device 100b has a statistical device E9 which is designed to determine or manage statistical information about the operation of the device 100, 100a, 100b or the search device E1.

[0257] according to Fig.18 Block E10 of the embodiment of the present invention represents, for example, a checking device, for example a firewall device, for example at least similar to Figure 1 Inspection device 125.

[0258] In other exemplary embodiments, the device 100b, for example the counting device E9, is designed to manage at least one of the following exemplary counters, see Fig.19 :

[0259] a) counter Z1, for the number of discarded protocol data units;

[0260] b) a counter Z2 for the total number of protocol data units processed by the device 100, 100a, 100b;

[0261] c) a counter Z3 for the number of protocol data units forwarded by means of the device 100, 100a, 100b;

[0262] d) a counter Z4 for the number of search hits of the search device E1;

[0263] e) a counter Z5 for the number of unsuccessful searches performed by means of the search device E1;

[0264] f) a counter Z6 for, for example, damaged protocol data units to be discarded, for which, for example, the control device E4 indicates that these protocol data units are to be discarded, with the exception of, for example, protocol data units of the AVB P1722 GPC type;

[0265] Counter Z7 for the number of bytes that have been transmitted by the device 100, 100a, 100b.

[0266] In other exemplary embodiments, at least one of the counters Z1, Z2, ..., Z7 has a data width of 32 bits, which in other exemplary embodiments enables, for example, relatively low-frequency polling (e.g., once per second or less frequently), for example by means of software, for example by means of software component 134 ( Figure 7 ).

[0267] In other exemplary embodiments, the search device E1 ( Fig.18 )'s design may depend on the search algorithm used.

[0268] In other exemplary embodiments, the following exemplary embodiments of the search algorithm are conceivable, wherein the following two exemplary embodiments are, for example, variants of a binary search and, for example, use a worksheet E2 ( Fig.18 ) and shadow table E3.

[0269] In other exemplary embodiments, the worksheet E2 is provided by, for example, the hardware component 132 ( Figure 7 ) is used, for example, to perform a 200 search ( Fig. 9 ) and / or for determining 202 a connection identifier VB-ID-1 associated with the received protocol data unit PDU-1.

[0270] In other exemplary embodiments, the shadow table E3 is used, for example, by the software component 134 , for example in order to change the search table, for example when adding and / or removing entries, for example during runtime of the device 100 , 100a , 100b .

[0271] In other exemplary embodiments, for example, a binary sort table can be used, which, for example, has a plurality of reference vectors ("arrays") of sorting, such as the reference vectors described above. In other exemplary embodiments, for example, each entry of the binary sort table can be designated as a node ("node").

[0272] In other exemplary embodiments, for example, a search tree can be used, such as a balanced search tree, such as a red-black search tree, for example, see the description of the first search tree B-1 and the second search tree B-2 above. In other exemplary embodiments, for example, at least one of the search trees B-1 and B-2 can be organized in the form of a table.

[0273] In other exemplary embodiments, the node structure of the at least one search tree B-1, B-2 may be characterized, for example, in the following manner:

[0274]

[0275] Wherein, refVector represents a reference vector, wherein the reference vector may exemplarily have the elements rxbus (e.g., having 8 bits), rembus (e.g., having 8 bits), and msgid (e.g., having 32 bits) described above,

[0276] Among them, attrib represents the optional attributes of the node.

[0277] Among them, sec represents the attributes associated with possible authentication,

[0278] Therein, fw represents an optional attribute which indicates whether a security check, for example an optional security check, is to be performed for the relevant protocol data unit or for the protocol data unit associated with the connection identifier pduCid, for example by means of a checking device 125, E10, for example a firewall.

[0279] Among them, nodeLeft represents the left child node in the binary search tree.

[0280] Among them, nodeRight represents the right child node in the binary search tree, and

[0281] Among them, color represents the color attribute of the search tree.

[0282] In other exemplary embodiments, for example, a binary search tree can have a "color" component, which is stored or can be stored in the hardware memory. In other exemplary embodiments, this component can be used, for example, so that the search tree can be modified "in-memory" (i.e., directly in the memory), for example without creating a copy, for example a costly copy, in the working memory of the software.

[0283] In other exemplary embodiments, the search tree, for example the first search tree B-1, which can be evaluated by means of the hardware component 132, has no color information (red-black) for its nodes. In other exemplary embodiments, this color information (red-black) is provided and / or used, for example, when adding and / or removing nodes, whose operations are performed, for example, on the second search tree B-2, for example, by means of the software component 134. Therefore, in other exemplary embodiments, the color information (red-black) associated with the nodes of the second search tree B-2, for example, can be retained or at least temporarily stored in a table that can be managed by means of the software component 134.

[0284] In other exemplary embodiments, a search tree that can be evaluated by means of hardware component 132, for example first search tree B-1, has color information (for example red-black) for its nodes, which can be implemented, for example, by means of the above-mentioned “color” component.

[0285] The above-mentioned exemplary embodiment based on a binary search advantageously results in a relatively small, logarithmic, search effort based on the total number of elements of the associated search tree or associated table.

[0286] In other exemplary embodiments, it is provided that the search device E1 searches 200 successfully ( Fig. 9 ), the optional attribute attrib of the node found in the search 200 (for example, the node of the search tree B-1) is sent to the means E7 for modifying the header data, see Fig.18 In this case, for example, a signal is used to notify that the relevant protocol data unit PDU-1 is not discarded, see the above reference Fig.12 Arrow a4 has already been described.

[0287] In other exemplary embodiments, it is provided that the search device E1 performs at least one of the following actions if the search 200 is unsuccessful: a) for example, by means of arrow a4, instructs the device E7 to discard the protocol data unit PDU-1 (wherein, for example, the counter Z6 can also be incremented, see Fig.19 ); b) inserting a connection identifier VB-ID-CFG, for example a static and / or configurable connection identifier (and / or setting a firewall flag fw, which indicates that the protocol data unit PDU-1 should be subjected to a security check, for example a security check performed by a firewall device 125, E10).

[0288] In other exemplary embodiments, it is provided that the data structure of at least one search tree B-1, B-2, for example a node structure, for example see the structure "node" already described above by way of example, has an attribute, which indicates whether a security check, for example a security check by means of the checking device 125, E10, should be performed for the relevant protocol data unit or for the protocol data unit associated with the connection identifier. For example, this attribute can be characterized by the above-mentioned bit flag "fw" and / or corresponds to the first information I1 or the first control information SI-1 ( Figure 1 ).

[0289] In other exemplary embodiments, it is provided that the inspection device 125 ( Figure 1 ) is designed to use the connection identifier VB-ID, for example for determining a service and / or an identification associated with, for example, the at least one received protocol data unit.

[0290] For other exemplary embodiments, see Figure 2A , relates to a method, for example a computer-implemented method, for processing a data unit PDU-1, for example a protocol data unit, for a device 100, 100a, 100b, for example according to the embodiments, the method comprising:

[0291] a first number 110 of input interfaces for receiving protocol data units, and optionally a second number 120 of output interfaces for outputting protocol data units, and a checking device 125, such as a firewall device, which is designed to check at least one received protocol data unit, such as to subject it to a security check, wherein the method comprises:

[0292] Receive 10( Figure 2A ) at least one protocol data unit PDU-1;

[0293] By means of the checking device 125, at least one received protocol data unit PDU-1 is checked 12, wherein the checking device 125 at least temporarily performs at least one of the following checks:

[0294] a) a non-state-based, e.g. non-state-oriented, e.g. stateless, check 12a, e.g. with respect to the at least one received protocol data unit;

[0295] b) A state-based, for example state-oriented, for example stateful, check 12b, for example with respect to the at least one received protocol data unit.

[0296] In other exemplary embodiments, it is provided that the method has at least one of the following elements:

[0297] a) outputting 14 at least one protocol data unit, for example based on the checking 12;

[0298] b) For example, based on the checking 12 , at least one protocol data unit is discarded 15 .

[0299] In other exemplary embodiments, it is provided that the checking device 125 subjects at least some of the received protocol data units to a non-state-based check and, for example based on the result of the non-state-based check, subjects at least some of the received protocol data units to a state-based check.

[0300] In other exemplary embodiments, it is provided that the checking device 125 modifies or influences the at least one received protocol data unit and / or the output of the at least one received protocol data unit, for example via an output interface.

[0301] Subsequently, further exemplary aspects and embodiments are described, in which these aspects and embodiments can be combined with one another individually or in any combination with at least one of the aspects exemplarily described above.

[0302] In other exemplary embodiments, see Fig.24A , stipulates that: the method has at least one of the following elements:

[0303] a) receiving 1300 data, for example in the form of a data frame DR;

[0304] b) determining 1202 an endpoint EP associated with receiving 1300 data, for example an input interface associated with receiving data, such as a socket, for example a User Datagram Protocol (UDP) socket, for example by means of a ternary content addressable memory (TCAM);

[0305] c) decomposing 1304 the data frame DR, for example, into at least one protocol data unit, such as S-PDU, S-PDU1, S-PDU2, S-PDU3;

[0306] d) assigning 1306 an identifier ID-EP representing the endpoint EP to the at least one protocol data unit S-PDU1, S-PDU2, S-PDU3;

[0307] e) checking 1308 at least one of the following elements of at least one protocol data unit S-PDU1, S-PDU2, S-PDU3, for example by means of the device 100, 100a, 100b and / or by means of the checking device 125: e1) message identifier H1 (see for example Figure 2C ), such as message ID, e2) request identifier H3 (see for example Figure 2C ), such as request ID, e3) protocol version H4 ( Figure 2C ), e4)Interface version H5( Figure 2C ), such as Interface Version, e5) type H6( Figure 2C ), such as a message type, such as Message Type;

[0308] f) Based on the inspection 1308 ( Fig.24A ) or based on the result ERG-1308 of the check 1308, f1) outputs 1310 or forwards data, for example in the form of a data frame DR, or f2a) discards 1312 these data, for example the data frame DR and / or f2b) increments 1314 a counter DROP-CNT, which counts, for example, how many data frames DR have been discarded. In other exemplary embodiments, the counter value of the counter DROP-CNT can be used, for example, in an attack identification method or system.

[0309] In other exemplary embodiments, the assignment 1306 of the identifier ID-EP characterizing the endpoint EP to the at least one protocol data unit S-PDU1, S-PDU2, S-PDU3, for example, enables: checking, for example, subsequently checking the corresponding protocol data units S-PDU1, S-PDU2, S-PDU3, for example, at least mainly (also) based on the identifier ID-EP characterizing the endpoint EP, which further increases flexibility and / or security.

[0310] Fig. 24B A simplified flow chart according to an exemplary embodiment is schematically shown, which describes, for example, Fig.24A In other exemplary embodiments, the process can be used to implement a non-state-based (eg, stateless) firewall function, such as for protocol data units associated with the SOME / IP protocol.

[0311] The element DR-ETH represents, for example, an Ethernet data frame that is transmitted at a device 100, 100a, 100b or is received or receivable by the device, which Ethernet data frame, for example, mainly has a plurality of protocol data units S-PDU1, S-PDU2, S-PDU3. The element TC-L represents: a UDP socket associated with the Ethernet data frame DR-ETH is determined, in the present case, for example, with the identifier "ID=2", for example, by means of a TCAM search; the element PDU-DECOMP represents: the Ethernet data frame DR-ETH is split into a plurality of protocol data units S-PDU1, S-PDU2, S-PDU3 contained therein or the protocol data units S-PDU1, S-PDU2, S-PDU3 contained in the Ethernet data frame DR-ETH are determined. The element ZUORD represents: the previously determined UDP socket or the identifier "ID=2" associated therewith is assigned to the determined protocol data units S-PDU1, S-PDU2, S-PDU3 contained in the Ethernet data frame DR-ETH.

[0312] The elements PDURX, PDUFW indicate that the determined protocol data units S-PDU1, S-PDU2, S-PDU3 contained in the Ethernet data frame DR-ETH are checked, for example, by the device 100, 100a, 100b or by the checking device 125, for example, at least similar to Fig.24A Block 1308.

[0313] In an exemplary embodiment, the apparatus 100, 100a, 100b, for example, with the aid of the processing device 130 ( Figure 7 ), for example checking the message IDs of the protocol data units S-PDU1, S-PDU2, S-PDU3, for example for determining the connection identifier VB-ID which may be associated with the message ID MSG-ID, for example see also Figure 8 .

[0314] In an exemplary embodiment, the apparatus 100, 100a, 100b, for example, by means of an inspection device 125 ( Figure 1 , Figure 7 ), and for example based on a previous check of the message ID MSG-ID, checks at least one of the following elements: e2) request identifier H3 (see for example Figure 2C ), such as request ID; e3) protocol version H4 ( Figure 2C ); e4) Interface version H5( Figure 2C ), such as Interface Version; e5) type H6( Figure 2C ), such as the message type, such as Message Type.

[0315] In other exemplary embodiments, see Fig.25A , stipulates that: the method has at least one of the following elements:

[0316] a) receiving 1320 data, for example in the form of a data frame DR';

[0317] b) determining 1322 an endpoint EP′ associated with receiving 1320 data, for example an input interface associated with receiving 1320 data, for example a socket, for example a Controller Area Network (CAN) socket, for example by means of a ternary content addressable memory (TCAM);

[0318] c) decomposing 1324 the data frame DR′, for example, into at least one protocol data unit, for example, I-PDU, I-PDU1, I-PDU2, I-PDU3;

[0319] d) assigning 1326 an identifier ID-EP' characterizing the endpoint EP' to the at least one protocol data unit I-PDU1, I-PDU2, I-PDU3;

[0320] e) checking 1328 at least one of the following elements of at least one protocol data unit I-PDU1, I-PDU2, I-PDU3, for example by means of the device 100, 100a, 100b or the checking device 125: e1) a message identification, for example a message ID, e2) a length;

[0321] f) Based on the check 1328, f1) outputs 1330 or forwards data, for example in the form of a data frame DR', or f2a) discards 1332 these data, for example the data frame DR' and / or f2b) increments 1334 a counter DROP-CNT'. In other exemplary embodiments, the counter value of the counter DROP-CNT' can be used, for example, in an attack identification method or system.

[0322] In other exemplary embodiments, the assignment 1326 of the identifier ID-EP' characterizing the endpoint EP to the at least one protocol data unit I-PDU1, I-PDU2, I-PDU3, for example, enables: checking, for example, subsequently checking the corresponding protocol data units I-PDU1, I-PDU2, I-PDU3, for example, at least primarily (also) based on the identifier ID-EP' characterizing the endpoint EP, which further increases flexibility and / or security.

[0323] Fig.25B A simplified flow chart according to an exemplary embodiment is schematically shown, which describes, for example, Fig.25A In other exemplary embodiments, the process can be used to implement a non-state-based (eg, stateless) firewall function, for example, for protocol data units associated with the CAN or CAN FD protocol, such as I-PDUs.

[0324] The element DR-CAN represents, for example, a CAN (or CAN FD) data frame that is transmitted at a device 100, 100a, 100b or that is received or receivable by the device, which data frame, for example, mainly has a plurality of protocol data units I-PDU1, I-PDU2, I-PDU3. The element TC-L' represents: the CAN socket associated with the CAN data frame DR-CAN, in the present case, for example, with the identifier "ID=2", is determined, for example, by means of a TCAM search; the element PDU-DECOMP' represents: the CAN data frame DR-CAN is split into a plurality of protocol data units I-PDU1, I-PDU2, I-PDU3 contained therein or the protocol data units I-PDU1, I-PDU2, I-PDU3 contained in the Ethernet data frame DR-CAN are determined. The element ZUORD′ means that the previously determined CAN socket or the identifier “ID=2” associated therewith is assigned to the determined protocol data units I-PDU1 , I-PDU2 , I-PDU3 contained in the CAN data frame DR-CAN.

[0325] The elements PDURX', PDUFW' indicate that the determined protocol data units I-PDU1, I-PDU2, I-PDU3 contained in the CAN data frame DR-CAN are checked, for example, by the device 100, 100a, 100b or by the checking device 125, for example, at least similar to Fig.25A Block 1328.

[0326] In an exemplary embodiment, the apparatus 100, 100a, 100b, for example, with the aid of the processing device 130 ( Figure 7 ), for example checking the message IDs of the protocol data units I-PDU1, I-PDU2, I-PDU3, for example for determining the connection identifier VB-ID which may be associated with the message ID MSG-ID, for example see also Figure 8 .

[0327] In an exemplary embodiment, the device 100, 100a, 100b, for example, by means of the inspection device 125 ( Figure 1 , Figure 7 ), and for example based on a previous check of the message ID MSG-ID, for example checks the lengths of the corresponding protocol data units I-PDU1, I-PDU2, I-PDU3.

[0328] Fig.26 A simplified block diagram according to an exemplary embodiment is schematically shown. An exemplary configuration KONF is depicted, which has a device 100c, which in other exemplary embodiments has, for example, similar or identical functionality to at least one of the devices 100, 100a, 100b exemplarily described above.

[0329] Element E20 represents a network coupling element, such as a bridge, for example an IEEE 802.1Q-compatible bridge, which is designed to receive data from at least one Ethernet interface ETH1, ETH2, . . . , for example in the form of Ethernet data frames DR-ETH, and to forward the received data, for example to device E21.

[0330] In a further exemplary embodiment, the network coupling element E20 has a device E20a which is designed to execute the operation according to Fig.24A The determination 1302 (eg, determination of a UDP socket) may be performed. In other exemplary embodiments, the result of the determination 1302 (eg, the determined UDP socket) may be sent to the device E21, for example.

[0331] In other exemplary embodiments, the device E21 is designed to: process, for example, an Ethernet data frame DR-ETH received from a bridge E20, for example, extract the protocol data units S-PDU1, S-PDU2, S-PDU3 contained in the received Ethernet data frame DR-ETH from the received Ethernet data frame DR-ETH, and, optionally, assign to the extracted protocol data units S-PDU1, S-PDU2, S-PDU3, for example, a UDP socket determined by means of TCAM E20a, for example, by concatenating information characterizing the determined UDP socket with the corresponding protocol data units S-PDU1, S-PDU2, S-PDU3.

[0332] Element E22 represents a bridge, for example for processing or distributing protocol data units, for example L-PDUs. Bridge E22 can, for example, receive protocol data units S-PDU1, S-PDU2, S-PDU3 from device E21 and forward them to apparatus 100c, for example for at least one check according to the exemplary embodiment.

[0333] For example, in other exemplary embodiments, the bridge E22 can also receive, for example, protocol data units I-PDU1, I-PDU2, I-PDU3 associated with at least one CAN or CAN-FD interface CAN1, CAN2 from the device E23, and forward these protocol data units to the device 100c, for example for at least one check according to the exemplary embodiment. For example, the bridge E22 thus forwards a plurality of protocol data units, for example, a plurality of protocol data units of different types or origins (blocks E21, E23), for example serially, i.e., successively in time, to the device 100c.

[0334] In a further exemplary embodiment, the device E23 is designed to receive CAN or CAN FD data frames DR-CAN from at least one CAN or CAN-FD interface CAN1, CAN2 and to process them, for example to determine the CAN socket ID, for example by means of a TCAM device E23a. In a further exemplary embodiment, the device E23 is designed to output the received CAN or CAN FD data frames DR-CAN, if applicable together with the determined CAN socket ID, to the network bridge E22.

[0335] In other exemplary embodiments, at least one CAN or CAN-FD interface CAN1, CAN2 may have at least one filtering device FF1, FF2 for data frames, such as a frame filter, with the help of which CAN data frames incoming at the corresponding CAN interface CAN1, CAN2 can be filtered according to specifiable standards (e.g., according to one or more standards).

[0336] In other exemplary embodiments, the device 100c is designed to check the protocol data units received from the bridge E22, such as the protocol data units of the I-PDU type or the S-PDU type (or other types or PDU types), for example according to one or more prescribable rules, for example based on the principles described in the embodiments. Preferably, the checking of the device 100c is hardware-based, for example purely hardware-based, i.e., for example, without using software, thereby enabling particularly efficient checking and providing security against software-based attack attempts.

[0337] Optionally, in other exemplary embodiments, the device 100c can, for example, via a device E25 for processing, for example forwarding or routing, one or more protocol data units, possibly after checking by the device 100c, be fed to a software-based further check, for example by a further check by a computing device E24. In other exemplary embodiments, the computing device E24 can be advantageously relieved, for example, in terms of checking the protocol data units, by a previous, for example purely hardware-based, check of the protocol data units by means of the device 100c.

[0338] In other exemplary embodiments, for example S-PDUs, for example S-PDUs transmitted via CAN-FD, can also be checked by the device 100 , 100a , 100b , 100c .

[0339] In other exemplary embodiments, one or more protocol data units contained in a CAN or CAN FD message may be assigned information indicating at which of the possible multiple CAN buses the CAN or CAN FD message arrived, for example by concatenating this information with the protocol data unit. In other exemplary embodiments, it is thereby possible, for example, to also perform an inspection of the SOME / IP messages, for example a deep packet inspection, for example via CAN or CAN FD.

[0340] Fig. 27 A simplified signaling diagram according to an exemplary embodiment is schematically shown. Element E30 represents a SOME / IP client; element E31 represents a SOME / IP server. Element E32 represents a SOME / IP request from client E30 to server E31; and element E33 represents a SOME / IP response from server E31 to client E30. Double arrow A5 represents a specifiable maximum waiting time within which, for example, a response E33 to a request E32 must occur in order to still be considered valid in some embodiments.

[0341] In other exemplary embodiments, the client E30 sets the message ID E34a of the protocol data unit E34 associated with the request E32, for example, based on the SOME / IP method that the client E30 wants to call. Optionally, the client E30 can set the request ID E34b to a specifiable, for example, unique value, for example, to distinguish the request E32 from other requests. For example, the client E30 sets the message type E34c to "REQUEST".

[0342] After receiving the request E32 or the protocol data unit E34 associated therewith, the server E31 uses the same message ID and the same request ID as in the request E32, and according to the first option, sets the message type of the protocol data unit available for the response E33 to a) "RESPONSE", see protocol data unit E35a, or according to the second option, sets it to b) "ERROR", see protocol data unit E35b.

[0343] In other exemplary embodiments, the principles described in these embodiments can be used, for example, to provide a firewall, such as a hardware-based firewall, such as a state-based (e.g., stateful) firewall, for protocol data units E34, E35a, E36b associated with the SOME / IP protocol.

[0344] For example, in other exemplary embodiments, the inspection device 125 may be designed to: for example, in a state-based inspection 12b ( Figure 2A ) framework, check 1210( Figure 2D ):

[0345] a) whether the response message RESP-MSG, for example, Response Message, has been received after sending the request message E32, for example, a request message associated with the response message E33, for example, RequestMessage, see also Fig. 27 Response E33; and / or

[0346] b) whether the received response message RESP-MSG, E33, e.g. Response Message, is associated with a previously sent request message E32; and / or

[0347] c) whether the received response message E33 is received within a specifiable response time A5 related to the sending of the request message E32 associated with the response message E33.

[0348] In other exemplary embodiments, the response time A5 is, for example, configurable and a response message E33 incoming after expiration of the response time A5 is discarded, for example as erroneous or invalid with respect to the previous receipt of the request message E32 associated therewith.

[0349] For other exemplary embodiments, see Fig.21 , relates to a device for implementing the method according to these embodiments. In other exemplary embodiments, the device can have, for example, Figure 1 , Figure 7 , Fig.18 , Fig.26At least one of the configurations 100, 100a, 100b, 100c, KONF described as an example.

[0350] In other exemplary embodiments, alternatively or additionally, the device may also have an exemplary Fig.21 Configuration 300 as depicted in or similar thereto.

[0351] The device 300 has a computing device ("computer") 302, which has at least one computing core 302a, 302b, 302c; a storage device 304 assigned to the computing device 302 for at least temporarily storing at least one of the following elements: a) data DAT; b) a computer program PRG, in particular for executing the method according to the embodiments. In other exemplary embodiments, for example, the computing core 302c can also be designed or modified so that: the computing core implements the function of a firewall; or instead of another computing core, the device 300 can have a hardware circuit 302c that implements the firewall 125, and in other exemplary embodiments (not shown), the hardware circuit can also be provided outside the computing device 302. In other exemplary embodiments, a similar situation applies to the hardware component 132.

[0352] according to Fig.21 The optional elements 325 , 332 exemplarily represent: a hardware firewall 325 or a hardware component 332 , for example similar to the components 132 , 125 .

[0353] In other exemplary embodiments, the storage device 304 has: a volatile memory (eg, a working memory (RAM)) 304a; and / or a non-volatile memory (eg, a flash EEPROM) 304b; or a combination thereof or a combination with other memory types not explicitly mentioned.

[0354] In other exemplary embodiments, the data DAT may at least temporarily have at least one received protocol data unit PDU-1 and / or at least a portion of at least one search tree B-1, B-2, and / or related information, such as color information characterizing the red-black attribute of the second search tree B-2, and / or state information, such as for state-based check 12b( Figure 2A ).

[0355] In other exemplary embodiments, according to Fig.18 At least one of the buffer memories E5, E6, E8 can be implemented, for example, by means of the storage device 304 or the RAM 304a.

[0356] In other exemplary embodiments, the device 300 has at least one data interface 306 for receiving and / or sending data, such as a protocol data unit. In other exemplary embodiments, by means of the data interface 306, for example, the input interface 110 ( Figure 1 ) and / or at least some of the output interfaces 120.

[0357] Other exemplary embodiments relate to a computer-readable storage medium SM comprising instructions which, when executed by a computer 302 , cause the computer to carry out the methods described in accordance with these embodiments.

[0358] Further preferred embodiments relate to a computer program PRG which comprises instructions which, when the program PRG is executed by a computer 302 , cause the computer to carry out the method according to the embodiments.

[0359] Further exemplary embodiments relate to a data carrier signal DCS which represents and / or transmits a computer program PRG according to these embodiments. The data carrier signal DCS can be transmitted, for example, via a data interface 306 of the device 300 .

[0360] In other exemplary embodiments, the devices 100, 100a, 100b, 100c, 300 can be used in, for example, an automotive gateway 1000, see Fig. 22 , or a gateway for use in the vehicle network, i.e. for an application in the field of automotive technology, wherein, for example, for a protocol data unit PDU-1 incoming at the device, a check 12, 12a, 12b can be performed, for example by means of hardware, and / or wherein, optionally, for example, for a protocol data unit PDU-1 incoming at the device, for example by means of hardware, a corresponding connection identifier VB-ID-1 can be determined, and wherein, optionally, for example, based on the determined connection identifier VB-ID-1, the incoming protocol data unit PDU-1 can be output. Advantageously, the hardware firewall 125 can subject at least some of the incoming protocol data units PDU-1 to a hardware-based security check, which can, for example, be non-state-based (see according to Figure 2A Block 12a) and / or based on state (see Figure 2A Block 12b).

[0361] In other exemplary embodiments, for example, as opposed to a physical interface, the input interface 110 and / or the output interface 120 may also each have at least one virtual interface.

[0362] In other exemplary embodiments, the virtual interface can be characterized in that individual data units, such as protocol data units, are present, for example, as so-called "contained PDUs", for example in Ethernet or UDP packets, such as so-called "container PDUs". In other exemplary embodiments, the contained PDUs can be separated from the container PDUs, for example, by means of a packet parser.

[0363] In other exemplary embodiments, through the devices described in these embodiments, a common data format or message format can be used, for example for processing incoming protocol data units PDU-1, for example, regardless of the corresponding type of the incoming protocol data unit PDU-1 (e.g. L-PDU, I-PDUs, N-PDU, S-PDU), while enabling efficient hardware-based firewall inspection.

[0364] In other exemplary embodiments, the received protocol data unit PDU-1, for example, based on the search 200 ( Fig. 9 ) or determination 202, provided with a connection identifier VB-ID-1, for example a connection identifier which is independent of the protocol or independent of the respective type of the incoming protocol data unit PDU-1 (e.g. L-PDU, I-PDU, N-PDU, S-PDU), based on which, for example, a firewall check 12, 12a, 12b (e.g. hardware-based) can be performed (and optionally software-based with the aid of an optional computing device E24, see Fig.26 ) and / or can optionally perform routing, for example forwarding, of the protocol data unit PDU-1 through or in the device, for example routing to one or more (multicast) output interfaces.

[0365] In other exemplary embodiments, the modification of the PDU identifier PDU-ID may be performed selectively.

[0366] In other exemplary embodiments, unknown protocol data units, for which the search 200 or the determination 202 is, for example, negative and therefore does not result in a connection identifier associated with the PDU identifier PDU-ID, can be further processed, for example with the aid of a software component 134, for example by means of a computer program that can be provided for this purpose, which, for example, performs a detailed analysis of the unknown protocol data units or performs a security analysis, and / or with the aid of a firewall 125.

[0367] In other exemplary embodiments, the devices 100, 100a, 100b, 100c, 300 described in these embodiments can be used, for example, as a feedback device, for example a one-way feedback device, for a gateway, for example, for an automotive gateway 1000, see Fig. 22 , wherein, for example, the device 100, 100a, 100b, 100c, 300 is designed to: receive the protocol data unit PDU-1 from at least one output interface 1012 of the gateway 10; and optionally, transmit these protocol data units PDU-1 to at least one input interface 1011 of the gateway 10. Advantageously, the device 100, 100a, 100b, 100c, 300 can perform the above-mentioned firewall check 12, 12a, 12b for at least some of the protocol data units PDU-1. For example, Fig. 22 The block 1014 in the gateway 1000 may have the configuration 100, 100a, 100b, 100c, 300 described in the above exemplary embodiments. The block arrow 1013 indicates: the data flow in the gateway 1000, such as the data flow from the input interface 1011 to the output interface 1012, which is associated with the processing pipeline of the gateway 1010, for example.

[0368] In other exemplary embodiments, the device 100, 100a, 100b, 100c, 300 is designed to receive, for example sequentially in time ("serialized"), data units, for example complete data units, for example protocol data units, for example from components of at least one output interface 1012 of the gateway 1000.

[0369] In other exemplary embodiments, the device 100, 100a, 100b, 100c, 300 is designed to output the protocol data units to be output in the same format as they are received. In other exemplary embodiments, the device 100, 100a, 100b, 100c, 300 is designed to insert a connection identifier determined, for example, based on the search 200, into the received protocol data unit PDU-1. In other exemplary embodiments, the device 100, 100a, 100b, 100c, 300 is designed to insert a (for example set) firewall flag (fw, see above), for example, based on the determined connection identifier, into the received protocol data unit PDU-1, whereby, in other exemplary embodiments, the firewall 125 can be informed that the device is to perform a check of the relevant protocol data unit PDU-1.

[0370] In other exemplary embodiments, the device 100, 100a, 100b, 100c, 300 is designed to change the type of the received protocol data unit PDU-1, for example, the message type.

[0371] In other exemplary embodiments, the device 100, 100a, 100b, 100c, 300 is designed to change, for example, correct the length of the received protocol data unit PDU-1, for example in the case of received padded ("padded") data units, for example associated with a CAN-FD data frame. In other exemplary embodiments, this can be useful, for example, when the received protocol data unit PDU-1 is to be forwarded to another output interface (for example other than the CAN-FD type), for example with its actual (and for example not due to the padding) length.

[0372] In other exemplary embodiments, the device 100, 100a, 100b, 100c, 300 is designed to load, for example dynamically, i.e. during operation of the device, a table associated with or characterizing at least one search tree B-1, B-2, wherein the loaded data DAT can, for example, be at least temporarily stored in the storage device 304. In other exemplary embodiments, therefore, for example, a second search tree B-2 can be loaded into the device, for example, from the outside, and at a specifiable point in time, for example when resetting the device, the content of the second search tree B-2 can be transferred to the first search tree B-1, so that the first search tree B-1 with the new content based on the loaded second search tree B-2 can be used thereafter, for example, for the hardware-based search 200.

[0373] In other exemplary embodiments, the device 100, 100a, 100b, 100c, 300 may selectively use, for example, a search tree B-1 or a first search tree B-1 and a second search tree B-2 or corresponding tables, wherein, for example, in some exemplary embodiments, a storage area available for one or more search trees or corresponding tables can be used for one search tree B-1 or one table, wherein, for example, in other exemplary embodiments, a storage area available for one or more search trees or corresponding tables can be used for two search trees B-1, B-2 or corresponding tables, so that, for example, in the case of two search trees, the storage capacity for each search tree is substantially halved compared to the case of a single search tree B-1.

[0374] In other exemplary embodiments, the first buffer memory E5 ( Fig.18) can be used, for example, for rate adjustment, i.e., for example, for adjusting the rate at which the received protocol data unit PDU-1 is output via at least one output interface 120a of the second number of output interfaces 120 and / or the received protocol data unit PDU-1 is checked by means of the firewall 125 before optional output, if necessary. In other exemplary embodiments, the rate can be controlled 261 or regulated 262 ( Fig.17 ).

[0375] In other exemplary embodiments, the rate at which protocol data units are received by the gateway 1000 or its output interface 1012 and the rate at which protocol data units are sent to the gateway 1000 or its input interface 1012 may be specified, for example, by the processing pipeline 14 .

[0376] In other exemplary embodiments, the device 100 , 100a , 100b , 100c , 300 is designed to receive and / or check by means of the firewall 125 protocol data units that are incoming, for example in the form of “bursts”, ie intermittently.

[0377] In other exemplary embodiments, the search device E1 is designed to operate at a non-constant rate relative to processing (e.g. searching), because, for example, in the first search tree B-1, individual searches 200 for different received protocol data units may last for different lengths of time.

[0378] In other exemplary embodiments, security checks 12 that are optionally or selectively activated or performed for individual protocol data units, such as security checks performed by firewall devices 125, E10, may also result in a non-constant processing rate for protocol data units.

[0379] In other exemplary embodiments, this possibly non-constant processing rate can be at least partially compensated for or adapted to a prescribable rate, for example by using at least one of the buffer memories E5, E6, E8.

[0380] In other exemplary embodiments, the first buffer memory E5 is designed to output status information a6, for example, to a component 1012 of the gateway 1000 that provides the protocol data unit PDU-1, which indicates, for example, that a first fill level, for example, a configurable first fill level, of the first buffer memory E5 has been reached. In other exemplary embodiments, the first buffer memory E5 is designed to no longer output status information a6, for example, when the first fill level (or a predeterminable second fill level, which may be different from the first fill level, for example, for implementing a hysteresis) of the first buffer memory E5 is again fallen below, for example, the configurable first fill level.

[0381] In other exemplary embodiments, data units, such as protocol data units, arrive at the device 100 or the inspection device 125, E10, such as the firewall device 125, E10, via different link layers (LinkLayer) (e.g., connection layer), some of which are listed as examples below:

[0382] Case 1: Ethernet and / or IP / UDP containers:

[0383] In this case, the protocol data units are multiplexed into user datagram protocol UDP container packets, for example.

[0384] Case 2: CAN container:

[0385] In this case, the protocol data units are multiplexed into CAN container data frames (“Frames”), for example.

[0386] Case 3: CAN / LIN bus:

[0387] In this case, the received CAN or LIN data frame, for example a frame, carries a protocol data unit, for example carries exactly one protocol data unit.

[0388] In other exemplary embodiments, such as in the above-mentioned situations 1 and / or 2, the inspection device 125, E10 can be designed to: perform inspection 12, 12a, 12b on at least one layer of layers 2 to 4 of the ISO / OSI reference model (for example, "Layer 2-4 Firewall").

[0389] In other exemplary embodiments, for example in the above-mentioned situations 1 and / or 2, at least one frame filter (Frame Filter), such as a data frame filter, such as a layer 2 frame filter (Layer 2Frame Filter), can be provided, which checks or inspects or filters the container, for example, only checks or inspects or filters the container.

[0390] In other exemplary embodiments, the function of the data frame filter, such as the layer 2 frame filter, can be implemented by the inspection device 125, E10. In other exemplary embodiments, the function of the data frame filter, such as the layer 2 frame filter, can also be implemented by at least one other component besides the inspection device 125, E10.

[0391] In other exemplary embodiments, the checking device 125 , E10 checks “contained” PDUs, ie protocol data units contained in a respective container, for example only checks these “contained” PDUs, ie protocol data units contained in a respective container.

[0392] In other exemplary embodiments, layer 2-4 firewall / frame filter and layer 5 firewall functionality (which can be implemented, for example, by inspection device 125, E10) are linked, whereby, in other exemplary embodiments, for example, effective deep packet inspection can be achieved.

[0393] In other exemplary embodiments, for example, a layer 2 (or layer 2-4) firewall generates a first identification, such as a so-called TCAMID, for example as a result of an L2 lookup of the container, ie, for example based on an inspection of the container on protocol layer 2.

[0394] In other exemplary embodiments, the first identifier, such as TCAMID, is inherited by all contained PDUs in the relevant container, such as copied into the PDU header.

[0395] In other exemplary embodiments, a layer 5 firewall function, such as it can be implemented, for example, by the inspection device 125, E10, can link its inspection results (for layer 5, "L5"), such as local inspection results, for example, with the results of the L2-L4 firewall.

[0396] In other exemplary embodiments, through the process exemplarily described above, for example, deep packet inspection from layer 2 to layer 5 may be performed.

[0397] In other exemplary embodiments, for the above-described exemplary case 2 of the CAN container, in which the protocol data units are multiplexed into a CAN container data frame (“Frame”), a frame filter may be provided, which evaluates or checks the CAN ID, for example.

[0398] In other exemplary embodiments, for the above-mentioned case 1 (Ethernet and / or IP / UDP container), for example, a ternary content addressable memory (TCAM) can be used, which evaluates the packet content of at least one layer of Layer 2 to Layer 4.

[0399] For other exemplary embodiments, see Fig.23, relating to the apparatus according to these embodiments and / or the method according to these embodiments and / or the computer-readable storage medium according to these embodiments and / or the computer program according to these embodiments and / or the data carrier signal according to these embodiments and / or the gateway according to these embodiments for at least one of the following elements 400:

[0400] a) processing 401 a data unit, such as a data unit of a vehicle (such as a motor vehicle), such as a protocol data unit;

[0401] b) determining 402, e.g. searching for a connection identifier associated with the received protocol data unit, e.g. by means of a hardware component;

[0402] c) managing 403 at least one search tree;

[0403] d) performing 404 a hardware-based search for a connection identifier of a data unit, for example a data unit of a gateway for an automotive application, for example a protocol data unit, wherein the search can be performed with a logarithmic workload, for example;

[0404] e) routing 405 or communicating data units, such as data units of a vehicle (such as a motor vehicle), such as protocol data units, wherein, for example, these data units may be of different types;

[0405] f) allocating 406 a connection identifier, for example a protocol-independent connection identifier;

[0406] g) performing 407 multicast transmission;

[0407] h) determining 408 whether, for a specifiable received data unit (eg, protocol data unit), a connection identifier is not provided, eg, registered, eg, whether the connection identifier is not contained in a search tree;

[0408] i) software-based processing 409 of received data units (eg protocol data units) for which no connection identifier is provided, for example registered, for example containing the connection identifier in the search tree;

[0409] j) checking 410 the at least one received protocol data unit PDU-1, for example performing 12 a security check;

[0410] k) performing hardware-based firewall inspection 411 of protocol data units associated with at least one protocol operating on layer 5 of the ISO / OSI reference model, such as at least one service-oriented protocol, such as protocol data units associated with the Scalable Service-Oriented Middleware over IP (SOME / IP) protocol;

[0411] l) selectively applying 412 a routing function, such as a forwarding function, and / or a firewall function to the protocol data unit;

[0412] m) Performing an inspection 413 of the SOME / IP message, such as deep packet inspection, for example via CAN or CAN FD.

Claims

1. A device (100; 100a; 100b; 100c; 300) for processing data units, for example protocol data units, the device comprising: a first number of input interfaces (110) for receiving (10) protocol data units; and optionally, a second number of output interfaces (120) for outputting (14) protocol data units; and a checking device (125; E10), for example a firewall device, the checking device being designed to check (12) at least one received protocol data unit (PDU-1), for example to subject the at least one received protocol data unit to a security check, in, The inspection device (125; E10) is designed to at least temporarily perform at least one of the following inspections: a) a non-state-based, e.g. non-state-oriented, e.g. stateless, check (12a), e.g. with respect to the at least one received protocol data unit (PDU-1); b) a status-based, eg state-oriented, eg stateful, check (12b), eg with respect to the at least one received protocol data unit (PDU-1).

2. The device (100; 100a; 100b; 100c; 300) according to claim 1, in, The checking device (125) is designed as a hardware circuit, such as a pure hardware circuit.

3. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The checking device (125) is designed to selectively check the at least one received protocol data unit (PDU-1), for example based on first control information (SI-1), for example a bit flag.

4. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The checking device (125) is designed to check at least some of the received protocol data units (PDU-1), for example all received protocol data units (PDU-1).

5. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The checking device (125) is designed to: subject at least some of the received protocol data units (PDU-1) to a non-state-based check (12a); and, for example based on a result (ERG-12a) of the non-state-based check (12a), subject at least some of the received protocol data units (PDU-1) to a state-based check (12b).

6. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The checking device (125) is designed to check protocol data units, which are associated with at least one protocol operating on layer 5 of the ISO / OSI reference model, such as at least one service-oriented protocol, such as a protocol data unit associated with the Scalable Service-Oriented Middleware Protocol based on IP, namely the SOME / IP protocol.

7. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The checking device (125) is designed to check at least one of the following elements, such as header data, such as header data, such as at least one of the following elements of a protocol data unit associated with the SOME / IP protocol, during the checking (12), such as during the non-state-based checking (12a): a) a message identification (H1), for example a message ID, for example associated with at least one assignable valid message identification, wherein the at least one assignable valid message identification can be organized, for example, in the form of a table; b) Service identification (H1a), such as service ID; c) Method ID (H1b); d) length (H2), for example relating to a specifiable length; e) a request identifier (H3), such as a request ID, such as associated with a specifiable value; f) Client identification (H3a), such as client ID; g) Session identifier (H3b), such as session ID; h) Protocol version (H4); i) Interface version (H5), such as Interface Version; j) Type (H6), such as message type, such as Message Type; j) Return value (H7), such as a return code, such as Return Code.

8. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The checking device (125) is designed to check (1210), for example within the framework of the state-based checking (12b): a) whether a response message (RESP-MSG; E33), such as a Response Message, has been received after sending a request message (E32), such as a request message associated with a response message, such as a Request Message; and / or b) whether the received response message (RESP-MSG; E33), for example, Response Message, is associated with a previously sent request message (E32); and / or c) Whether the received response message is received within a specifiable response time (A5), the response time being related to sending the request message associated with the response message.

9. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The checking device (125) is designed to discard (34) the at least one received protocol data unit (PDU-1) or not discard (38) the at least one received protocol data unit, for example, leaving it unchanged, for example, based on the checking (12).

10. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The checking device (125) is designed to modify (36) or influence the at least one received protocol data unit (PDU-1) and / or the output of the at least one received protocol data unit (PDU-1), for example via the output interface (120).

11. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The inspection device (125) is designed to perform at least one of the following elements: a) Attack identification (40), such as intrusion detection; b) marking (41) the at least one received protocol data unit (PDU-1), for example based on the checking (12) and / or based on a result (ERG) of the checking (12); c) outputting and / or forwarding (42) the at least one received protocol data unit (PDU-1), for example by means of a multicast mechanism, for example to at least one software component (134), for example for evaluation or execution, for example further evaluation or execution, of attack identification, for example software-based attack identification; d) outputting and / or forwarding (43) the at least one received protocol data unit (PDU-1), for example by means of a unicast mechanism, for example to at least one software component (134) or the at least one software component (134), for example for evaluation or execution, for example further evaluation or execution, of attack identification, for example software-based attack identification; e) determining (44) and / or evaluating (45) a service identification message, such as a service discovery message, which is based on a network protocol, such as a connectionless network protocol, such as a User Datagram Protocol UDP; f) Determining (46) and / or evaluating (47) a protocol data unit of the AUTOSAR I-PDU type, for example for a check, such as a safety check.

12. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, The device has at least one memory (E5, E6, E8) for at least temporarily storing one or more protocol data units or parts of one or more protocol data units.

13. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, The device has adjustment means (E4) designed to change (266) a PDU identifier (MSG-ID) associated with a received protocol data unit (PDU-1), for example to normalize it.

14. The device (100; 100a; 100b; 100c; 300) according to at least one of the preceding claims, in, The checking device (125) is designed to use a connection identifier (VB-ID) associated with a received protocol data unit (PDU-1), for example for determining a service and / or an identification associated with, for example, the at least one received protocol data unit (PDU-1).

15. A method, such as a computer-implemented method, for processing data units, such as protocol data units, for a device (100; 100a; 100b; 100c; 300), such as according to at least one of the preceding claims, comprising: a first number of input interfaces (110) for receiving (10) protocol data units; and optionally, a second number of output interfaces (120) for outputting (14) protocol data units; and an inspection device (125), such as a firewall device, which is designed to inspect (12) at least one received protocol data unit (PDU-1), such as to subject it to a security inspection, in, The method has: receiving (10) at least one protocol data unit (PDU-1); By means of the checking means (125), at least one received protocol data unit (PDU-1) is checked (12), wherein the checking means (125; E10) at least temporarily performs at least one of the following checks: a) a non-state-based, e.g. non-state-oriented, e.g. stateless, check (12a), e.g. with respect to the at least one received protocol data unit (PDU-1); b) a status-based, eg state-oriented, eg stateful, check (12b), eg with respect to the at least one received protocol data unit (PDU-1).

16. The method according to claim 15, The method has at least one of the following elements: a) outputting (14) said at least one protocol data unit (PDU-1), e.g. based on said checking (12); b) discarding (15; 34) said at least one protocol data unit (PDU-1), for example based on said checking (12).

17. The method according to at least one of claims 15 to 16, in, The checking means (125) subjects at least some of the received protocol data units (PDU-1) to a non-state-based check (12a) (1200); and, for example based on a result (ERG-12a) of the non-state-based check (12a), subjects at least some of the received protocol data units (PDU-1) to a state-based check (12b) (1202).

18. The method according to at least one of claims 15 to 17, in, The inspection device (125) performs at least one of the following elements: a) Attack identification (40), such as intrusion detection; b) marking (41) the at least one received protocol data unit (PDU-1), for example based on the checking (12) and / or based on a result (ERG) of the checking (12); c) outputting and / or forwarding (42) the at least one received protocol data unit (PDU-1), for example by means of a multicast mechanism, for example to at least one software component (134), for example for evaluation or execution, for example further evaluation or execution, of attack identification, for example software-based attack identification; d) outputting and / or forwarding (43) the at least one received protocol data unit (PDU-1), for example by means of a unicast mechanism, for example to at least one software component (134) or the at least one software component (134), for example for evaluation or execution, for example further evaluation or execution, of attack identification, for example software-based attack identification; e) determining (44) and / or evaluating (45) a service identification message, such as a service discovery message, which is based on a network protocol, such as a connectionless network protocol, such as a User Datagram Protocol UDP; f) Determining (46) and / or evaluating (47) a protocol data unit of the AUTOSAR I-PDU type, for example for a check, such as a safety check.

19. The method according to at least one of claims 15 to 18, The method has at least one of the following elements: a) receiving (1300) data, for example in the form of a data frame (DR); b) determining (1302), for example by means of a ternary content addressable memory TCAM, an endpoint (EP) associated with the reception (1300) of said data, for example an input interface associated with the reception (1300) of said data, for example a socket, for example a User Datagram Protocol UDP socket; c) decomposing (1304) the data frame (DR) into at least one protocol data unit (S-PDU1, S-PDU2, S-PDU3), for example, an S-PDU; d) assigning (1306) an identifier (ID-EP) characterizing the endpoint (EP) to the at least one protocol data unit (S-PDU1, S-PDU2, S-PDU3); e) checking (1308) at least one of the following elements of the at least one protocol data unit (S-PDU1, S-PDU2, S-PDU3), for example S-PDU, for example, by means of the device (100; 100a; 100b; 100c; 300) or the checking device (125): e1) a message identifier (H1), for example a message ID, e2) a request identifier (H3), for example a request ID, e3) a protocol version (H4), e4) an interface version (H5), for example an Interface Version, e5) a type (H6), for example a message type, for example a Message Type; f) Based on the checking (1308), f1) outputs (1310) or forwards the data, for example in the form of the data frame (DR), or f2a) discards (1312) the data, for example the data frame (DR) and / or f2b) increments (1314) a counter (DROP-CNT).

20. The method according to at least one of claims 15 to 19, The method has at least one of the following elements: a) receiving (1320) data, for example in the form of a data frame (DR'); b) determining (1322), for example by means of a ternary content addressable memory TCAM, an endpoint (EP′) associated with the reception (1320) of said data, for example an input interface associated with the reception (1320) of said data, for example a socket, for example a controller area network CAN socket; c) decomposing (1324) the data frame (DR') into at least one protocol data unit (I-PDU1, I-PDU2, I-PDU3), for example an I-PDU; d) assigning (1326) an identifier (ID-EP') characterizing the endpoint (EP') to the at least one protocol data unit (I-PDU1, I-PDU2, I-PDU3); e) checking (1328) at least one of the following elements of the at least one protocol data unit (S-PDU1, S-PDU2, S-PDU3), for example an I-PDU, for example by means of the device (100; 100a; 100b; 100c; 300) or the checking device (125): e1) a message identification, for example a message ID, e2) a length; f) based on the checking (1328), f1) outputs (1330) or forwards the data, for example in the form of the data frame (DR'), or f2a) discards (1332) the data, for example the data frame (DR') and / or f2b) increments (1334) a counter (DROP-CNT').

21. An apparatus (100; 100a; 100b; 100c; 300) for implementing the method according to at least one of claims 15 to 20.

22. A computer-readable storage medium (SM) comprising instructions (PRG) which, when executed by a computer (302), cause the computer to carry out at least some of the steps (10, 12) of the method according to at least one of claims 15 to 20.

23. A computer program (PRG) comprising instructions which, when executed by a computer (302), cause the computer to carry out at least some of the steps (10, 12) of the method according to at least one of claims 15 to 20.

24. A data carrier signal (DCS) transmitting and / or representing a computer program according to claim 23.

25. A gateway (1000), for example an automotive gateway (1000), comprising at least one device (100; 100a; 100b; 100c; 300) according to at least one of claims 1 to 14 and / or 21.

26. An application (400) of the device (100; 100a; 100b; 100c; 300) according to at least one of claims 1 to 14 and / or 21 and / or the method according to at least one of claims 15 to 20 and / or the computer-readable storage medium (SM) according to claim 22 and / or the computer program (PRG) according to claim 23 and / or the data carrier signal (DCS) according to claim 24 and / or the gateway (1000) according to claim 25 for at least one of the following elements: a) processing (401) a data unit, such as a vehicle, such as a data unit of a motor vehicle, such as a protocol data unit; b) determining (402), for example searching for, for example by means of a hardware component (132), a connection identifier (VB-ID-1) associated with the received protocol data unit (PDU-1); c) managing (403) at least one search tree (B-1, B-2); d) performing (404) a hardware-based search for a connection identifier (VB-ID) of a data unit, such as a data unit of a gateway for an automotive application, such as a protocol data unit, in, For example, the search can be performed with a logarithmic workload; e) routing (405) or communicating data units, such as data units of a vehicle, such as data units of a motor vehicle, such as protocol data units, wherein, for example, the data units can be of different types; f) assigning (406) a connection identifier (VB-ID), for example a protocol-independent connection identifier; g) performing (407) multicast transmission; h) determining (408) whether for a specifiable received data unit, for example a protocol data unit (PDU-1), a connection identifier (VB-ID) is not provided, for example registered, for example, whether the connection identifier is not contained in the search tree (B-1, B-2); i) software-based processing (409) of a received data unit, for example a protocol data unit (PDU-1), for which no connection identifier (VB-ID) is provided, for example registered, for example containing a connection identifier in the search tree (B-1, B-2); j) checking (410; 12) the at least one received protocol data unit (PDU-1), for example performing a security check; k) performing hardware-based firewall inspection (411) of protocol data units associated with at least one protocol operating at layer 5 of the ISO / OSI reference model, such as at least one service-oriented protocol, such as protocol data units associated with the Extensible Service-Oriented Middleware Protocol over IP, i.e., SOME / IP protocol; l) selectively applying (412) a routing function, such as a forwarding function, and / or a firewall function to the protocol data unit; m) Inspecting (413) the SOME / IP message, for example via CAN or CAN FD, for example deep packet inspection.

Citation Information

Cited By

  • Network system fast addressing method and device and storage medium

    CN121603475A

  • Data processing method, communication system, storage medium, electronic apparatus and computer program product

    WO2026144412A1