Device with high reliability in performing time stamp and method thereof

The processing apparatus and method enhance data timestamping reliability and integrity by using primary and secondary timers with error detection, ensuring accurate timestamp verification for improved data fusion in safety-sensitive applications.

JP2024163981APending Publication Date: 2024-11-26RENESAS ELECTRONICS CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024071794
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-02
Filing Date
2024-04-25
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

Existing data fusion systems in vehicles rely on unreliable and incomplete timestamping of sensor data, which affects the quality and integrity of data fusion, particularly in safety-sensitive applications like autonomous driving and aerospace.

Method used

A processing apparatus and method that uses primary and secondary timers to capture timestamps, generates proof data with error detection codes, and verifies timestamps through redundant capture and comparison to ensure data integrity and reliability, adhering to ASIL D standards.

Benefits of technology

Ensures reliable and accurate timestamping of sensor data, enhancing the integrity and reliability of data fusion for safety-critical applications by detecting and correcting timestamp errors, thereby improving the performance of autonomous systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024163981000001_ABST
    Figure 2024163981000001_ABST
Patent Text Reader

Abstract

To perform a time stamp of data such as sensor data with high-level reliability and / or integrity.SOLUTION: A processing device for processing a data frame including data captures a time stamp with the use of a primary timer when a trigger indicating the processing of the data frame is received. The processing device generates verification data based on the data frame and the time stamp, and stores the verification data in a memory module together with the data frame and the time stamp.SELECTED DRAWING: Figure 2a
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This document relates to an apparatus and method for performing time stamping of data, and more particularly to an apparatus and method for performing time stamping of data at a high level of integrity, such as Automotive Safety Integrity Level (ASIL) Level D. [Background technology]

[0002] A vehicle is equipped with various environmental sensors (cameras, radar sensors, Lidar sensors, etc.) configured to capture sensor data about the vehicle's environment. The sensor data from the various sensors can be fused to determine an environment model for the vehicle. This model may be used to provide advanced driver assistance systems (ADAS) and / or autonomous driving.

[0003] Typically, different sensors provide sensor data at different times. The quality, especially the reliability and / or completeness, of the data fusion typically depends on the reliability and / or completeness of the time synchronization of the sensor data of the different sensors. In particular, the quality of the data fusion typically depends on the reliability and / or completeness of the timestamps provided with the data frames of the different sensors.

[0004] This document is directed to the technical problem of performing time stamping of data, such as sensor data, with a high level of reliability and / or integrity. This document is directed to reliably distributing time within a communication network, such as a vehicular communication network, such that various electronic control units of the vehicle have the same time reference. It is noted that the methods and apparatus described herein are generally applicable to safety-critical applications, such as aerospace and / or medical applications. Summary of the Invention

[0005] According to one aspect, a processing device configured to process (e.g., in the context of receiving or transmitting) a data frame including data, such as sensor data, is described. Upon receiving a trigger indicating processing of the data frame, the processing device is further configured to capture a timestamp using a primary timer. Additionally, the processing device is configured to generate attestation data based on the data frame and the timestamp, and store the attestation data in conjunction with the data frame and the timestamp in a memory module.

[0006] According to a further aspect, a method is described for performing time stamping on data in a communications interface, particularly with one or more data frames. The method includes processing (e.g., in a receive or transmit context) a data frame including the data, and capturing a time stamp using a primary timer upon receiving a trigger indicating processing of the data frame. Additionally, the method includes generating attestation data based on the data frame and the time stamp, and storing the attestation data in conjunction with the data frame and the time stamp in a memory module.

[0007] According to a further aspect, a software program is described, which may be adapted to run on a processor and to perform the method steps outlined in this document when executed on the processor.

[0008] According to another aspect, a storage medium is described. The storage medium may include a software program adapted to be executed on a processor and, when executed on the processor, to perform the method steps outlined in this document.

[0009] It should be noted that the methods and systems, including the preferred embodiments outlined herein, can be used alone or in combination with other methods and systems disclosed herein. In addition, features outlined in the context of a system are also applicable to the corresponding method. Moreover, all aspects of the methods and systems outlined herein may be combined in any manner. In particular, features recited in the appended claims may be combined with each other in any manner. [Brief description of the drawings]

[0010] The invention will now be described, by way of example only, with reference to the accompanying drawings, in which: [Figure 1a] 1 shows an example of a communication system with a processing device including a communication interface with a transmitting unit and a receiving unit. [Figure 1b] 1 shows an example of a receiving unit. [Figure 1c] 1 shows an example of a transmission unit. [Figure 1d] 1 shows an example of a data package including a data frame. [Figure 2a] 1 shows an example of a receiving unit with a generator for verification data. [Figure 2b] 1 shows an example of a sending unit with a generator for verification data. [Diagram 3] 1 illustrates a flow chart of an example of a method for performing time stamping on data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] As mentioned above, this document is directed to increasing the reliability and / or integrity level of time-stamping data. In this context, Fig. 1a shows an example of a system 150 including a processing device 160. The processing device 160 may include a communication interface 161 with a transmitting unit 130 for transmitting data over a communication path 100, such as an Ethernet link, and a receiving unit 110 configured to receive data via the communication path 100. The processing device 160, more particularly the communication interface 161, may be integrated within a microcontroller unit (MCU) or within a system on chip (SoC). The processing device 160, more particularly the communication interface 161, may include one or more (hardware-based) timers, in particular a primary timer 163 and / or a secondary timer 164, as described below. The clocks used for the one or more timers 163, 164 may be the same. Alternatively, different timers 163, 164 may use different clocks. Additionally, the processing unit 160 may include memory modules 116, 136, which may be part of the communication interface 161. An electronic control unit (ECU) of a vehicle may include one or more processing units 160.

[0012] The processing unit 160 may further include a processor unit 162, for example with a central processing unit (CPU). The processor unit 162 may be configured to execute software to perform one or more of the functions described in this document.

[0013] It should be noted that the processing units 160 on either side of the communication path 100 may be implemented in different ways. In particular, aspects described herein may be implemented in only one of the processing units 160 or in both processing units 160.

[0014] 1b shows a block diagram of an example of a receiving unit 110. The receiving unit 110 includes (among other components and / or logic, such as shift registers and / or control and status logic) a frame state machine (FSM) 111 configured to identify individual data frames 122 of a data stream received over the communication path 100. The frame state machine 111 is configured to pass the individual data frames 122 to a storage module 113 (specifically a FIFO (First In First Out) module). Furthermore, the frame state machine 111 is configured to pass a start frame delimiter (SFD) 121 of the preamble of the individual frame 122 to the timestamp capture module 114. The SFD 121 of the data frame 122 may be considered to be a trigger indicating the fact that the data frame 122 has been received at the receiving unit 110. Thus, the frame state machine 111 may be considered to be a trigger module configured to generate a trigger 121 indicating receipt of the data frame 122.

[0015] Thus, the receiving unit 110 may include a trigger module 111 configured to identify a predefined trigger 121, i.e. a point or data entity, within the data frame for triggering the time stamp. In case of Ethernet, the trigger 121 may be an SFD. In case of different protocols, such as CAN (Controller Area Network) and / or PCIe (Peripheral Component Interconnect Express) and / or another protocol, the trigger 121 may be a different data entity.

[0016] The timestamp capture module 114 is configured to capture a timestamp 124 of the data frame 122 at the time the SFD 121 is received by the capture module 114. The timestamp 124 may be determined using a primary time 123 time value provided by a primary timer 163, which may utilize a clock synchronized using, for example, gPTP (generalized Precision Time Protocol). The timestamp 124 is provided to the storage module 113 along with the corresponding data frame 122.

[0017] The receiving unit 110 may further include a classification module 112 configured to assign a DMA (Direct Memory Access) channel number 125 to the metadata of each data frame 122 (based on the data contained within the data frame 122). The DMA channel number 125 of a data frame 122 may be stored together with the corresponding data frame 122 in the storage module 113. The data frame 122 may include metadata regarding the actual payload of the frame received over the communication path 100.

[0018] Thus, each data frame 122 containing data (such as sensor data from a sensor) may be stored along with a channel number 125 (as part of the metadata of the frame 122) and along with a timestamp 124 (indicating when the frame 122 was received at the receiving unit 110). This extended frame data 126 may be stored in a memory module 116 (e.g., random access memory (RAM)) using a DMA controller 115 via an interface bus (e.g., AXI) 127. The storage location within the memory module 116 may depend on the channel number 125. The extended frame data 126 may include the channel number 125, the data frame 122, the timestamp 124, and / or the verification data 211.

[0019] In case of an erroneous operation of the receiving unit 110, it may happen that the timestamp 124 of the data frame 122 is altered and / or the data frame 122 is associated with an incorrect timestamp 124. Fig. 2a shows the receiving unit 110 including a generator 210 for generating verification data 211 based on the data of the data frame 122 and the timestamp 124. The verification data 211 may include or be an error detection code, such as a CRC (Cyclic Redundancy Check). It is calculated over the data of the frame 122 and the data of the timestamp 124 using a predefined data generation method. The verification data 211 may be stored together with the frame 122 to provide an extended frame data 126 that also includes the verification data 211.

[0020] The verification data 211 may be used to detect erroneous situations where the timestamp 124 of the data frame 122 has once been altered and / or is incorrect. For this purpose, the verification data 211 may be compared with the timestamp 124 stored (in the memory module 116) together with the data frame 122. In particular, the verification data may be generated based on the data of the data frame 122 and based on the timestamp 124 stored together with the data frame 122 (using the data generation method described above). The verification data may include or may be an error detection code, in particular a CRC. If the verification data 211 differs from the verification data, the frame 122 may be discarded and a hardware failure may be reported. Otherwise, the frame and timestamp processing may continue. The comparison of the verification data 211 with the verification data may be performed in software on the CPU (Central Processing Unit) 162 or using dedicated hardware.

[0021] The frame 122 from which the timestamp 124 is captured and from which the verification data 211 is generated may be a frame for clock synchronization. The data of the frame 122 may indicate a clock value. The clock value contained within the frame 122 may be used in conjunction with the timestamp 124 (of the local primary time 123 at the receiving unit 110, provided by the primary timer 163) to provide accurate clocking and / or synchronization (e.g., using gPTP). The primary timer 163 may be synchronized using the gPTP protocol.

[0022] Another cause of an incorrect timestamp may be an error in the timestamp capture module 114 and / or the trigger module 111. For example, the timestamp capture module 114 may not update the timestamp 124, but may leave it at a constant value. For that purpose, a redundant capture module 220 may be provided. The redundant capture module 220 is configured to capture a redundant timestamp 224 at the time of the SFD 121 using a redundant and / or secondary timer 164 providing a secondary time 223.

[0023] The redundant timestamp 224 may be compared to the primary timestamp 124. If the redundant timestamp 224 and the primary timestamp 124 do not match and / or correspond (e.g., because the primary timestamp 124 remains constant), a fault is detected. The redundant timestamp 224 and the primary timestamp 124 may be compared using software, in particular using software running on the processor unit 162. Alternatively, the redundant timestamp 224 and the primary timestamp 124 may be compared using dedicated hardware.

[0024] It should be noted that the redundant timestamp 224 and the primary timestamp 124 may be different from each other. On the other hand, the redundant timestamp 224 and the primary timestamp 124 may have a predetermined relationship to each other (e.g., a predetermined ratio and / or a predetermined offset). When determining whether the redundant timestamp 224 and the primary timestamp 124 match and / or correspond, the predetermined relationship between both timestamps 124, 224 may be taken into account (by software). If the redundant timestamp 224 and the primary timestamp 124 exhibit a predetermined relationship, it may be determined that the redundant timestamp 224 and the primary timestamp 124 match and / or correspond. On the other hand, if the redundant timestamp 224 and the primary timestamp 124 do not exhibit a predetermined relationship, it may be determined that the redundant timestamp 224 and the primary timestamp 124 do not match and / or correspond.

[0025] Upon receiving a new frame 122, an "Rx Occurred" flag may be set. Such a flag may be set by the hardware DMA controller 115 or by software running on, for example, the processor unit 162. Furthermore, the flag may be cleared by software (running on, for example, the processor unit 162). As an example, the software running on the processor unit 162 may read the timestamps 124, 224 from the register module 221. The "Rx Occurred" flag may be checked to verify whether the timestamps 124, 224 should be updated. If the "Rx Occurred" flag is set, the redundant timestamp 224 may be compared to the primary timestamp 124 (as outlined above). On the other hand, if the "Rx Occurred" flag is not set, the comparison of the redundant timestamp 224 to the primary timestamp 124 may be omitted.

[0026] For a new frame 122 having a timestamp 124 (possibly only frames used for clock and / or time synchronization), a CRC may be calculated over the data of the frame 122 and the associated timestamp 124, which are stored in the memory module 116 (e.g., using software running on the processor unit 162). This CRC may be referred to as verification data. The calculated CRC (i.e., verification data) may be compared with stored attestation data 211 (in RAM 116). If the verification data and the stored attestation data 211 do not match, the frame 122 may be discarded and a hardware failure may be reported. Otherwise, frame and timestamp processing may continue.

[0027] It should be noted that the proof data 211 is typically determined using hardware (i.e., generator 210), whereas the verification data is typically determined using software (running on processor unit 162).

[0028] The captured timestamp 124 and the redundant timestamp 224 may be provided repeatedly (e.g., every 100 milliseconds) to the register module 221. The register module 221 may include a register for each timestamp 124, 224. The value (i.e., timestamp) 124, 224 of each time 123, 223 (provided by the respective timer 163, 164) may be written into the respective register of the register module 221. Thus, the register module 221 provides a consistent snapshot of the contents of the capture modules 114, 220 (each of which may be implemented as a register).

[0029] Software (e.g., in the processor unit 162) may access the registers of the register module 221 (repeatedly, e.g., every 100 milliseconds) to compare the captured timestamp 124 with the redundant timestamp 224. It may check whether both timestamps 124, 224 are consistent and / or correspond, and any unexpected differences may indicate a hardware failure.

[0030] If the "Rx occurred" flag is set (or, more generally, if a reception occurred within the observation interval), one may check whether the timestamp 124 has advanced. This allows detection of timer failures and / or problems with SFD generation within the trigger module 111.

[0031] After processing, the "Rx occurred" flag may be cleared.

[0032] 1c shows an example of a transmitting unit 130 including modules similar to those of the receiving unit 110. It should be noted that the features described in the context of the receiving unit 110 are also (correspondingly) valid for the transmitting unit 130.

[0033] The processing unit 160 may include a memory module 136 (e.g., RAM) for storing data that can be passed to the DMA controller 135 via the interface bus 147. The memory module 136 may be part of the communication interface 161, and in particular of its transmission unit 130. In this case, the DMA controller 135 may be omitted. The individual frames 146 may be stored in the storage module 133 (e.g., a FIFO module). The metadata of the extended frame 146 (including the data frame 142) may be analyzed using the timestamp control module 134, which is configured to determine (based on the metadata of the extended frame 146) whether the timestamp 124 should be stored together with the frame 146 in the memory module 136 (where the frame 146 is already stored in the memory module 136).

[0034] The sending unit 130 includes a timestamp capture module 114 configured to capture a timestamp 124 in each SFD 121 of the frame 142 based on a timer value 123 of a primary timer 163 (which may be synchronized using gPTP). The timestamp 124 may be stored in the memory module 136 together with the frame 146.

[0035] As already outlined in the context of the receiving unit 110 and shown in Fig. 2b, the receiving unit 110 may include a generator 210 configured to generate verification data 211, as shown in Fig. 2b, of the sending unit 130. Additionally, the receiving unit 110 may include a redundant capture module 220 and a register module 221.

[0036] For every individual transmit (Tx) event (when DMA controller 135 fetches a new frame 146 from RAM 136), a flag "Tx occurred" may be set (by hardware or software when providing frame 146 for fetching). Such a flag may be set by DMA controller 135 in hardware or cleared by software (e.g., software in processor unit 162).

[0037] For transmission events with a timestamp (which may only apply to clock and / or time-synchronized frames), a CRC may be calculated over the Tx data frame 142 and the Tx timestamp 124 stored in the memory module 136 (e.g., using software running on the processor unit 162). This CRC may be referred to as verification data. Furthermore, the calculated CRC (i.e., verification data) may be compared with the stored verification data 211 (in the memory module 136). If they differ, a signal transmission problem may be detected and a hardware failure may be reported. Otherwise, TS processing may continue.

[0038] The timestamp 124 and the redundant timestamp 224 may be provided to a register module 221. Software in the processor unit 162 may check whether both match. The register module 221 may comprise or consist of ("special function") registers for storing the values ​​of the timestamps 124, 224. Software (in the processor unit 162) may access the registers of the register module 221 and perform a software-based comparison of the timestamps 124, 224. An unexpected difference (deviation from a predetermined relationship between the timestamps 124, 224) indicates a hardware failure.

[0039] If the "Tx occurred" flag is set (or, more generally, if a transmit event occurs), it may be checked whether the timestamp 124 has advanced, thereby allowing detection of stalled timer failures and / or SFD generation problems.

[0040] The "Tx occurred" flag may then be cleared.

[0041] 1d shows an example of a data package 170 that may be received by the receiving unit 110 (particularly the module 111) via the communication path 100 and / or transmitted by the transmitting unit 130 (particularly the module 131) via the communication path 100. The data package 170 includes a data frame 122, 142. In addition, the data package 170 typically includes additional data 171 (having one or more data fields). In the case of Ethernet, the data package 170, the additional data 171 may include a preamble, an SFD, a frame check sequence (FCS), and / or an interframe gap (IFG). The verification data 211 may be determined based only on the data frame 122, 142 (excluding the additional data 171). The trigger 121 may be included in the additional data 171 (e.g., as in the case of Ethernet) or in the data frame 122, 142 (as in the case of CAN).

[0042] 3 shows a flow chart of one example (possibly computer-implemented) of a method 300 for performing time stamping on data in a communication interface 161, in particular the receiving unit 110 and / or the transmitting unit 130. The method 300 is directed to providing reliable time synchronization across different communication interfaces in a communication network. The data may include sensor data provided by one or more sensors, e.g. vehicle sensors. The steps of the method may be performed by software and / or hardware.

[0043] The method 300 may include processing 301 a data frame 122 , 142 including data, which may include receiving the data frame 122 or transmitting the data frame 142 .

[0044] Additionally, the method 300 includes capturing 302 a timestamp 124 using a primary timer (wherein the primary timer 163 provides the primary time 123) upon receiving a trigger 121 (in particular a start frame delimiter (SFD)) indicating processing 301 of the data frame 122, 142. The timestamp 124 may be captured using a (hardware-based) capture module 114, where the capture module 114 may be configured to capture a time 134 indicated by the primary timer 163 in response to receiving the trigger 121.

[0045] Additionally, the method 300 includes a step 303 of generating verification data 211 based on the data frames 122, 142 and the timestamp 124. The verification data 211 may include an error detection code generated using a predetermined data generation method.

[0046] The method 300 further includes a step 304 of storing the attestation data 211 together with the data frames 122, 142 and the timestamp 124 in a memory module 116, 136 (e.g., RAM), which may be accessible by application software (utilizing the receiving unit 110 and / or the transmitting unit 130 to exchange data frames 122, 142 with one or more other entities). As an example, the application software may be configured to fuse sensor data provided by multiple different (vehicle) sensors. The application software may be executed on a processor unit 162 of a processing device 160, which may comprise the receiving unit 110 and / or the transmitting unit 130.

[0047] It should be noted that when receiving data, the attestation data 211, the data frame 122, and the timestamp 124 may be stored together and / or actively in the memory module 116. On the other hand, when transmitting data, the data frame 142 is typically already stored in the memory module 136 (prior to generating the timestamp 124 and / or the attestation data 211). In this case, the data frame 142 may be fetched from the memory module 136 to generate the attestation data 211. Thereafter, the attestation data 211 and / or the timestamp 124 may be stored in the memory module 136 (together and / or linked with the already stored data frame 142).

[0048] The attestation data 211 may be used to verify whether the timestamp 124 (stored in the memory module 116, 136 together with the data frame 122, 142) has been previously modified and / or is currently incorrect. Thus, the method 300 may include attesting the timestamp 124 based on the attestation data 211. As a result, reliable time stamping of the data is achieved (particularly according to an integrity level of ASIL D).

[0049] Thus, a processing device 160 configured to provide reliable time stamping of data (at a given ASIL level) is described. The processing device 110 may be a receiving unit and / or may be configured to receive one or more data frames 122. Alternatively or in addition, the processing device 130 may be a transmitting unit and / or may be configured to transmit one or more data frames 142.

[0050] The processing unit 160 is configured to process data frames 122, 142 containing data. The processing may include receiving the data frames 122 over the data communication path 100. Alternatively, or in addition, the processing may include transmitting the data frames 142 over the data communication path 100. The data frames 122, 142 may be Ethernet frames or CAN frames. The data communication path 100 may be an Ethernet link or a CAN bus. The CAN communication may conform to CAN 2.0, CAN-FD, and / or CAN-XL.

[0051] Additionally, the processing device 160 may be configured to capture the timestamp 124 using the primary timer 163 upon receiving the trigger 121 indicating processing of the data frame 122, 142. The processing device 160 may supplement the timestamp 124 with the primary time 123 provided by the primary timer 163. The primary time 123 may be provided by the primary timer 163 of the processing device 160. The primary timer 163 may be synchronized with one or more other processing devices 160 in the communication network including the data communication path 100 using a synchronization method (e.g., Generalized Precision Time Protocol (gPTP)). An offset and / or rate of the primary timer 163 may be determined using the synchronization method.

[0052] The trigger 121 may be a start frame delimiter (SFD) of an Ethernet package 170. The timestamp 124 may be captured using the hardware-based capture module 114.

[0053] The processing unit 160 may further be configured to generate (using a (predetermined) data generation method) verification data 211 based on the data frames 122, 142 and the timestamps 124. The verification data 211 may be such that it allows verification whether the timestamps 124 stored together with the data frames 122, 142 have been altered with respect to the captured timestamps 124 upon receipt of the trigger 121. The verification data 211 may include an error detection code, in particular a Cyclic Redundancy Check (CRC), determined based on the data of the data frames 122, 142 and the timestamps 124.

[0054] The attestation data 211 may be stored in the memory modules 116, 136 together with the data frames 122, 142 and the timestamps 124. As an example, the attestation data 211, the data frames 122, 142 and the timestamps 124 may be stored in the memory modules 116, 136 using a direct memory access (DMA) controller 115, 135. Alternatively, the attestation data 211, the data frames 122, 142 and the timestamps 124 may be stored in the local memory modules 116, 136 (without using the DMA controller 115, 135), for example, as in a CAN network. The memory modules 116, 136 may be random access memory (RAM), for example, local RAM. Application software (e.g., running on the processor unit 162 of the processing device 160) may access the memory modules 116, 136 to utilize the data frames 122, 142 and the timestamps 124. Additionally, application software may utilize the attestation data 211 to verify the accuracy of the timestamp 124. This results in a trustworthy scheme for time-stamping data.

[0055] The memory modules 116, 136 may be part of the communication interface 161 of the processing device 160, which comprises the transmitting unit 130 and / or the receiving unit 110. The receiving unit 110 and / or the transmitting unit 130 may comprise the memory modules 116, 136, respectively. In this case, the DMA controllers 115, 135 may be omitted. Alternatively or additionally, the processing device 160 may include one or more of the memory modules 116, 136 arranged outside the communication interface 161 (e.g., as part of the processor unit 162). In this case, the communication interface 161, in particular the transmitting unit 130 and / or the receiving unit 110, may include the DMA controllers 115, 135.

[0056] The processing device 160 (particularly using software on the processor unit 162 of the processing device 160) may be configured to verify, based on the verification data 211, whether the timestamp 124 stored together with the data frames 122, 142 in the memory modules 116, 136 has been previously modified or is currently correct. To this end, the processing device 160 (particularly using software on the processor unit 162) may generate the verification data based on the data frames 122, 142 and the timestamp 124 stored in the memory modules 116, 136. The verification data may be generated using the same data generation method (particularly the same method for generating error detection codes) as was used to generate the verification data 211.

[0057] The verification data may be compared to verification data 211 stored in memory modules 116, 136 along with data frames 122, 142. It may then be determined whether the timestamp 124 stored in memory modules 116, 136 along with data frames 122, 142 has been previously altered and / or is currently incorrect based on the comparison of the verification data and verification data 211. If the verification data and verification data 211 are identical and / or match, it may be concluded that the timestamp 124 was not previously altered and / or is currently correct. Otherwise, it may be concluded that the timestamp 124 has been previously altered and / or is currently incorrect.

[0058] The processing unit 160 may be configured to report a fault if it is determined that the timestamp 124 stored in conjunction with the data frame 122, 142 in the memory module 116, 136 has been previously altered and / or is currently incorrect. Alternatively, or in addition, the processing unit 160 may be configured to discard the data frame 111, 131 from the memory module 116, 136 if it is determined that the timestamp 124 stored in conjunction with the data frame 122, 142 in the memory module 116, 136 has been previously altered and / or is currently incorrect.

[0059] This may result in increased reliability of application software that utilizes the time-stamped data frames 122, 142.

[0060] The processing unit 160 may be configured to determine whether the data frame 122, 142 includes data used for clock and / or time synchronization (e.g., to synchronize a clock used to provide the primary time 123). Verification that the timestamp 124 stored in conjunction with the data frame 122, 142 in the memory module 116, 136 has previously been modified and / or is currently incorrect may be performed if and only if the data frame 122, 142 is determined to be a frame used for clock and / or time synchronization.

[0061] In other words, the verification of the time stamping may be performed only for a portion of the data frames 122, 142 processed by the processing unit 160, thereby providing an improved compromise between reliability and computational efficiency. It is ensured that all data frames 122, 142 related to the clock and / or time synchronization (especially gPTP frames) are verified, thereby providing a high integrity (especially ASIL) level regarding the clock and / or time synchronization in an efficient manner.

[0062] Upon receiving the trigger 121 indicating processing of the data frame 122, 142, the processing unit 160 may be configured to capture a redundant timestamp 224 using a secondary timer 164 (e.g., a software-based or hardware-based timer). The secondary timer 164 may be configured to provide a secondary time 223. The timestamp 124 may be compared to the redundant timestamp 224. Furthermore, based on the comparison, it may be verified whether the capture module 114 for capturing the timestamp 124 is defective and / or whether the trigger module 111, 131 for generating the trigger 121 is defective. This may result in further improving the reliability of the timestamp.

[0063] The processing device 160, in particular the software running on the processor unit 162, may be configured to determine the time interval and / or the data frames 122, 142, for which it is finally verified whether the capture module 114 for capturing the data frames 124 is defective and / or whether the trigger module 111, 131 for generating the trigger 121 is defective. A redundant timestamp 224 may be captured (to verify the capture module 114 and / or the trigger module 131) and / or the timestamp 124 may be compared with the redundant timestamp 224, in particular only if the time interval is equal to or greater than a predefined verification time (e.g., milliseconds) and / or if the number of data frames 122, 124 is equal to or greater than a predefined verification number (e.g., 10). By doing this, an improved compromise between reliability and computational efficiency may be provided.

[0064] The processing unit 160 may be configured to set a flag indicating a new data frame 122, 142 upon processing the data frame 122, 142. Furthermore, the processing unit 160 may be configured to clear the flag after verifying whether the capture module 114 for capturing the timestamp 124 and / or the trigger module 111, 131 for generating the trigger are defective. By doing this, the reliability of the described verification scheme may be further improved (by avoiding false positives).

[0065] The components of the processing unit 160 shown in Figure 2a (for the receiving unit 110) and / or Figure 2b (for the transmitting unit 130) may be implemented solely in hardware (wherein the memory modules 116, 136 may be implemented separately, e.g., as memory in the processor unit 162). Thus, the tasks performed by the illustrated components, one or more of the capture modules 114, 220, the register module 221, and / or the generator 210 may be performed solely in hardware. The attestation data 211 may be generated using a hardware-based (CRC) generator 210.

[0066] On the other hand, Calculation of validation data Comparison of the verification data with the validation data, and / or Comparing timestamps 124 and 224 Other tasks, such as may be performed using software running on the processor unit 162 of the processing device 160.

[0067] It should be noted that the processing unit 160 may comprise one or more communication interfaces 161 configured as described herein (to generate verification data 211 for verification of the timestamp 124). Furthermore, the processing unit 160 may comprise one or more communication interfaces that do not include the timestamp verification scheme described herein (and designed as described in the context of Figures 1b and 1c). Furthermore, it should be noted that the processing unit 160 and / or the communication interface 161 of the processing unit 160 may be configured to provide verification data 211 for verification of the timestamp 124 for only a subset of the data frames 122, 142.

[0068] It should be noted that this description and drawings merely illustrate the principles of the proposed method and system. Those skilled in the art will be able to implement various configurations that embody the principles of the present invention and fall within its spirit and scope, although not explicitly described or shown herein. Furthermore, all examples and embodiments outlined in this document are expressly intended for illustrative purposes only, primarily to help the reader understand the principles of the proposed method and system. Moreover, all statements herein providing principles, aspects, and embodiments of the present invention, as well as specific examples thereof, are intended to encompass equivalents thereof.

Claims

1. A processing device comprising: Process the dataframe containing the data, capturing a timestamp using a primary timer upon receiving a trigger indicating processing of said data frame; generating attestation data based on said data frames and said timestamps; configured to store the attestation data together with the data frame and the timestamp in a memory module; Processing unit.

2. 2. The processing apparatus according to claim 1, the verification data allows verification of whether the timestamp stored together with the data frame has been altered with respect to the timestamp captured when the trigger was received. Processing unit.

3. 3. The processing apparatus according to claim 1, the verification data includes an error detection code, in particular a cyclic redundancy check, determined on the basis of the data of the data frame and the time stamp, Processing unit.

4. The processing apparatus according to any one of claims 1 to 3, The processing device, in particular the software applications running on the processor unit of the processing device, verifying, based on the verification data, that the timestamp stored in the memory module together with the data frame has not been previously altered and / or is currently incorrect; configured to report a fault if it is determined that the timestamp stored in the memory module together with the data frame has previously been altered and / or is currently incorrect. Processing unit.

5. 5. The processing apparatus according to claim 4, said processing device, in particular a software application running on a processor unit of said processing device, is configured to discard said data frame from said memory module if it is determined that said timestamp stored together with said data frame in said memory module has previously been modified and / or is currently incorrect, Processing unit.

6. 6. The processing apparatus according to claim 4, said processing device, in particular a software application running on a processor unit of said processing device, is configured to generate verification data based on said data frames and said timestamps stored in said memory module, said verification data being generated using the same data generation method as used to generate said verification data, The processing device, in particular the software applications running on the processor unit of the processing device, comparing said verification data with said verification data stored in said memory module together with said data frame; and determining, based on a comparison of the verification data and the verification data, whether the timestamp stored in the memory module together with the data frame has been previously altered and / or is currently incorrect. Processing unit.

7. The processing apparatus according to any one of claims 4 to 6, The processing device, in particular the software applications running on the processor unit of the processing device, determining whether the data frame includes data used for clock and / or time synchronization; configured to verify, if and only if it is determined that the data frame is a frame used for the clock and / or time synchronization, that the timestamp stored together with the data frame in the memory module has not been previously modified and / or is currently incorrect, Processing unit.

8. The processing apparatus according to any one of claims 1 to 7, capturing a redundant timestamp using a secondary timer upon receiving the trigger indicating processing of the data frame; Comparing the timestamp to the redundant timestamp; configured to verify whether a capture module that captures the timestamp and / or a trigger module that generates the trigger are defective based on a comparison of the timestamp and the redundant timestamp; Processing unit.

9. 9. The processing apparatus according to claim 8, determining the time interval and / or the number of data frames since last verifying whether the capture module capturing the timestamp and / or the trigger module generating the trigger is faulty; configured to compare the timestamp with the redundant timestamp if and only if the time interval is equal to or greater than a predefined verification time and / or if the number of data frames is equal to or greater than a predefined verification number, Processing unit.

10. The processing apparatus according to any one of claims 1 to 9, the processing device is configured to receive the data frame; the process includes receiving the data frame over a data communication path; Processing unit.

11. The processing apparatus according to any one of claims 1 to 10, The processing device is configured to transmit the data frame; the process includes transmitting the data frame over a data communication path. Processing unit.

12. The processing apparatus according to any one of claims 1 to 11, the data frame is an Ethernet frame, a CAN frame, or a PCIe frame; and / or The memory module is a random access memory. Processing unit.

13. The processing apparatus according to any one of claims 1 to 12, The time stamp is captured using a hardware-based capture module; and / or the attestation data and the time stamp are stored in the memory module using a direct memory access controller; Processing unit.

14. 1. A method for performing time stamping of data in a communications interface, comprising: Process the dataframe containing the data, capturing a timestamp using a primary timer upon receiving a trigger indicating processing of said data frame; generating attestation data based on said data frames and said timestamps; storing said verification data in a memory module together with said data frame and said time stamp; method.