METHOD FOR VERIFYING THE VALIDITY OF SENSOR DATA OF AN ETHERNET ON-BOARD NETWORK
Patent Information
- Application Number
- DE502020009656
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-12-20
- Filing Date
- 2020-12-16
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2040-12-16
AI Technical Summary
Current automotive Ethernet systems lack effective mechanisms to validate timestamps, which is crucial for reliable sensor data fusion and synchronization, especially in safety-critical applications like ADAS, where incorrect timestamps can lead to data loss and operational safety issues.
A method is introduced to determine the transit time, maximum speed, and type of transmission medium of signal paths within the Ethernet on-board network, allowing for the detection of timestamp validity and potential attacks, using existing IEEE 802.1AS and PTP protocols without requiring additional hardware.
This approach enhances synchronization accuracy and data fusion reliability, reduces the load on data buses, and improves security by detecting errors and attacks, all while being platform-independent and cost-effective, without the need for additional hardware or proprietary protocols.
Description
Field
[0001] The present invention relates to a method for testing the validity of sensor data background
[0002] Automotive manufacturers (OEMs) and Tier 1 automotive suppliers are preparing the next generation of architecture for vehicle control units, or electronic control units (ECUs). One development is the so-called "zone-oriented architecture," in which ECUs are grouped into zones, such as a front right door zone. A key difference from previous architectures is that the controllers are located in specific physical or spatial positions to optimally capture data from the sensors located there. For example, an ECU that collects data from a sensor in the right front door can be positioned in the right front door zone.
[0003] Also under consideration is the localization or distribution of software execution for features and applications across other controllers and processors. Such localization or distribution can be part of an optimization process and can also be used in the event of an error or failure, for example, of an electronic control unit (ECU). This localization or distribution is referred to as dynamic migration or simply migration. Series production for the dynamic migration of software to other ECUs / processors within the vehicle is expected shortly.
[0004] Ethernet can be the network of choice for connecting electronic control units (ECUs) in a network. Ethernet technology is becoming increasingly popular for the electrical systems of vehicles and automotive suppliers. The use of Ethernet technology requires an effective synchronization concept. Existing Ethernet systems can utilize an implementation of the IEEE 802.1AS time synchronization standard. Two variants that have attracted particular attention are the selection of the specific 802.1AS revision and the time range of the 802.1AS revision, the latter being a mandatory requirement for the former. Other protocols outside of the physical transmission standards include Ethernet AVB and its successor, Ethernet TSN. Ethernet AVB has already been adopted for series production in automobiles. A key sub-standard for Ethernet TSN and AVB is the IEEE 802.1AS time synchronization standard, which is dependent on the main IEEE 802.1 standard for higher-layer LAN protocols (bridging).Both standards use the Precision Time Protocol (PTP) of IEEE 1588 to establish a common time base in an Ethernet network.
[0005] Ethernet connections support a variety of switching protocols at Layer 3 of the OSI model for the transmission of data packets between senders and receivers. Higher protocol layers handle the segmentation of the data stream into packets, process communication between communicating systems, the translation of data into a system-independent format, and finally, the provision of functions for applications.
[0006] Almost all Ethernet communication networks used in vehicles employ a time synchronization protocol that provides a global time base for the network that is synchronized across all network devices. The prevalence of time-synchronized network devices is expected to increase further in the future.
[0007] The IEEE 802.1AS standard provides such a protocol for time synchronization. Starting with a so-called "best clock" in the network, also known as the Grandmaster Clock, a master-slave clock hierarchy is established. The Grandmaster provides the time base for the network, to which all other network devices synchronize. The Grandmaster is determined using the Best Master Clock Algorithm (BMCA) and announced within the network. To this end, IEEE 802.1AS-compliant network devices send announcement messages with information about their internal clock to directly connected network devices. This information about the internal clocks reveals the accuracy of each clock, its reference point, and other characteristics that allow the best clock in the network to be determined.A recipient of such an announcement message compares the received information with the characteristics of its own internal clock and any messages already received from another port, comparing them with information about clocks on other network devices. It accepts a clock located on another network device if it has better clock parameters. After a short time, the best clock on the network is determined, which then becomes the Grandmaster. Time synchronization messages are then distributed across the network from the Grandmaster.A network device that receives a time synchronization message does not simply forward it, but corrects the time information by the previously determined latency on the connection over which it receives time synchronization messages from a directly connected network device, as well as by the internal processing time, before it forwards the time synchronization message with the corrected time information.
[0008] In the clock hierarchy according to IEEE 802.1AS and the "generalized precision time protocol" (gPTP) defined therein, only one network device provides the network's best clock. This network device thus controls and regulates the entire time of the vehicle. All other clocks in network devices on the network are synchronized exclusively with this single clock. Some vehicle manufacturers even synchronize networks of other standards, such as CAN, via this Ethernet time master, so that the system time is communicated to almost all network devices in the vehicle by the network device providing the grandmaster. This defines a single network device as a single point of failure in the network or vehicle, whose failure or manipulation can have serious consequences for the vehicle's operational safety. For example,In vehicles with a high degree of driver assistance systems or with (partially) autonomous driving systems, a large number of sensor data points acquired within a narrow time window are processed together to derive corresponding control signals for the vehicle's actuators. Accurate time recording of sensor data can also be of great importance for documentation purposes, for example, when stored in log files, the analysis of which can be used to reconstruct malfunctions or operator errors. The latter is of particular interest to insurance companies and law enforcement agencies. Therefore, a secure, synchronized provision of this time information is essential.
[0009] EP 2 759 174 A1 determines the difference between the counters of the receiving node and the receiving node using a timestamp and error calculation unit. The error value is calculated from the difference between the two counter values (absolute) or from the difference between the drift of the two counter values.
[0010] EP 2 490 357 A2 describes a method for synchronizing a local estimate of the global network time of a receiving node in a network with a global network time reference from at least the first and second transmitting nodes in the network. The clock synchronization method allows a free-running node in an avionics network to calculate whether a node has been synchronized or not. In the case of detection, it is proposed to set a sync flag.
[0011] US 2008 183 896 A1 describes how, if it is determined that the communication loss lasts too long, which is predefined for the network and is a function of the maximum drift rate of the clock at a server with respect to the clock at that server's clock source, the receiving server declares its time parameters invalid.
[0012] EP 2 191 300 A1 discloses a sensor network for recording earthquake data. For this purpose, clock update cycles are determined based on the maximum tolerated time deviation and the determined (current) frequency drift.
[0013] EP 2 382 829 A1 discloses a method for synchronizing a reference frequency of a base station transceiver (BTS) with the reference frequency of a base station controller (BSC). The method comprises a sequence of steps in which synchronization packets are transmitted and timestamped with a transmission time stamp and a reception time stamp. An evaluation of the network delivery is performed after completion of a
[0014] WO 2019 / 197233 A1 of the applicant describes a method for operating an Ethernet on-board computer of a motor vehicle, in which the following steps are carried out: determining a connection delay of a first signal on a first connection path between a first control unit of the Ethernet on-board computer and a second control unit of the Ethernet on-board computer; determining a maximum speed of the first connection path based on the connection delay; and determining a transmission medium of the first connection path based on the connection delay and the maximum speed.
[0015] WO 2019 / 081463 A1 of the applicant discloses a method for processing an Ethernet message with an incorrect timestamp, in which the following steps are performed: receiving an Ethernet message with a timestamp by a control unit; determining a time difference between a global time of the timestamp and a local time of a clock of the control unit; and recognizing the timestamp of the Ethernet message as incorrect, wherein the global time of the timestamp is replaced by the local time of the clock of the control unit if the timestamp is recognized as incorrect.
[0016] DE 10 2018 207684 A1 describes a method for determining the synchronization accuracy of a time synchronization of a first communication unit, the method comprising: sending a time request via a communication channel at a corresponding transmission time from the first communication unit to a second communication unit; receiving a time response, wherein the time response includes a synchronization time indication of the second communication unit, at a corresponding reception time at the first communication unit; and determining the synchronization accuracy based on the transmission time and the reception time.
[0017] The observation period is evaluated. If it is high enough, a confidence level of the received synchronization packets is determined. Only if the confidence level is above a threshold is a correction made to the reference frequency of the oscillator in the base station transmitter-receiver.
[0018] The number of environmental sensor systems in automobiles has been steadily increasing for years. In 2016, in addition to the existing ultrasonic and radar sensors, a laser scanner was also introduced into series production. Despite the near-standard use of various sensor systems in automobiles, questions remain regarding the fusion of the acquired sensor data. Data fusion can compensate for the weaknesses of individual sensor systems and ensure greater reliability (robustness) through redundancy. To ensure that data quality for ADAS systems remains stable even in traffic jams or urban environments, several sensor systems monitoring the same field of view are required during safety-critical maneuvers, such as emergency braking. The term sensor fusion describes the merging of data from different sensors.Sensor fusion aims to achieve a higher quality of data in any given aspect compared to the individual data obtained from each sensor. A further distinction is made between homogeneous and heterogeneous sensor networks. In a homogeneous sensor network, all sensors operate with the same physical measurement principle and are therefore subject to the same physical limitations (such as range, accuracy, and noise sensitivity). In heterogeneous sensor networks, on the other hand, different measurement techniques are used, so that weaknesses of one sensor can potentially be compensated for by another. Sensor fusion is thus categorized as complementary, competitive, or cooperative.
[0019] Several approaches for detecting changes to the configuration or structure of a communication network using network time synchronization are known from the state of the art. To leverage the added benefits of sensor fusion, monitoring the data streams and their correlation is necessary. Unauthorized changes to the network configuration can lead to disruptions, potentially including the preparation of an attack that intercepts messages for analysis and may forward modified messages. This can be used to prevent or at least disrupt secure and proper operation.
[0020] Currently, there are no solutions that validate timestamps for validity. So, how should a fusion unit behave when it needs to merge two packets, but the timestamps don't match? This doesn't necessarily mean the data is old and unusable, but rather that there's an error in the timestamp. Furthermore, it's worth noting that virtually all packets are important, and normally none can be omitted. For example, in an ADAS system, there's no time to request lost packets again. Safety-critical problems caused by data loss have serious consequences and can lead to incorrect control of actuators within the system.
[0021] It is therefore an object of the invention to provide a method which, if timestamps are incorrectly assigned, can detect this and, through this detection, can check whether the data belong together, since they have different temporal origins, in order to use them reliably through sensor fusion.
[0022] This problem is solved by the method specified in claim 1 and the control unit specified in claim 11. Embodiments and further developments are specified in the respective dependent claims.
[0023] In other words, the purpose of the invention is to reliably monitor and secure the time synchronization in the vehicle electrical system.
[0024] The time can be corrupted by errors, temperature, or even attacks. Especially with regard to automated driving, time-controlled execution of actions is becoming increasingly important, such as the synchronization of sensors (camera, lidar, radar, etc.) and their data streams. For these functions in particular, plausibility checks are necessary to verify whether an operation can be taken over by the vehicle, for example, or whether the driver should remain in control. The advantage of the invention lies in the provision of mechanisms and methods for validating the timestamp of sensor messages and verifying their validity.
[0025] This method can detect whether timestamps have been deliberately falsified and whether a potential attack is present. Furthermore, the method detects whether a timestamp might be invalid even if no synchronization has yet occurred. A timestamp can also be faulty, for example, due to a so-called bit transposition, which is detected by the described approach. If the last successful synchronization is unknown, this can be determined using the specified method. This method enhances security in the Ethernet environment.
[0026] The advantage of the invention lies in the fact that it improves and guarantees the synchronization accuracy, and thus also the fusion accuracy, of sensor data within the network, since current standards such as Ethernet or AUTOSAR do not yet offer automotive-specific tools. This means that malfunctions or potential errors / attacks can be detected using the presented approach. Implementing such mechanisms and protocols eliminates the need for additional hardware and proprietary protocols. Furthermore, this means that the number of communication technologies in the vehicle does not need to increase, nor does it require the installation or wiring of additional cables.
[0027] A further advantage is that the method reduces the load on a vehicle's data bus. Less synchronization is required, which also has a positive impact on microcontroller resources, reduces potential errors, and lowers power consumption. The significant advantages of the invention further stem from the fact that Ethernet can execute time-controlled actions without additional hardware components such as temperature-controlled crystals or safety modules. The Ethernet network on-board network according to the invention is improved in terms of cost and reliability.
[0028] This method can be implemented in particular in the form of software that can be distributed as an update or upgrade to existing software or firmware of participants in the network and thus represents a standalone solution.
[0029] The detection makes it possible to find out, for example, whether a neighboring control unit is exposed to particular danger, such as excessively high or low temperature, a fault or attack.
[0030] Detecting modifications to the network provides an additional method for ensuring data security and functional safety within the vehicle's electrical system. For example, if a modified control unit is used, this will likely go unnoticed by both the driver and the workshop – the Ethernet network and the control units can identify faults using these methods.
[0031] The invention and the resulting solution are particularly interesting for the automotive sector, as reliability and safety over Ethernet are of paramount importance in automobiles and will continue to grow in importance. In the coming years, sensors (cameras and radar) will also transmit uncompressed data over Ethernet. Such data rates necessitate further technologies to make the Ethernet system more reliable and performant. This method contributes to enabling these applications.
[0032] A persistent problem today, and with every new system, is the dependence on communication interfaces and their support. The invention described here enables much more platform-independent development. Implementing this invention allows for a longer implementation timeframe and reduces necessary maintenance.
[0033] More precise synchronization allows, for example, real-time critical actions (sensor fusion) to be executed more safely and reliably. The quality of sensor data fusion is improved, ultimately leading to a better environmental model and better trajectories.
[0034] In the field of ADAS, however, it is generally not economical to equip all network participants with sufficient hardware for end-to-end encrypted communication. The described method requires significantly fewer hardware resources and can be implemented with existing systems, thus significantly increasing the security level without necessarily entailing higher manufacturing costs for the network or connected devices.
[0035] The use of the newly introduced Ethernet protocol in automobiles necessitates mechanisms that leverage simple techniques and inherent technological properties to eliminate the need for expensive implementations and additional hardware. Early detection of attacks and malfunctions through early analysis of communication paths allows for the identification of vulnerabilities and errors before the vehicle is delivered. The network system according to the invention offers improved cost and reliability. The invention more clearly defines the system's testability, thereby reducing testing costs. Furthermore, the invention provides transparent security functionality.
[0036] The method can be implemented in a control unit and an on-board network consisting of various control units can be used, which ensures improved protection of time synchronization.
[0037] This problem is solved by the method specified in claim 1 and the control unit specified in claim 11. Embodiments and further developments are specified in the respective dependent claims.
[0038] In one embodiment of the procedure for verifying the validity of sensor data from an Ethernet on-board computer, the following steps will be carried out in a motor vehicle: a) Determining a propagation delay (9) of a first signal (10) on a first link path (6) between a first control unit (3) of the Ethernet network (2) and a second control unit (4) of the Ethernet network (2); b) Determining a maximum speed (11) of the first link path (6) based on the propagation delay (9); and c) Determining a type of transmission medium (12) of the first link path (6) based on the maximum speed (11).
[0039] In addition, the following are performed: identification of at least one first control unit (3) of the Ethernet network; synchronization of at least one first control unit of the Ethernet network; determination of the synchronization interval; determination of a drift of a timer of the first control unit; determination of a timestamp of the first control unit; reading of a timestamp or querying of the time of the first control unit; comparison of the timestamp with a reference clock of the Ethernet network; performance of a runtime measurement; determination of the speed of the associated clock generator; determination of the time difference of the synchronization interval and determination of the last synchronization.
[0040] Additionally, by determining the propagation time of a first signal, the maximum speed of the first connection path, and the type of transmission medium of the first connection path, an entropy source can be formed from which at least one dynamic key for the connection path is determined, which is used to encrypt a time synchronization message for connection path 6.
[0041] In a further embodiment of the procedure, the drift of the timer is determined using the IEEE 802.1AS protocol.
[0042] A further embodiment of the invention is characterized in that the comparison of the timestamp with a reference clock of the Ethernet on-board unit (3) is carried out by forming a difference in the form TDeviation = TRReference-TSuspicious.
[0043] Another embodiment of the invention is characterized by the fact that the speed of the clock generator is determined using the PTP NRR (Neighbor Rate Ratio) method.
[0044] A further embodiment of the invention is characterized in that the type of transmission medium and the determination of the synchronization interval, the determination of a drift of a timer of the first control unit, the determination of a timestamp of the first control unit, the determination of the speed of the associated clock generator, the determination of the time difference of the synchronization interval, the determination of the last synchronization are communicated to a program in the Ethernet network and a connection path selection of the program is adapted depending on the type of transmission medium.
[0045] Another embodiment of the invention is characterized by the fact that the type of transmission medium is determined as optical, copper or wireless.
[0046] A further embodiment of the invention is characterized in that a transmission security value (15), which describes a probability of loss of data transmitted via the first connection path (6), is assigned to the first connection path (6) based on the type of transmission medium (12).
[0047] A further embodiment of the invention is characterized in that propagation times of a plurality of signals on the first connection path are determined and the fastest propagation time of the plurality of signals is selected, whereby the maximum speed of the first connection path is determined on the basis of the fastest propagation time.
[0048] A further embodiment of the invention is characterized in that a transit time of a second signal on a second connection path different from the first connection path between the first control unit and the second control unit is determined, and a maximum speed of the second connection path is determined, wherein a type of transmission medium (19) of the second connection path (7) is determined on the basis of the maximum speed (11) of the second connection path (7).
[0049] Another embodiment of the invention is characterized in that the method is carried out after a change of the first control unit (3) from a normal operating mode to an energy-saving mode and / or from the energy-saving mode to the normal operating mode.
[0050] A further embodiment of the invention is characterized in that the propagation time of the first signal is determined with the first control unit and a propagation time of a third signal is determined on a third connection path between the second control unit (4) and a third control unit of the Ethernet network with the third control unit (5), which is only indirectly connected to the first control unit, wherein the determination of the propagation time of the third signal is triggered by a service message sent from the first control unit to the third control unit.
[0051] The design of the control unit for an Ethernet network, which is configured as a first control unit, enables a signal to be sent to a second control unit of the Ethernet network and the signal to be received from the second control unit; a propagation delay of the signal on a connection path to the second control unit to be determined; a maximum speed of the connection path to be determined based on the propagation delay and a type of transmission medium of the connection path to be determined based on the maximum speed, wherein the control unit comprises at least one microprocessor, volatile memory and non-volatile memory, at least two communication interfaces, a synchronizable timer, and non-volatile memory program instructions which, when executed by the microprocessor, are implementable and executable in at least one embodiment of the method according to claims 1 to 10.
[0052] Another embodiment of the Ethernet on-board network for a motor vehicle is characterized in that the first control unit is connected to a second control unit at least via a connection path, and the first control unit is designed according to claim 11.
[0053] Another embodiment of the Ethernet network is characterized by the fact that the Ethernet network has a third control unit, which is only indirectly connected to the first control unit and is directly connected to the second control unit via a third connection path, wherein the third control unit is configured to determine a propagation delay of a third signal on the third connection path, wherein the first control unit is configured to trigger the determination of the propagation delay of the third signal by sending a service message to the third control unit.
[0054] One embodiment is represented by a computer program product. This computer program product comprises instructions which, when executed by a computer, cause the computer to execute the method according to one or more of claims 1-10.
[0055] One embodiment is provided on a computer-readable medium on which the computer program product according to claim 12 is stored.
[0056] A computer program product according to the invention contains instructions which, when executed by a computer, cause it to execute one or more embodiments and further developments of the method described above.
[0057] The computer program product can be stored on a computer-readable medium or data carrier. The data carrier can be physically embodied, e.g., as a hard drive, CD, DVD, flash memory, or the like; however, the data carrier or medium can also comprise a modulated electrical, electromagnetic, or optical signal that can be received by a computer using a suitable receiver and stored in the computer's memory.
[0058] A control unit according to the invention comprises, in addition to a microprocessor, non-volatile and volatile memory, and a timer, at least one physical communication interface. The components of the control unit are communicatively interconnected by means of one or more data lines or buses. The memory of the control unit contains computer program instructions which, when executed by the microprocessor, configure the network device to implement one or more embodiments of the method described above.
[0059] The method according to the invention can be implemented with existing network devices, requiring, if necessary, only adjustments to the software or the state machines used for receiving and processing time synchronization messages. These adjustments ensure that only the time synchronization messages originating from the Grandmaster Clock determined during initialization are used for synchronizing the clocks, while still forwarding the additional time synchronization messages instead of simply deleting them. This results in minimal additional costs, if any, for implementation. Existing systems can also be configured to implement the method by appropriately modifying the software. A further advantage of the method according to the invention is that the underlying hardware platform is irrelevant, as long as it supports synchronization according to the IEEE 802.1AS standard. Short description of the drawings
[0060] The invention is explained below by way of example with reference to the drawing. The drawing shows: Fig. 1a a schematic top view of a motor vehicle with an embodiment of an Ethernet on-board network according to the invention; Fig. 1 a schematic representation of the Ethernet on-board network with a first control unit, a second control unit and a third control unit, which are connected by a first connection path, a second connection path and a third connection path; Fig. 2 a complete sequence of the method and the determination of the current time of the node under investigation and its clock generator properties; Fig. 3 a flowchart for encrypting the time synchronization messages to determine the type of transmission medium of the respective connection path; Fig. 4 a representation of a sawtooth model of a frequency drift during successful time synchronization; Fig. 5 a graphical representation of the calculation of the period of asynchronicity; Fig. 6a a sequence of determining a sensor offset during sensor fusion; Fig.6b Determining the time of the last successful synchronization; Fig. 7 A flowchart for determining the individual quartz frequency; Fig. 8 A flowchart for calculating the key and sending the messages; Fig. 9 A flowchart for the timing of key use; Fig. 10 A flowchart for adapting a program in the Ethernet network; Fig. 11 A flowchart for adapting a program in the Ethernet network; Fig. 12 A flowchart for determining and storing a signal's propagation time; Fig. 13 A flowchart for an example of adapting a program in the Ethernet network; Fig. 14 A flowchart for an example of adapting a program in the Ethernet network; Fig. 15 Flowchart for evaluating the use of received data based on the last successful synchronization time; Fig. 16 Structure of a control unit; Fig.17 Encrypted links with a generated dynamic key from the communication of the control units; Fig. 18 a representation of the use case of data fusion; Fig. 19 a representation of the use case of data fusion with a data recorder; Fig. 20 a representation of an assignment of correct data in a data fusion; Fig. 21 a representation of an incorrect assignment of data in a data fusion; Fig. 22 a process for retrospectively deleting data if the synchronization time is above the threshold.
[0061] Identical or similar elements can be referenced in the figures using the same reference symbols. Description of exemplary implementations
[0062] Fig. 1a Figure 1 shows a top view of a motor vehicle 1. The motor vehicle 1 has an Ethernet electrical system 2. According to the exemplary embodiment, the Ethernet electrical system 2 has a plurality of control units 3, 4, 5, which can also be referred to as control devices or control units. The control units are interconnected by communication paths. Due to the existing topology of the Ethernet electrical system 2 in the exemplary embodiment, there are several parallel communication paths between the control units. The communication paths can, for example, be made of different media types or materials.
[0063] With the increasing number of Ethernet variants, dynamic speed adjustment will also become more common. This means, for example, that the speed can be changed during operation. A 10 Gbit / s connection, for instance, could be reduced to 100 Mbit / s to save energy. Because this is a dynamic function, the vehicle's electrical network may be configured differently after delivery or initial installation than after a software update or in a malfunctioning situation.
[0064] The Ethernet network 2 comprises at least one first control unit 3, a second control unit 4, and additionally a third control unit 5. The first control unit 3 is connected to the second control unit 4 via a first connection path 6. Furthermore, according to the exemplary embodiment, the first control unit 3 is also connected to the second control unit 4 via a second connection path 7.
[0065] The first control unit 3, the second control unit 4, and / or the third control unit 5 can, for example, be configured as a control device or network switch. The second control unit 4 and the third control unit 5 are connected to each other by a third connection path 8.
[0066] According to the embodiment of Fig. 1a The first control unit 3 and the second control unit 4 are directly connected to each other via the first connection path 6, while the first control unit 3 and the second control unit 4 are only indirectly connected via the second connection path 7, since the second connection path 7 is divided into two parts by another control unit. According to another embodiment, the second connection path 7 can also directly connect the first control unit 3 and the second control unit 4.
[0067] Generally speaking, this method is suitable for detecting synchronization errors.
[0068] As in Fig. 2 The method allows for the calculation and determination of the duration of the out-of-synchronization, specifically when the last correct synchronization occurred. Based on an existing synchronization, the procedure proposes determining the clock inaccuracy within the network, for example, that of "my" neighboring ECU or the "neighbor" CPU, even within the same ECU. Using this data, a timestamp from this component, in conjunction with "my" own clock or that of the Grandmaster and the synchronization interval, can be used to calculate how much time has elapsed since the last synchronization. This allows the determination of when the last successful synchronization took place. At a specific point in time, also called the determination time, a timestamp from an ECU of a control unit is recorded, the synchronization of which is to be determined.Based on a series of parameters, it is then determined how many synchronization intervals or since when this component has not been successfully synchronized, as exemplified in . Fig. 4 is visualized.
[0069] Thus, the procedure determines when the last successful synchronization of a node occurred and therefore also how long the node has been out of synchronization. This forms the basis for deciding whether the sensor data is trustworthy and therefore usable or not.
[0070] Fig. 4 This generally illustrates the synchronization of a message-based time synchronization. After synchronization messages arrive, the internal clock or offset is adjusted. The clock then continues to run with its own characteristics until the next synchronization.
[0071] As from Fig. 2 To obtain the necessary information, the process begins by querying the node, i.e., a microcontroller, switch, the entire ECU, or control unit 3, 4, 5, at its current time or by reading it using a timestamp. This value is stored. The process then determines the frequency drift of the timer using the 802.1AS protocol (Pdelay query). Using cyclic messages, which are actually used for time-of-flight measurement and are transmitted anyway, the system calculates the operating speed of the clock generator of this ECU / microcontroller, the entire ECU, or control unit 3, 4, 5.
[0072] For runtime measurement, the process is followed by the process from Fig. 3 The measurement process is used as follows: A port, the initiator, starts the measurement by sending a Delay_Request message to the connected port, the responder, and generating an output timestamp t1. This output timestamp is a hardware timestamp written as late as possible when leaving the Ethernet transceiver. Upon arrival of this packet, the responder generates a timestamp t2. In response, the responder sends a Delay_Response message. This message transmits the received timestamp t2 of the Delay_Request message. When this message leaves the responder, it generates a timestamp t3, which is sent in an immediately following Delay_Response_Follow-Up message. Upon receiving the Delay_Response message, the initiator generates a timestamp t4. The initiator can calculate the average running time of the distances traveled from the four timestamps t1 to t4.
[0073] PTP defines a master / slave clock hierarchy with a best clock within a network. The time base of all nodes in the network is derived from this clock, the Grandmaster. The Best Master Clock Algorithm (BMCA) determines this clock type and announces this information within the network. IEEE 802.1AS-compliant systems cyclically send announcement messages to their neighboring nodes containing information about the cloud's best clock. The recipient of such a message compares this information with the characteristics of its own clock and any messages already received from another port. Based on these messages, a time synchronization span tree is constructed. Each port is assigned one of four port states. The port with a shorter path to the Grandmaster than its link partner receives the Master Port state.The Slave state is assigned when no other port on that node already has this state. The Disabled state is selected by the port that cannot fully support the PTP protocol. The Passive state is selected when none of the other three states apply.
[0074] The exchange of time information is ultimately carried out by the Sync_Follow_Up mechanism. The master ports cyclically send Sync and Follow_Up messages to the adjacent link partner. When the Sync message leaves the master port, a timestamp is generated, which is immediately transmitted in a subsequent Follow_Up message. This timestamp corresponds to the current time of the grandmaster at the time the Sync message was sent. The messages originating from the grandmaster are not forwarded but are recreated at each node, including the switches.
[0075] As in Fig. 6a The PTP NRR (Neighbor Rate Ratio) method can be used to determine or calculate the clock speed. This involves using cyclic PDelay messages to calculate the clock speed (offset) relative to the reference clock. The read or queried time (Tverdächtig) is assigned to the current system time (TReference), which is the trusted time—either the Grandmaster or the time for which the data is relevant. If the component under investigation is a sensor, the sensor fusion time could be used as a reference. This means that the difference between the two times is first determined. TDeviation = TRarisation-Suspected
[0076] Using the synchronization frequency, the maximum permissible T deviation can first be calculated: In Ethernet, the interface between the PHY (transceiver) and the MAC is the primary interface for recording time information. This interface (xMII) is clocked at a nominal frequency f of 25 MHz. Crystals for Automotive Ethernet AVB / TSN-compatible implementations must not exceed a maximum inaccuracy fo of ±100 ppm. Thus, even the worst possible crystal, in conjunction with the interface, would cause a frequency deviation of 5 kHz from the nominal frequency f, according to the formula: df = f * fo / 10 ∧ 6
[0077] The change in the period between the maximum (2500 Hz) and minimum frequencies (2499 Hz) is 8 ps with a period of 40 ns. This means that two quartz crystals (and thus two ECUS) can have a maximum time difference of 8 ps between them at +25°C within 40 ns. Exactly 3,125,000 periods of 40 ns each are possible within the standard synchronization interval of 125 ms, which corresponds to a maximum deviation of 25 µs.
[0078] According to the IEEE 802.1AS specification, the synchronization interval can range from 31.25 ms to 32 seconds. The shortest interval corresponds to a worst-case deviation of 6.25 µs, while the longest interval results in a deviation of 6.4 ms.
[0079] Schematically, in Fig. 6b The procedure for calculating when the last synchronization took place is as follows: using the preceding formula, determining the speed of the clock generator and knowing the synchronization interval Tdeviation.
[0080] In the Fig. 1b The illustrated embodiment of the Ethernet network 2 comprises the first control unit 3, the second control unit 4, and the third control unit 5. Furthermore, the Ethernet network 2 also includes the first connection path 6, the second connection path 7, and the third connection path 8. According to the embodiment, a propagation delay 9 of a first signal 10 on the first connection path 6 is determined. The propagation delay 9 describes how long the first signal 10 travels along the first connection path 6 from the first control unit 3 to the second control unit 4 or vice versa. Based on the propagation delay 9 of the first signal 10, a maximum speed 11 of the first connection path 6 is determined. The maximum speed 11 of the first connection path 6 varies, for example, depending on the cable length, the transmission speed, and / or the type of media or transmission medium.Based on the maximum speed 11, a type of transmission medium 12 of the first connection path 6 is determined.
[0081] According to this embodiment, the type of transmission medium 12 is defined as optical, copper, or wireless. In the case of optical transmission, the first connection path 6 is, for example, designed as a fiber optic connection. In the case of copper transmission, the first connection path is, for example, formed by a cable with twisted pairs, such as an unshielded twisted pair cable (UTP). In the case of wireless transmission, the first connection path 6 is essentially designed as a radio link, and the first control unit 3 and / or the second control unit 4 have or are connected to a radio receiver and / or radio transmitter.
[0082] Control unit 3 determines a runtime for data transmission via the on-board network to control unit 4. It is important that the determination of the runtime is based in some way on an actual physical condition of the transmission path from the first control unit 3 to the control unit 4, i.e., that there is a physical condition or property of the transmission path, a change of which leads to a change in the determined runtime.
[0083] Here, one control unit 3 determines the latency for data transmission over the network to control unit 4. This can be done in various ways. For example, the latency can be determined through time synchronization between the first and second participants, such as according to the IEEE 802.1AS time synchronization standard and its PTP protocol. The "Delay Request" and "Peer Delay" messages implemented within this protocol can be used as data packets. However, the method is not limited to this. The crucial point is that the latency determination is based in some way on an actual physical characteristic of the transmission path from the first participant / control unit 3 to the second participant / control unit 4; that is, there must be a physical characteristic or property of the transmission path whose change leads to a change in the determined latency.
[0084] Furthermore, the first control unit 3 determines the message frequency, which is essentially derived from the speed of the PLL and quartz crystal, of the opposing control unit 4. From these two values, which constantly change due to temperature, aging, etc., the control unit 3 derives a key for encrypting these time messages.
[0085] The time synchronization messages are encrypted with the generated dynamic key, which can generally be derived from individual parameters of the connection partner.
[0086] As in Fig. 3 Additionally, based on the line delay 221 and the message frequency 213, an individual and constantly changing key is generated. This key is unique per unit of time and also differs per link. This approach ensures that no key is duplicated in the network. By generating the keys from the combination of point-to-point line delay and the frequency of the crystal, the key becomes particularly resistant to circumvention attempts, since the key is constantly changing and will be different on every link in the vehicle network.
[0087] The two values can either be used directly in combination or supplemented with other static values, such as the address, which both control units must know, in order to generate the keys. The respective control unit, whereby the procedure can be executed on both control units or participants / link partners, determines a random value from this to obtain the individual and only short-term valid key for encryption. The key changes continuously based on previous measurements, which do not require any additional effort, as these are used for time synchronization.
[0088] The type of transmission medium 12 is communicated to a program 13 in the Ethernet network 2. The program 13 can, for example, be located in the first control unit 3, the second control unit 4, the third control unit 5, or another control unit of the Ethernet network 2. Depending on the type of transmission medium 12, a connection path selection 14 is adjusted. For example, the program 13 can use the connection path selection 14 to send data via a different connection path than before the connection path selection. The program 13 can also, for example, interrupt the transmission of data using the connection path selection 14 and resume it at a later time.
[0089] According to the exemplary embodiment, a transmission reliability value 15 is assigned to the first connection path 6 based on the type of transmission medium 12. The transmission reliability value describes the probability of data loss transmitted via the connection path. The transmission reliability value 15 thus indicates how reliably the data can be transmitted via the first connection path. This information is fed to the entropy source 200. If, for example, a reliability threshold is undershot and the data can only be transmitted with insecurity, it can be expected that the data will reach its destination with a delay or, if retransmission is not worthwhile due to the required data timeliness, will not reach its destination at all.
[0090] According to a further embodiment, propagation times of a plurality of signals on the first connection path 6 are determined, and the fastest propagation time of the plurality of signals is selected. The maximum speed 11 of the first connection path 6 is then determined based on the fastest propagation time.
[0091] A control unit initiates the delay measurement and waits for the receipt of messages from the link partners. Based on the message reception, using PTP as an example, the line delay can be measured. When one link partner starts the delay measurement, the other link partner is automatically notified and should also start a measurement so that these two measurements can generate a corresponding measured value.
[0092] Analogous to the procedure described above, the type of transmission medium 12 can also be determined for the second connection path 7 and / or the third connection path 8.
[0093] The recorded values are different, remain secret, and are stored in the control unit. Furthermore, they are not transmitted over the network—nor do they need to be. Discovering the key simply by trial and error is highly improbable. An individual key is generated based on these two values. Firstly, the frequency of each crystal is different, and secondly, the line delay of each link is also different. Here, two fluctuating values are added together to produce a third value that is even more difficult to guess—the key value. The line delay typically ranges from 50 to 500 nanoseconds, and the frequency is a parameter specified in + / - ppm. The line delay in both directions is based on the same channel, which is why the calculated values are identical on both sides of the link. Therefore, the parameters do not need to be exchanged.Thus, both partners have virtually identical values for key generation at almost the same time. One link partner encrypts using these two values derived from the last measurement, and the other link partner decrypts using its latest values.
[0094] It is also provided that a propagation delay 16 of a second signal 17 on the second connection path 7 is determined. A maximum speed 18 of the second connection path 7 is then determined based on the propagation delay 16 of the second signal 17. Based on the maximum speed 18 of the second connection path 7, a type of transmission medium 19 of the second connection path 7 is then determined.
[0095] It is advantageous to use the current key A1 as long as no new line measurement is performed. This ensures the link partner always knows which key to use unless a new line measurement has been initiated beforehand. A new key can be generated either cyclically, e.g., at a predefined frequency, triggered as needed, or always immediately before sending important messages.
[0096] The first control unit 3, the second control unit 4, and the third control unit 5 can all be operated in normal mode or in energy-saving mode. In energy-saving mode, each control unit consumes less energy than in normal mode. For example, in energy-saving mode, the speed of a port on the respective control unit can be reduced compared to the speed in normal mode. This reduced port speed then also affects the maximum speed of the respective connection path.
[0097] According to a further embodiment, a service message 20 can be sent from the first control unit 3 to the third control unit 8. The service message 20 then triggers the determination of a propagation time 21 for a third signal 22. The third signal 22 is transmitted between the second control unit 4 and the third control unit 5. According to this embodiment, the propagation time 21 of the third signal 22 is determined by the third control unit 5.
[0098] Fig. 10 This generally describes the procedure for determining the propagation delay. In step S1, the propagation delay 9 of the first signal 10 is determined. In step S2, the type of transmission medium 12 is determined. In step S3, the program 13 is then adapted. In step S4, the propagation delay 9 of the first signal 10 is determined. This allows the type of transmission medium 12 to be determined in step S5. The type of transmission medium 12 can, in turn, include the following parameters: speed 23, medium 24, cable length 25, power transmission 26, bit error rate 27. In step S6, the program 13 is then adapted and the connection path 14 is selected.
[0099] This example suggests measuring the propagation time of signals between connected control units or controllers. Methods from standards IEEE 1588 or IEEE 802.1AS can be used to measure propagation times 9, 16, and 21. Methods for determining these propagation times can also be provided by TTEthernet (time-triggered Ethernet).
[0100] Fig. 12 Figures 9, 16, and 21 demonstrate how to determine the respective runtimes. Both local and non-local runtime queries are described. Program 13, which is executed on at least one control unit, preferably first determines the local runtime or, if more than one control unit is directly connected, the runtimes locally. Then, other control units are preferably queried for their runtimes relative to their neighbors using a service-oriented method, such as SOME / IP (Scalable Service-Oriented Middleware over IP). This can be implemented either centrally or decentrally. The query can be performed once, at system startup, upon definition, or after a software update, or it can be executed cyclically to detect dynamic changes. This data, including the addresses of the control units, is then stored and assigned the first time it is queried.In step S7, the respective runtime to the directly connected control units is determined. In step S8, the respective runtimes of other connection paths are queried. In step S9, the respective runtimes and their associated connection partners are stored.
[0101] Fig. 13 This section demonstrates another method for deriving other speeds based on a reference measurement. For example, if the current temperature is very high or poor-quality cables are used, pre-stored values may be too inaccurate. Therefore, it is proposed that the application or program 13 performs measurements on its own control unit, specifically taking into account its own parameters and other speeds, which can then be derived and calculated. In step S10, an analysis is performed for each local Ethernet port. In step S11, it is checked whether channel parameters are known. If not, step S12 follows, and the procedure ends. If so, step S13 follows, in which the respective runtimes 9, 16, and 21 are determined. In step S14, the data is stored, and the determined runtime is related to the channel parameters.In step S15, a reference value list is created.
[0102] Fig. 14 This demonstrates a possible optimization through knowledge of the transmission medium type 12, 19. In step S16, it is determined whether the transmission medium type 12, 19 is copper. If so, step S17 follows, confirming that PoDL (Power over Data Lines), i.e., power supply via Ethernet, is possible. If step S16 determines that the medium is not copper, step S18 follows. In step S18, it is checked whether the transmission medium type 12 is optical. If so, step S19 follows. In step S19, it is determined that this results in a lower bit error rate and therefore higher reliability of this connection path. In step S20, the option is given to deactivate the RX (receiving unit) or TX (transmitting unit) of the control unit 3, 4, 5 if this is not required.
[0103] If step S18 determines that the medium or type of transmission medium 12 is not optical, step S21 assumes that the respective connection path is configured as a direct MII (Media Independent Interface) connection. In this case, the respective control unit is suitable, for example, for IEEE 802.1 CB (Frame Replication and Elimination for Redundancy).
[0104] Further possibilities arise from knowledge of the transmission speed. Combined with the current data streams, data can, for example, be selectively transmitted via a high-bandwidth connection, thereby deactivating other, unnecessary connection paths and saving energy.
[0105] Furthermore, high-bandwidth connections offer the possibility of using redundancy mechanisms (e.g., IEEE 802.1 CB). Since the data is continuously transmitted redundantly, a high bandwidth is necessary. It is also conceivable to adapt the application depending on the speed of the transmission path. For example, a camera can adjust the resolution of the transmitted image data depending on the speed of the link or connection path 6, 7, 8.
[0106] The control unit 3, 4, 5 in Fig. 16 The network device comprises a microprocessor 402, volatile and non-volatile memory 404, 406, two communication interfaces 408, and a synchronizable timer 410. The elements of the network device are communicatively interconnected via one or more data connections or buses 412. The non-volatile memory 406 contains program instructions which, when executed by the microprocessor 402, implement at least one embodiment of the method according to the invention, and the entropy source is formed in the volatile and / or non-volatile memory 404, 406, from which the dynamic keys 28 for the communication paths 6 are then generated. Fig. 17 The decoding process of the dynamic key is specified during decryption.
[0107] In Fig. 15 This section describes how the usability of received data is evaluated based on its last successful synchronization time. This process determines whether the data being reviewed before storage is suitable for its intended use. This is particularly advantageous when the data is stored on a data recorder. For the data recorder, it is crucial that the data is accurate. In the event of an accident, for example, it is important to know whether the camera detected the pedestrian or not. If incorrect data or data with an incorrect time is recorded, the recording is invalid and cannot be recognized as such without this procedure.
[0108] The querying component analyzes a data stream and its sender, as in Fig. 22 This process is illustrated. Based on this method, it can be determined when the data was last trusted. The nominal thresholds are defined either by the functions, the system manufacturers, or the use case itself. This can vary per ECU and per use case. Based on these thresholds, the data can be classified as valid, invalid, or untrusted.
[0109] Fig. 18 and Fig. 19 Two use cases are shown where time synchronization is essential and the method is employed. Firstly, various data from different sensors / control units must be fused, which are contained in the sensor message based on the time information. Secondly, this data can also be saved to provide evidence in case of an error.
[0110] Fig. 20 This shows that both during data fusion and storage, timestamps in the data are used as a basis so that the correct data can be assigned chronologically.
[0111] Fig. 21 This shows the arrival of various sensor data frames at a fusion unit or, for example, at a data recorder. The recorder does not sort the data according to its arrival order, but rather according to its timestamp, which is based on a previous time synchronization. Since data in a network must travel different distances, it is typically sorted based on when the sensor data was generated and recorded.
[0112] In Fig. 21 It is shown that a timestamp is incorrect, meaning that an inconsistency occurred in the sensor data during fusion, resulting in faulty time synchronization, and that the proposed method was not used in this case. This method improves the precision and accuracy of clock synchronization for the real-time capability of the Ethernet onboard network. A key measure of the quality of a synchronization protocol is its achievable synchronization accuracy, which can be derived as additional information from the method.
[0113] Out of Fig. 22 The process is described in detail, including how data is retroactively deleted if the synchronization time is above the threshold. This procedure is also used, for example, when data is already stored (or about to be stored), as in the use case of a data recorder. For the data recorder, it is crucial whether the data is also factually correct – in the event of an accident, for example, it is important whether the camera recognized the pedestrian or not. If incorrect data is recorded, or data with an incorrect time, then the recording is invalid. The querying component analyzes a data stream and its sender as described in... Fig. 22The procedure determines when the data was last trusted. The nominal thresholds are defined either by the functions, the system manufacturers, or the specific use case itself. This can vary per ECU and per use case. Based on these thresholds, the data can be classified as valid, invalid, or untrusted.
[0114] The querying component can be a data recorder or cloud storage system that wants to check a stored data record from a component, such as a sensor data stream. This can involve checking, for example, the address, stream, and timestamp. A final check is performed to verify successful synchronization and determine the time when the data was last valid. The storage is then checked, and any incorrectly synchronized data records are discarded. List of reference symbols
[0115] 1. Motor vehicle 2. Ethernet on-board network 3. First control unit 4. Second control unit 5. Third control unit 6. First connection path 7. Second connection path 8. Third connection path 9. First signal transit time 10. First signal 11. Maximum speed of the first connection path 12. Type of transmission medium of the first connection path 13. Program 14. Connection path selection 15. Transmission security value 16. Second signal transit time 17. Second signal 18. Maximum speed of the second connection path 19. Type of transmission medium of the second connection path 20. Service message 21. Third signal transit time 22. Third signal 23. Speed 24. Medium 25. Cable length 26. Power transmission 27. Bit error rate 28. Dynamic key 29. Time synchronization message 200. Entropy source 211. Transmit at time t1 212. Receive at time t4 213Receive at time t4 221Receive at time t2 222Send at time t3 223Delayed send at time t3 300Encrypted message at time t5400 Control unit 402 Microprocessor 404 RAM 406 ROM 408 Communication interface 410 Timer 412 Bus / Communication interface 1001 Receiving an encrypted message 1002 Starting line delay and frequency measurement 1003 Requesting the last line measurement and frequency parameters 1004 Generating the key 1005 Decrypting the message
Claims
1. Method for checking the validity of sensor data of an Ethernet onboard network (2) in a motor vehicle (1), in which the following steps are carried out: d) determining a propagation time (9) of a first signal (10) on a first connecting path (6) between a first control unit (3) of the Ethernet onboard network (2) and a second control unit (4) of the Ethernet onboard network (2); e) determining a maximum speed (11) of the first connecting path (6) on the basis of the propagation time (9); and f) determining a type of a transmission medium (12) of the first connecting path (6) on the basis of the maximum speed (11), characterized in that the following steps are carried out: - identification of at least a first control unit (3) of the Ethernet onboard network (2); - synchronization of at least a first control unit (3) of the Ethernet onboard network (2); - ascertainment of the synchronization interval of the first control unit (3); - ascertainment of a drift of a timer (410) of the first control unit (3); - ascertainment of a timestamp of the first control unit (3); - reading a timestamp of the first control unit (3); - comparison of the timestamp of the first control unit (3) with a reference clock of the Ethernet onboard network (2); - performance of a propagation time measurement on the first control unit (3); - ascertainment of the speed of the associated clock generator; - ascertainment of the time difference of the synchronization interval; - ascertainment of the last synchronization, when the last successful synchronization of a node took place and for how long the control unit (3) of the node has not been synchronized again.
2. Method according to Claim 1, characterized in that the drift of the timer is ascertained by means of the protocol IEEE 802.1AS D8.3.
3. Method according to Claim 1 or 2, characterized in that the comparison of the timestamp with a reference clock of the Ethernet onboard network (3) results in a difference being calculated in the form Tdeviation = Treference - Tsuspect.
4. Method according to one of Claims 1 to 3, characterized in that the speed of the clock generator is ascertained by means of the PTP Neighbor Rate Ratio, NRR, method.
5. Method according to one of Claims 1 to 4, characterized in that the type of the transmission medium (12) and the - ascertainment of the synchronization interval - ascertainment of a drift of a timer (410) of the first control unit (3) - ascertainment of a timestamp of the first control unit (3) - ascertainment of the speed of the associated clock generator - ascertainment of the time difference of the synchronization interval - ascertainment of the last synchronization, when the last successful synchronization of a node took place and for how long the control unit (3) of the node has not been synchronized again are communicated to a program (13) in the Ethernet onboard network (2) and a connecting path selection (14) of the program (13) is adapted on the basis of the type of the transmission medium (12).
6. Method according to one of Claims 1 to 5, characterized in that the type of the transmission medium (12) is determined as optical, copper or wireless.
7. Method according to one of the preceding claims, characterized in that a transmission security value (15), which describes a probability of loss of data transmitted by way of the first connecting path (6), is assigned to the first connecting path (6) on the basis of the type of the transmission medium (12).
8. Method according to one of the preceding claims, characterized in that propagation times of a plurality of signals on the first connecting path (6) are determined and the fastest propagation time of the plurality of signals is selected, the maximum speed (11) of the first connecting path (6) being determined on the basis of the fastest propagation time.
9. Method according to one of the preceding claims, characterized in that a propagation time (16) of a second signal (17) on a second connecting path (7), which is different from the first connecting path (6), between the first control unit (3) and the second control unit (4) is determined, and a maximum speed (11) of the second connecting path (7) is determined, a type of the transmission medium (19) of the second connecting path (7) being determined on the basis of the maximum speed (11) of the second connecting path (7).
10. Method according to one of the preceding claims, characterized in that the method is carried out after the first control unit (3) changes from a normal operating mode to an energy-saving mode and / or from the energy-saving mode to the normal operating mode.
11. Method according to one of the preceding claims, characterized in that the propagation time (9) of the first signal (10) is determined using the first control unit (3) and a propagation time (21) of a third signal (22) on a third connecting path (8), which is connected to the first control unit (3) only indirectly, between the second control unit (4) and a third control unit (5) of the Ethernet onboard network (2) is determined using the third control unit (5), the determination of the propagation time (21) of the third signal (22) being triggered by a service message (20) sent from the first control unit (3) to the third control unit (5).
12. Control unit for an Ethernet onboard network (2), which, as first control unit (3), is designed: - to send a signal (10) to a second control unit (4) of the Ethernet onboard network (2) and to receive the signal (10) from the second control unit (4); - to determine a propagation time (9) of the signal (10) on a connecting path (6) to the second control unit (4); - to determine a maximum speed (11) of the connecting path (6) on the basis of the propagation time (9); and - to determine a type of a transmission medium (12) of the connecting path (6) on the basis of the maximum speed (11), and at least comprises - a microprocessor (402), - a volatile memory (404) and nonvolatile memory (406), - at least two communication interfaces (408), - a synchronizable timer 410, the nonvolatile memory (406) contains program instructions that are executed by the microprocessor (402), characterized in that at least one embodiment of the method according to Claims 1 to 10 can be implemented and carried out.
13. Ethernet onboard network (2) for a motor vehicle (1), having a first control unit (3) and a second control unit (4), wherein the control units (3, 4) are connected to one another by way of at least one connecting path (6, 7), and the first control unit (3) is designed according to Claim 11.
14. Ethernet onboard network according to Claim 11, characterized in that the Ethernet onboard network (2) has a third control unit (5), which is connected to the first control unit (3) only indirectly and is connected to the second control unit (4) directly by way of a third connecting path (8), wherein the third control unit (5) is designed to determine a propagation time (21) of a third signal (22) on the third connecting path (8), wherein the first control unit (3) is designed to trigger the determination of the propagation time (21) of the third signal (22) by way of a service message (20) to the third control unit (5).
15. Computer program product comprising commands that, when the program is executed by a computer, cause said computer to carry out the method (200) according to one or more of Claims 1-10.
16. Computer-readable medium on which the computer program product according to Claim 14 is stored.
17. Vehicle having an Ethernet onboard network comprising multiple control units (3, 4, 5) according to Claim 12.
