Processing device and method for executing timestamps
By using the main timer to capture and redundant timer in the processing device to verify the timestamp of sensor data, the sensor data timestamp reliability and integrity problems are solved, and data transmission with high integrity levels is achieved, and data fusion is enhanced. Reliability and security.
Patent Information
- Application Number
- CN202410514380.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-02
- Filing Date
- 2024-04-26
- Publication Date
- 2024-11-05
AI Technical Summary
In the prior art, the reliability and integrity of the timestamp of sensor data in the communication network is difficult to ensure, which affects the quality of data fusion, especially in safety-critical applications with high integrity levels.
By using the main timer in the processing device to capture the timestamp and generate verification data based on the data frame and timestamp, it is stored in the memory module to ensure the reliability and integrity of the timestamp, and use redundant timers to perform redundancy of timestamps Remain capture and compare, detect and report timestamp failures.
Improves the time stamp reliability and integrity of sensor data, ensures data transmission at high integrity levels (such as ASIL D), and enhances the reliability and security of data fusion.
Smart Images

Figure CN118900155A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] The disclosure of German patent application No. 102023204032.8 filed on May 2, 2023 (including description, drawings and abstract) is incorporated herein by reference in its entirety. Technical Field
[0003] The present document relates to a device and a method for performing timestamping of data at a high integrity level such as ASIL (Automotive Safety Integrity Level) D. Background Art
[0004] The vehicle includes different environmental sensors (such as cameras, radar sensors, lidar sensors, etc.) configured to capture sensor data about the vehicle environment. The sensor data of the different sensors can be fused to determine a model of the vehicle environment. The model can be used to provide advanced driver assistance systems (ADAS) and / or autonomous driving.
[0005] Different sensors usually provide sensor data at different times. The quality, in particular the reliability and / or integrity of data fusion usually depends on the reliability and / or integrity of the time synchronization of the sensor data of the different sensors. The quality of data fusion usually depends on the reliability and / or integrity of the timestamps provided with the data frames of the different sensors.
[0006] The present document aims at the technical problem of performing timestamping of data, such as sensor data, with a high level of reliability and / or integrity. The present document aims at distributing time within a communication network (e.g., of a vehicle) in a reliable manner so that different electronic control units of the vehicle have the same time basis. It should be noted that the methods and devices described in this document are generally applicable to safety-critical applications (such as aerospace applications and / or medical applications, etc.). Summary of the invention
[0007] According to one aspect, a processing device is described that is configured to process (e.g., in the case of receiving or transmitting) a data frame, the processing frame including data such as sensor data. The processing device is also configured to capture a timestamp using a master timer upon receiving a trigger indicating processing of the data frame. In addition, the processing device is configured to generate verification data based on the data frame and the timestamp, and store the verification data together with the data frame and the timestamp in a memory module.
[0008] According to another aspect, a method for timestamping data with one or more data frames at a communication interface is described. The method includes processing (e.g., in the case of receiving or transmitting) a data frame including data, and upon receiving a trigger indicating the processing of the data frame, capturing a timestamp using a master timer. In addition, the method includes generating verification data based on the data frame and the timestamp, and storing the verification data together with the data frame and the timestamp in a memory module.
[0009] According to another aspect, a software program is described. The software program may be adapted to be executed on a processor and, when executed on the processor, to perform the method steps outlined in the present disclosure.
[0010] 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, for performing the method steps outlined in the present disclosure.
[0011] It should be noted that the methods and systems including the embodiments outlined in this document may be used alone or in combination with other methods and systems disclosed in this document. Furthermore, features outlined in the context of a system also apply to the corresponding method. Furthermore, all aspects of the methods and systems outlined in this document may be combined in any manner. Features of the claims may be combined with each other in any manner. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1A An example of a communication system with a processing device comprising a communication interface with a sending unit and a receiving unit is shown.
[0013] Figure 1B An example of a receiving unit is shown.
[0014] Figure 1C An example of a transmission unit is shown.
[0015] Figure 1D An example of a data packet including a data frame is shown.
[0016] Figure 2A An example of a receiving unit with a generator for verification data is shown.
[0017] Figure 2B An example of a sending unit with a verification data generator is shown.
[0018] Figure 3 A flow chart illustrating an example of a method of time stamping data. DETAILED DESCRIPTION
[0019] As mentioned above, the present disclosure is intended to improve the reliability and / or integrity level of timestamp data. In this case, Figure 1A An example of a communication system 150 including a processing device 160 is shown. The processing device 160 may include a communication interface 161 having a sending unit 130 for sending data via a communication path 100 (such as an Ethernet link) and a receiving unit 110 configured to receive data via the communication path 100. The communication interface 161 in the processing device 160 may be integrated within a microcontroller unit (MCU) or within a system on a chip (SoC). The communication interface 161 may include one or more (hardware-based) timers, in particular a main timer 163 and / or an auxiliary timer 164, as described below. The clock for one or more timers 163, 164 may be the same. Alternatively, different timers 163, 164 may use different clocks. In addition, the processing device 160 may include a memory module 116, 136, wherein the memory module 116, 136 may be part of the communication interface 161. An electronic control unit (ECU) of a vehicle may include one or more processing devices 160.
[0020] The processing device 160 may also include a processor unit 162, for example having a central processing unit (CPU). The processor unit 162 may be configured to execute software for performing one or more of the functions described in this disclosure.
[0021] It should be noted that the processing devices 160 on both sides of the communication path 100 may be implemented in different ways. Various aspects described in this disclosure may be implemented in only one processing device 160 , or in both processing devices 160 .
[0022] Figure 1B A block diagram of an example of a receiving unit 110 is shown. The receiving unit 110 comprises a frame state machine (FSM) 111 (and other components and / or logic, such as shift registers and / or control and status logic), which is configured to identify individual data frames 122 of a data stream received via the communication path 100. The FSM 111 is configured to pass the individual data frames 122 to a storage module 113 (particularly a FIFO (First In First Out) module). Furthermore, the FSM 111 is configured to pass a start frame delimiter (SFD) 121 of the preamble of the individual frame 122 to a timestamp capture module 114. The SFD 121 of the data frame 122 can be considered as a trigger indicating the fact that the data frame 122 has been received at the receiving unit 110. Therefore, the FSM 111 can be considered as a trigger module configured to generate a trigger 121 indicating the receipt of the data frame 122.
[0023] 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 a data frame, for triggering a timestamp. In the case of Ethernet, the trigger 121 may be an SFD. In the case of a different protocol, 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.
[0024] The timestamp capture module 114 is configured to capture the timestamp 124 of the data frame 122 at the time when the SFD 121 is received by the timestamp capture module 114. The timestamp 124 can be determined using the time value of the master time 123 provided by the master timer 163, wherein the master timer 163 can use a clock that has been synchronized using, for example, gPTP (General Precision Time Protocol). The timestamp 124 is provided to the storage module 113 together with the corresponding data frame 122.
[0025] The receiving unit 110 may further include a classification module 112 configured to assign a DMA (direct memory access) channel number 125 to metadata of individual data frames 122 (based on the data included in the data frame 122). The DMA channel number 125 of the data frame 122 may be stored in the storage module 113 together with the corresponding data frame 122. The data frame 122 may include metadata about the actual payload of the frame that has been received via the communication path 100.
[0026] Thus, a separate data frame 122 including data, such as sensor data from a sensor, may be stored with a DMA channel number 125 as part of the metadata of the frame 122 and a timestamp 124 indicating the moment the frame 122 was received by the receiving unit 110. The extended frame data 126 may be stored in a memory module 116 (e.g., a random access memory (RAM)) via an interface bus (e.g., AXI) 127 using a DMA controller 115. The storage location within the memory module 116 may depend on the DMA channel number 125. The extended frame data 126 may include the DMA channel number 125, the data frame 122, the timestamp 124, and / or the check data 211.
[0027] In the event 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 that the data frame 122 is associated with an erroneous timestamp 124 .
[0028] Figure 2AAn example of a receiving unit 110 is shown, which includes a generator 210 for generating check data 211 based on the data of the data frame 122 and the time stamp 124. The check data 211 may include or may be an error detection code, such as a CRC (Cyclic Redundancy Check), which is calculated on the data of the frame 122 and the time stamp 124 using a predefined data generation method. The check data 211 may be stored together with the frame 122 to provide an extended frame data 126 that also includes the check data 211.
[0029] The check data 211 can be used to detect the error situation that the timestamp 124 of the data frame 122 has been changed and / or is incorrect. For this purpose, the check data 211 can be compared with the timestamp 124 stored together with the data frame 122 (in the memory module 116). The verification data can be generated (using the above-mentioned data generation method) based on the data of the data frame 122 and based on the timestamp 124 stored together with the data frame 122. The verification data may include an error detection code (e.g., CRC) or may be an error detection code. If the check data 211 is different from the verification data, the frame 122 can be discarded and a hardware fault can be reported. Otherwise, the frame and timestamp processing can be continued. The comparison of the check data 211 and the verification data can be performed in software on the CPU 162 or using dedicated hardware.
[0030] The frame 122 for which the timestamp 124 is captured and for which the check 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 included in the frame 122 may be used in conjunction with the timestamp 124 (the timestamp of the local master time 123 provided by the master timer 163 at the receiving unit 110) to provide accurate clock and / or synchronization (e.g., using gPTP). The master timer 163 may have been synchronized using the gPTP protocol.
[0031] Another reason for performing an erroneous timestamp may be an error of the timestamp capture module 114 and / or the trigger module 111. For example, it may happen that the timestamp capture module 114 does not update the timestamp 124 and remains fixed to a constant value of the timestamp. For this purpose, a redundant capture module 220 may be provided, which is configured to capture a redundant timestamp 224 at the instant of the SFD 121 using a redundant and / or auxiliary timer 164 providing an auxiliary time 223.
[0032] 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 do not correspond (e.g., because the primary timestamp 124 is fixed at a constant value), a fault is detected. The redundant timestamp 224 and the primary timestamp 124 may be compared using software running on the processor unit 162. Alternatively, the redundant timestamp 224 and the primary timestamp 124 may be compared using dedicated hardware.
[0033] 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 with each other (e.g., a predetermined ratio and / or a predetermined offset). When determining whether the redundant timestamp 224 matches and / or corresponds with the primary timestamp 124, the predetermined relationship between the two timestamps 124, 224 may be considered (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.
[0034] When a new frame 122 is received, a flag "Rx has occurred" may be set. Such a flag may be set in hardware by the DMA controller 115, or by software running, for example, on the processor unit 162. In addition, the flag may be cleared by software (e.g., running on the processor unit 162). For example, the software running on the processor unit 162 may read the timestamps 124, 224 from the register module 221. The flag "Rx has occurred" may be checked to verify whether the timestamps 124, 224 should have been updated. If the flag "Rx has occurred" is set, the redundant timestamp 224 and the main timestamp 124 may be compared (as outlined above). On the other hand, if the flag "Rx has occurred" is not set, the comparison of the redundant timestamp 224 and the main timestamp 124 may be omitted.
[0035] For a new frame 122 with a timestamp 124 (perhaps only for frames used for clock and / or time synchronization), a CRC can be calculated based on the data of the frame 122 and the associated timestamp 124 stored in the memory module 116 (e.g., using software running on the processor unit 162). This CRC can be referred to as verification data. The calculated CRC (i.e., verification data) can be compared with the stored check data 211 (stored in the RAM 116). When the verification data and the stored check data 211 do not correspond, the frame 122 can be discarded and a hardware fault can be reported. Otherwise, frame and timestamp processing can continue.
[0036] It should be noted that check data 211 is typically determined using hardware (ie, generator 210). Verification data, on the other hand, is typically determined using software (running on processor unit 162).
[0037] The captured timestamps 124 and redundant timestamps 224 may be repeatedly (e.g., every 100 ms) provided to a register module 221. The register module 221 may include a register for each timestamp 124, 224. The values of the corresponding times 123, 223 (i.e., timestamps) 124, 224 (provided by the corresponding timers 163, 164) may be written into the corresponding registers of the register module 221. Thus, the register module 221 provides a consistent snapshot of the contents of the timestamp capture modules 114, 220 (where the timestamp capture modules 114, 220 may each be implemented as registers).
[0038] Software (e.g., software of processor unit 162) may access registers of register module 221 (repeatedly, e.g., every 100 ms) for comparing captured timestamp 124 and redundant timestamp 224. Both timestamps 124, 224 may be checked to see if they fit together and / or correspond, where unexpected differences may indicate a hardware failure.
[0039] If the "Rx has occurred" flag is set (or more generally, if reception has occurred within the observation interval), it may be checked whether the timestamp 124 has been stepped forward. This allows detection of a stuck timer failure within the trigger module 111 and / or a problem in SFD generation. After processing, the "Rx has occurred" flag may be cleared.
[0040] Figure 1C An example of a sending unit 130 is shown, which includes modules similar to those of the receiving unit 110. It should be noted that features described in the context of the receiving unit 110 are also valid for the sending unit 130 (in a corresponding manner).
[0041] The processing device 160 may include a memory module 136 (e.g., RAM) for storing data that may be passed to the DMA controller 135 via the interface bus 147. The memory module 136 may be part of the transmission unit 130 in the communication interface 161. In this case, the DMA controller 135 may be omitted. The individual frames 146 may be stored in a storage module 133 (e.g., a FIFO module). The metadata of the extended frame 146 (which includes the data frame 142) may be analyzed using the timestamp control module 134, which is configured to decide (based on the metadata of the extended frame 146) whether the timestamp 124 is to be stored in the memory module 136 with the frame 146 (where the frame 146 is already stored in the memory module 136).
[0042] The transmitting unit 130 includes a timestamp capture module 114 configured to capture a timestamp 124 at each SFD 121 of the data frame 142 based on a timer value 123 of a master timer 163 (which may be synchronized using gPTP). The timestamp 124 may be stored with the frame 146 in the memory module 136.
[0043] As already outlined in the context of the receiving unit 110 and as Figure 2B As shown in , the sending unit 130 may include a generator 210, and the generator 210 is configured to generate verification data 211. In addition, the receiving unit 110 may include a redundancy capture module 220 and a register module 221.
[0044] In all individual transmit (Tx) events (when the DMA controller 135 has fetched a new frame 146 from the RAM 136), a flag "Tx has occurred" may be set (set by hardware or software when a frame 146 is provided for fetching). Such a flag may be set in hardware by the DMA controller 135 and may be cleared by software (e.g., software of the processor unit 162).
[0045] For transmit events with timestamps (which may only be the case for clock and / or time synchronization frames), a CRC may be calculated on the Tx 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. In addition, the calculated CRC (i.e., verification data) may be compared to the stored check data 211 (stored in the memory module 136). When they are different, a signal transmission problem may be detected and a hardware fault may be reported. Otherwise, TS processing may continue.
[0046] The timestamp 124 and the redundant timestamp 224 may be provided to a register module 221. The software of the processor unit 162 may check whether the two fit together. The register module 221 may include or may be present in ("special function") registers for storing the values of the timestamps 124, 224. The software (of the processor unit 162) may access the registers of the register module 221 and may perform a software-based comparison of the timestamps 124, 224. Unexpected differences (which deviate from the predetermined relationship between the timestamps 124, 224) indicate a hardware failure.
[0047] If the "Tx Occurred" flag is set (or more generally, if a transmit event has occurred), then the timestamp 124 may be checked to see if it has been stepped forward, thereby allowing detection of stuck timer failures and / or problems in SFD generation.
[0048] Subsequently, the "Tx Occurred" flag may be cleared.
[0049] Figure 1D An example of a data packet 170 is shown, which can be received by a receiving unit 110 (in particular a module 111) on a communication path 100 and / or sent by a sending unit 130 (in particular a module 131) on a communication path 100. The data packet 170 includes a data frame 122, 142. In addition, the data packet 170 typically includes additional data 171 (with one or more data fields). In the case of Ethernet, the data packet 170, the additional data 171 may include a preamble, an SFD, an FCS (frame check sequence) and / or an IFG (interframe gap). The check data 211 can be determined based only on the data frame 122, 142 (excluding the additional data 171). The trigger 121 can be contained in the additional data 171 (as is the case for example for Ethernet) or in the data frame 122, 142 (as is the case for CAN).
[0050] Figure 3 A flowchart of an example (possibly computer-implemented) method 300 for time stamping data at a receiving unit 110 and / or a sending unit 130 in a communication interface 161 is shown. The method 300 is intended to provide reliable time synchronization across different communication interfaces 161 within a communication network. The data may include sensor data provided by one or more sensors (e.g., vehicle sensors). The method steps may be performed by software and / or hardware.
[0051] The method 300 includes processing 301 a data frame 122 , 142 including data, wherein the processing 301 may include receiving the data frame 122 or sending the data frame 142 .
[0052] Furthermore, the method 300 includes capturing 302 a timestamp 124 using a master timer 163 (where the master timer 163 provides a master time 123) upon receiving a trigger 121 (e.g., a start frame delimiter (SFD)) indicating processing 301 of a data frame 122, 142. The timestamp 124 may be captured using a (hardware-based) timestamp capture module 114, where the timestamp capture module 114 may be configured to capture a time 134 indicated by the master timer 163 in response to receiving the trigger 121.
[0053] Furthermore, the method 300 comprises generating 303 check data 211 based on the data frames 122, 142 and the time stamp 124. The check data 211 may comprise an error detection code generated using a predetermined data generation method.
[0054] The method 300 further comprises storing 304 the check data 211 together with the data frames 122, 142 and the timestamp 124 in a memory module 116, 136 (e.g., in a RAM), wherein the memory module 116, 136 is accessible by an application software (which utilizes the receiving unit 110 and / or the sending unit 130 to exchange the data frames 122, 142 with one or more other entities). For example, the application software may be configured to fuse sensor data provided by a plurality of different (vehicle) sensors. The application software may be executed on a processor unit 162 of a processing device 160, which may include the receiving unit 110 and / or the sending unit 130.
[0055] It should be noted that when receiving data, the check data 211, the data frame 122, and the timestamp 124 can be stored jointly and / or actively in the memory module 116. On the other hand, when sending data, the data frame 142 is generally already stored in the memory module 136 (before the timestamp 124 and / or the check data 211 are generated). In this case, the data frame 142 can be obtained from the memory module 136 for generating the check data 211. Subsequently, the check data 211 and / or the timestamp 124 can be stored in the memory module 136 (in conjunction with and / or linked to the already stored data frame 142).
[0056] The check data 211 may be used to verify whether the timestamp 124 (which is stored in the memory module 116, 136 together with the data frame 122, 142) has been altered and / or is incorrect. Therefore, the method 300 may include checking the timestamp 124 based on the check data 211. Thus, reliable timestamping of data (particularly according to the ASIL D integrity level) is achieved.
[0057] Thus, a processing device 160 configured to provide reliable data timestamps (at a predetermined ASIL level) is described. The processing device 160 may be a receiving unit and / or may be configured to receive one or more data frames 122. Alternatively or additionally, the processing device 160 may be a sending unit and / or may be configured to send one or more data frames 142.
[0058] The processing device 160 is configured to process data frames 122, 142 including data. Processing may include receiving the data frames 122 via the data communication path 100. Alternatively or additionally, processing may include sending the data frames 142 via 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.
[0059] In addition, the processing device 160 may be configured to capture a timestamp 124 using a master timer 163 upon receiving a trigger 121 indicating processing of a data frame 122, 142. The timestamp 124 of a master time 123 provided by the master timer 163 may be captured. The master time 123 may be provided by a master timer 163 of the processing device 160. The master timer 163 may have been synchronized with one or more other processing devices 160 within a communication network including the data communication path 100 using a synchronization method, such as gPTP (generalized precision time protocol). An offset and / or rate of the master timer 163 may have been determined using a synchronization method.
[0060] In the case of Ethernet, the trigger 121 may be a start frame delimiter (SFD) of the data packet 170. The timestamp 124 may be captured using a hardware-based timestamp capture module 114.
[0061] The processing device 160 may also be configured to generate check data 211 based on the data frames 122, 142 and the timestamp 124 (using a (predetermined) data generation method). The check data 211 may enable the check data 211 to verify whether the timestamp 124 stored together with the data frames 122, 142 has been changed relative to the timestamp 124 captured when the trigger 121 was received. The check data 211 may include an error detection code determined based on the data of the data frames 122, 142 and the timestamp 124, in particular a cyclic redundancy check (CRC).
[0062] The check data 211 may be stored in the memory modules 116, 136 together with the data frames 122, 142 and the timestamp 124. For example, the check data 211, the data frames 122, 142 and the timestamp 124 may be stored in the memory modules 116, 136 using the DMA controllers 115, 135. Alternatively, the check data 211, the data frames 122, 142 and the timestamp 124 may be stored in the local memory modules 116, 136 (without using the DMA controllers 115, 135), such as in the case of a CAN network. The memory modules 116, 136 may be random access memories (RAMs), such as local RAMs. 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 timestamp 124. In addition, the application software may utilize the check data 211 to verify the correctness of the timestamp 124. Thus, a reliable solution for time stamping data is provided.
[0063] The memory modules 116, 136 may be part of a communication interface 161 of the processing device 160, wherein the communication interface 161 includes the sending unit 130 and / or the receiving unit 110. The receiving unit 110 and / or the sending unit 130 may each include a memory module 116, 136. In this case, the DMA controllers 115, 135 may be omitted. Alternatively or additionally, the processing device 160 may include one or more memory modules 116, 136 located outside the communication interface 161 (e.g., as part of the processor unit 162). In this case, the sending unit 130 and / or the receiving unit 110 in the communication interface 161 may include the DMA controllers 115, 135.
[0064] By using software on the processor unit 162, the processing device 160 may be configured to verify, based on the check data 211, whether the timestamp 124 stored with the data frames 122, 142 within the memory modules 116, 136 has been altered and / or is incorrect. For this purpose, by using software on the processor unit 162, the processing device 160 may generate the verification data based on the data frames 122, 142 and the timestamp 124 stored within the memory modules 116, 136. The verification data may be generated using the same data generation method as used to generate the check data 211, in particular the same method used to generate the error detection code.
[0065] The verification data may be compared to the check data 211 stored in the memory module 116, 136 along with the data frame 122, 142. It may then be determined based on the comparison of the verification data with the check data 211 whether the timestamp 124 stored in the memory module 116, 136 along with the data frame 122, 142 has been altered and / or is incorrect. If the verification data and the check data 211 are identical and / or match, it may be concluded that the timestamp 124 has not been altered and / or is correct. Otherwise, it may be concluded that the timestamp 124 has been altered and / or is incorrect.
[0066] If it is determined that the timestamp 124 stored in the memory module 116, 136 along with the data frame 122, 142 has been altered and / or is incorrect, the processing device 160 can be configured to report a fault. Alternatively or additionally, if it is determined that the timestamp 124 stored in the memory module 116, 136 along with the data frame 122, 142 has been altered and / or is incorrect, the processing device 160 can be configured to discard the data frame 111, 131 from the memory module 116, 136.
[0067] Therefore, the reliability of application software using the time-stamped data frames 122 , 142 may be improved.
[0068] The processing device 160 may be configured to determine whether the data frame 122, 142 includes data for clock and / or time synchronization (e.g., for synchronizing a clock used to provide the master time 123). If it is determined that the data frame 122, 142 is a frame for clock and / or time synchronization, it may be verified whether the timestamp 124 stored in the memory module 116, 136 along with the data frame 122, 142 has been altered and / or is incorrect.
[0069] In other words, the verification of the timestamps may be performed only on a portion of the data frames 122, 142 processed by the processing device 160, thereby providing an improved trade-off between reliability and computational efficiency. It may be ensured that all data frames 122, 142 (in particular gPTP frames) related to clock and / or time synchronization are verified, thereby providing a high integrity (in particular ASIL) level with respect to clock and / or time synchronization in an efficient manner.
[0070] The processing device 160 may be configured to capture the redundant timestamp 224 using the auxiliary timer 164 (e.g., a software-based or hardware-based timer) upon receiving the trigger 121 indicating the processing of the data frame 122, 142. The auxiliary timer 164 may be configured to provide the auxiliary time 223. The timestamp 124 may be compared with the redundant timestamp 224. Furthermore, based on the comparison, it may be verified whether the timestamp capture module 114 for capturing the timestamp 124 and / or the trigger modules 111, 131 for generating the trigger 121 are faulty. Therefore, the reliability of the timestamp may be further improved.
[0071] By running software on the processing unit 162, the processing device 160 may be configured to determine the time interval and / or the number of data frames 122, 142 since the last time the timestamp capture module 114 for capturing the timestamp 124 and / or the trigger module 111, 131 for generating the trigger 121 was verified to be faulty. If the time interval is equal to or greater than a predetermined verification time (e.g., 100 ms) and / or the number of data frames 122, 142 is equal to or greater than a predetermined verification number (e.g., 10), a redundant timestamp 224 (for verifying the timestamp capture module 114 and / or the trigger module 131) may be captured and / or the timestamp 124 may be compared with the redundant timestamp 224. By doing so, an improved tradeoff between reliability and computational efficiency may be provided.
[0072] The processing device 160 may be configured to set a flag indicating a new data frame 122, 142 when processing the data frame 122, 142. Furthermore, the processing device 160 may be configured to clear the flag after verifying whether the timestamp capture module 114 for capturing the timestamp 124 and / or the trigger module 111, 131 for generating the trigger is faulty. By doing so, the reliability of the described verification scheme may be further improved (by avoiding false positives).
[0073] exist Figure 2A (for receiving unit 110) and / or Figure 2B The components of the processing device 160 depicted in (for the sending unit 130) may be implemented only as hardware (wherein the memory modules 116, 136 may be implemented separately, for example as memory within the processor unit 162). Therefore, the tasks performed by the depicted components, one or more timestamp capture modules 114, 220, register module 221 and / or generator 210 may be performed only by hardware. The check data 211 may be generated using a hardware-based (CRC) generator 210.
[0074] On the other hand, other tasks, such as calculation of verification data, comparison of check data 211 and verification data and / or comparison of time stamps 124 , 224 may be performed using software running on processor unit 162 of processing device 160 .
[0075] It should be noted that the processing device 160 may include one or more communication interfaces 161 configured as described in the present disclosure (for generating the verification data 211 to verify the timestamp 124). In addition, the processing device 160 may include one or more communication interfaces that do not include the timestamp verification scheme described in the present disclosure (and in accordance with Figure 1B and Figure 1C Furthermore, it should be noted that the processing device 160 and / or the communication interface 161 of the processing device 160 may be configured to provide check data 211 for verifying the timestamp 124 only for a subset of the data frames 122 , 142 .
[0076] It should be noted that the description and the accompanying drawings illustrate only the principles of the proposed method and system. Those skilled in the art will be able to implement various arrangements that embody the principles of the present invention and are included in its spirit and scope, although not explicitly described or shown herein. In addition, all examples and embodiments summarized in this disclosure are primarily and explicitly intended to be used only for explanatory purposes to help the reader understand the principles of the proposed method and system. In addition, all statements of the principles, aspects, and embodiments of the present invention and their particular examples provided herein are intended to cover their equivalents.
Claims
1. A processing device, configured to: processing the data frame upon receiving a trigger indicating processing of the data frame; Use the master timer to capture timestamps; generating verification data based on the data frame and the timestamp; as well as The verification data are stored together with the data frame and the time stamp in a memory module.
2. The processing device according to claim 1, Wherein the check data enables verification whether the timestamp stored together with the data frame is altered with respect to the timestamp captured when the trigger is received.
3. The processing device according to claim 1, The check data includes an error detection code determined based on the data and the timestamp of the data frame.
4. The processing device according to claim 1, The processing device is configured to: verifying based on the check data whether the timestamp stored together with the data frame in the memory module has been altered and / or is incorrect; and If it is determined that the timestamp stored with the data frame within the memory module has been altered and / or is incorrect, a fault is reported.
5. The processing device according to claim 4, Wherein the processing device is configured to discard the data frame from the memory module if it is determined that the timestamp stored with the data frame in the memory module has been altered and / or is incorrect.
6. The processing device according to claim 4, The processing device is configured to: generating verification data based on the data frame and the timestamp stored in the memory module; comparing the verification data with the check data stored in the memory module along with the data frame; as well as determining, based on the comparison of the verification data with the check data, whether the timestamp stored together with the data frame in the memory module has been altered and / or is incorrect, The verification data is generated using the same data generation method as the method used to generate the verification data.
7. The processing device according to claim 4, The processing device is configured to: determining whether the data frame includes data for clock synchronization and / or time synchronization; and If it is determined that the data frame is a frame for clock synchronization and / or time synchronization, it is verified whether the time stamp stored in the memory module together with the data frame has been altered and / or is incorrect.
8. The processing device according to claim 1, The processing device is configured to: upon receiving said trigger indicating said processing of said data frame, capturing redundant timestamps using an auxiliary timer; comparing the timestamp to the redundant timestamp; and Based on the comparison between the timestamp and the redundant timestamp, it is verified whether a timestamp capturing module for capturing the timestamp and / or a trigger module for generating the trigger is faulty.
9. The processing device according to claim 8, The processing device is configured to: determining a time interval and / or number of data frames since the time stamp capture module for capturing the time stamp and / or the trigger module for generating the trigger was last verified to be faulty; and If the time interval is equal to or greater than a predetermined verification time, and / or the number of data frames is equal to or greater than a predetermined verification number, the timestamp is compared with the redundant timestamp.
10. The processing device according to claim 1, wherein the processing device is configured to receive the data frame; and Processing includes receiving the data frame via a data communications path.
11. The processing device according to claim 1, wherein the processing device is configured to send the data frame; and Processing includes transmitting the data frame via a data communications path.
12. The processing device according to claim 1, The data frame is an Ethernet frame, a CAN frame or a PCIe frame.
13. The processing device according to claim 1, The timestamp is captured using a hardware-based timestamp capture module and / or the verification data and the timestamp are stored in the memory module using a direct memory access controller.
14. A method for time stamping data at a communication interface: upon receiving a trigger indicative of said processing of said data frame, processing a data frame including data; Use the master timer to capture timestamps; generating verification data based on the data frame and the timestamp; as well as The verification data are stored together with the data frame and the time stamp in a memory module.
