Data processing method and data processing device

Abstract

A method for data processing, comprising: determining, at a first device, a first parameter characterizing a time difference between a previous synchronization of the first device with a second device and a reference time associated with first data processed by the first device, sending the first parameter and a second parameter characterizing a time associated with the previous synchronization by the first device to the second device.

Description

Technical field

[0001] The disclosure relates to a method for data processing.

[0002] The disclosure further relates to a data processing device. Summary

[0003] Example embodiments relate to a method, for example a computer-implemented method, for data processing, comprising: determining, at a first device, a first parameter characterizing a time difference between a previous synchronization of the first device with a second device and a reference time associated with first data processed by the first device; sending the first parameter and a second parameter characterizing a time associated with the previous synchronization by the first device to the second device. In some embodiments, this enables the provision of a temporal reference, for example, for sending data, for example the first data.

[0004] In some embodiments, transmitting includes transmitting the first data. In other words, in some embodiments, the first parameter and the second parameter may be transmitted, for example, together with the first data.

[0005] In some embodiments, the method comprises receiving, e.g., repeatedly receiving, e.g., periodically receiving, second data from the second device, and synchronizing with the second device based on the second data.

[0006] In some embodiments, the method comprises providing a connection event counter for counting a number of connection events associated with the second device, and optionally counting the number of connection events associated with the second device using the connection event counter. In some embodiments, a connection event may be defined as the receipt of data, for example, in the form of a data packet. Thus, in some embodiments, a connection event may occur when the first device receives data from the second device.

[0007] In some embodiments, the method comprises: providing a timer for determining the time difference between the previous synchronization of the first device with the second device and the reference time, and optionally determining the time difference between the previous synchronization of the first device with the second device and the reference time using the timer.

[0008] In some embodiments, the method comprises receiving, e.g. repeatedly receiving, e.g. periodically receiving, second data or the second data from the second device, starting, e.g. restarting, the timer upon receipt of the second data, and optionally stopping the timer when the first data is available, e.g. at the reference time.

[0009] In some embodiments, the method comprises: determining the first parameter using the timer, for example, using a timer value of the timer as the first parameter.

[0010] In some embodiments, the method comprises: determining the second parameter using the connection event counter, for example, using the number of connection events associated with the second device as the second parameter.

[0011] In some embodiments, the method comprises at least one of: a) using a wireless data exchange for transmitting, for example using a WPAN (Wireless Personal Area Network) technology for transmitting, for example using a BLE (Bluetooth Low Energy) technology for transmitting, b) using one or more of the wireless data exchanges for receiving, for example using a WPAN (Wireless Personal Area Network) technology for receiving, for example using a BLE (Bluetooth Low Energy) technology for receiving.

[0012] For example, in some embodiments, the method includes using a BLE technology for both transmitting and receiving.

[0013] In some embodiments, a BLE connection mode as defined in or compatible with the Bluetooth Core Specification, Version 5.4, Version Date 2023-01-31, is used, for example, for transmitting and receiving. Details of the BLE Connected Mode that may be used in some embodiments can be found, for example, in the Bluetooth Core Specification, Version 5.4, Volume 1, Part A, Chapter 4.2.2.6 (page 263).

[0014] In some embodiments, the connection event counter for counting a number of connection events associated with the second device may be a connection event counter (connEventCounter), such as that specified in Volume 5, Part B, Chapter 4.5.1 of the Bluetooth Core Specification, Version 5.4.

[0015] In some embodiments, the second data may be received by the second device periodically based on a connection interval (connlnterval), such as specified in Volume 6, Part B, Chapter 4.5.1 of the Bluetooth Core Specification, Version 5.4.

[0016] In some embodiments, the first data are linked to and / or characterize at least one of the following elements: a) sensor data from at least one sensor, b) sensor data linked to at least one vehicle, for example a passenger car, c) pressure data characterizing, for example, a tire pressure of a vehicle, d) temperature data characterizing, for example, a temperature associated with a tire of a vehicle, e) acceleration data characterizing, for example, an acceleration of a component attached, for example, to a tire of a vehicle, and / or data derived from the acceleration (for example, an angular position, for example linked to a specific point in time, and / or a time difference since reaching or passing a predetermined angular position, and / or a period of a wheel revolution, and / or an angular velocity of a wheel,and / or rotational speed of (part of) a wheel, and / or a parameter derived from a rotation of a wheel).

[0017] In some embodiments, other types of wireless data exchange, for example other than BLE, may also be used for transmitting and / or receiving, for example a ZigBee technology or the like.

[0018] In some embodiments, other types of wireless data exchange, for example other than WPAN, may also be used for sending and / or receiving.

[0019] Further exemplary embodiments relate to a method, for example a computer-implemented method, for processing data provided by a first device, for example the first device according to the embodiments, comprising: receiving, at a second device, a first parameter from the first device characterizing a time difference between a previous synchronization of the first device with the second device and a reference time associated with the first data processed by the first device, and a second parameter characterizing a time associated with the previous synchronization, and optionally the first data. In some embodiments, the method may optionally further comprise processing at least one of the first parameters and / or the second parameter and / or the first data.

[0020] Further exemplary embodiments relate to an apparatus for carrying out the method according to the embodiments.

[0021] Further exemplary embodiments relate to a sensor device comprising at least one device according to the embodiments.

[0022] Further exemplary embodiments relate to a tire pressure monitoring system for a vehicle, comprising at least one of the following elements: a) a device according to the embodiments, b) a sensor device according to the embodiments.

[0023] Further exemplary embodiments relate to a use of the method according to the embodiments and / or the device according to the embodiments and / or the sensor device according to the embodiments and / or the tire pressure monitoring system according to the embodiments for at least one of: a) sending data, for example the first data, with a temporal reference to the second device, b) providing a timestamp for the first data, c) enabling the use of a WPAN (Wireless Personal Area Network) technology for the sending, for example using a BLE (Bluetooth Low Energy) technology, d) sending sensor data relating to the tire pressure monitoring together with associated time information, e) performing a, for example automatic, learning procedure, for example a self-learning procedure, to determine specific tire pressure values ​​associated with a vehicle,to a corresponding tire of the vehicle., Brief description of the exemplary figures

[0024] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Fig. 1 schematically shows a simplified flow diagram according to exemplary embodiments, Fig. 2 schematically shows a simplified block diagram according to exemplary embodiments, Fig. 3 schematically shows a simplified flow diagram according to exemplary embodiments, Fig. 4 schematically shows a simplified flow diagram according to exemplary embodiments, Fig. 5 schematically shows a simplified flow diagram according to exemplary embodiments, Fig. 6 schematically shows a simplified flow diagram according to exemplary embodiments, Fig. 7 schematically shows a simplified flow diagram according to exemplary embodiments, Fig. 8 schematically shows a simplified flow diagram according to exemplary embodiments, Fig. 9 schematically shows a simplified flow diagram according to exemplary embodiments, Fig. 10 schematically shows a simplified block diagram according to exemplary embodiments, Fig. 11 schematically shows a simplified block diagram according to exemplary embodiments, Fig. 12 schematically shows a simplified timing diagram according to exemplary embodiments, Fig. 13 schematically shows aspects of use according to exemplary embodiments.

[0025] Exemplary embodiments, see for example Fig. 1 and Fig. 2, relate to a method, for example a computer-implemented method, for data processing, comprising: determining 102 ( Fig. 1), on a first device 10 ( Fig. 2), a first parameter P1, which represents a time difference between a previous synchronization SYNC ( Fig. 1) the first device 10 with a second device 20 ( Fig. 2) and a reference time linked to the first data DAT1 processed by the first device 10, sending 104 ( Fig. 1) of the first parameter P1 and a second parameter P2 characterizing a point in time associated with the previous synchronization SYNC, by the first device 10 to the second device 20. In some embodiments, this makes it possible to provide a temporal reference, for example for sending data, for example the first data DAT1.

[0026] In some embodiments, sending 104 comprises sending 104a the first data DAT1. In other words, in some embodiments, the first parameter P1 and the second parameter P2 may be sent, for example, together with the first data DAT1. In some embodiments, this enables, for example, the second device 20 to evaluate the first data DAT1 with a specific temporal reference, as characterized, for example, by at least one of the first parameter P1 and the second parameter P2.

[0027] The optional block 100 of Fig. 1 symbolizes an exemplary previous synchronization SYNC according to some embodiments, which in some embodiments may be performed, for example, based on second data DAT2 exchanged between the first device 10 and the second device 20, e.g., received by the first device 10 from the second device 20.

[0028] In some embodiments, Fig. 3, the method comprises: receiving 110, for example, repeatedly receiving 110a, for example, periodically receiving 110b, the second data DAT2 from the second device 20, synchronizing 112 with the second device 20 based on the second data DAT2. In some embodiments, this enables the first device 10 to synchronize with the second device 20 in a periodic manner. In some embodiments, a period time for the periodic receiving 110b of the second data DAT2 can be configured and / or standardized and / or negotiated and / or predetermined, for example, by the second device 20.

[0029] In some embodiments, Fig. 4, the method comprises: providing 120 a connection event counter CEC for counting a number of connection events associated with the second device 20, and optionally counting 122 the number NUM-CE of connection events associated with the second device 20 using the connection event counter CEC. In some embodiments, a connection event may be defined as receipt of data by the first device 10 from the second device 20, for example in the form of a data packet, for example the second data DAT2. Thus, in some embodiments, a connection event may occur, for example, when (for example, whenever) the first device 10 receives the second data DAT2 from the second device 20.In some embodiments, the reception of empty data packets (e.g., without payload or user data) is also possible and may, in some embodiments, characterize a connection event.

[0030] In some embodiments, Fig. 2, similar to the first device 10 and its connection event counter CEC, the second device 20 can also provide a connection event counter CEC', wherein the connection event counter CEC' of the second device 20 counts, for example, the number of connection events, as characterized, for example, by the second device 20 sending the second data DAT2 to the first device 10. In other words, both devices 10, 20 can provide, for example, maintain, a corresponding connection event counter CEC, CEC', the counter value of which indicates how many connection events have occurred, for example, starting from an initialization state in which the counter(s) CEC, CEC' may have been reset, for example, to zero.

[0031] In some embodiments, the second data DAT2 may or may not include a payload (also referred to as user data), for example, user data. In other words, in some embodiments, the counting 122 ( Fig. 4) can be performed, for example, by the first device 10 even if the received second data DAT2 characterizes "empty" data packets, for example, data packets that do not contain any payload or user data. In this way, in some embodiments, synchronization of the first device 10 with the second device 20 is ensured even if no payload data is to be sent from the second device 20 to the first device 10.

[0032] In some embodiments, Fig. 5, the method comprises: providing 130 a timer TIM, for example by the first device 10, for determining the time difference between the previous synchronization SYNC of the first device 10 with the second device 20 and the reference time, and optionally determining 132 the time difference t_synch, Δt between the previous synchronization of the first device 10 with the second device 20 and the reference time using the timer TIM.

[0033] In this regard, Fig. 12 is an exemplary timing diagram illustrating connection events that may be used in some embodiments for synchronization between devices 10, 20. The first time axis t1 is linked to the first data DAT1.

[0034] In some embodiments, Fig. 2, the first data DAT1 are linked to and / or characterize at least one of the following elements: a) sensor data SD from at least one sensor 12, b) sensor data SD-V associated with at least one vehicle 30 ( Fig. 11), for example a passenger car, c) pressure data PD, which characterize, for example, a tire pressure of a vehicle 30, d) temperature data TD, which characterize, for example, a temperature associated with a tire of a vehicle.In some embodiments, the first data DAT1 may also include and / or characterize other data, e) acceleration data, for example for characterizing an acceleration of a component that is attached, for example, to a tire of a vehicle 30, and / or data derived from the acceleration, for example an angular position, for example linked to a specific point in time, and / or a time difference since reaching or passing a predetermined angular position, and / or a period of a wheel revolution, and / or an angular velocity of a wheel, and / or a rotational speed of a wheel or part of a wheel, and / or a parameter derived from a rotation of a wheel.

[0035] As in Fig. 12, the second time axis t2 is the connection event counter CEC ( Fig. 2) of the first device 10, and the third time axis t3 is associated with the connection event counter CEC' ( Fig. 2) of the second device 20. The element e1 in Fig. 12 symbolizes the beginning of a connection that enables data exchange between devices 10, 20. Element e2 symbolizes a first connection event with the number "Ox001", for example, "1" in hexadecimal notation, on the time axes t2, t3. It should be noted that further, for example subsequent, connection events "0x002", ..., "0x2E0", ..., "0x2EE" are also exemplary in Fig. 12 are shown.

[0036] In some embodiments, the connection events, which may be characterized, for example, by the second device 20 ( Fig. 2) sends the second data DAT2 to the first device 10 periodically, for example with a predetermined connection interval e3.

[0037] In other words, in some embodiments, Fig. 6, the method comprises: receiving 135, for example repeated receiving 135a, for example periodic receiving 135b, the second data DAT2 from the second device 20, for example by the first device 10, starting 137, for example restarting 137a, the timer TIM upon receipt of the second data DAT2, and optionally stopping 139 the timer TIM when the first data DAT1 is available, for example at the reference time RPT ( Fig. 12).

[0038] In some embodiments, Fig. 12, for example, a specific synchronization or resynchronization of the first device 10 with the second device 20 is characterized by a value "0x2E5" of the connection counters CEC, CEC'. In some embodiments, this (re)synchronization can be triggered by the first device 10 receiving the second data DAT2 from the second device 20 at the time T1 associated with the value "0x2E5" of the connection counters CEC, CEC'.

[0039] As above with reference to Fig. 6, in some embodiments, the first device 10 may set its timer TIM ( Fig. 2) start or restart upon receipt of the second data DAT2, for example at the connection event “0x2E5”, for example at time t3 = T1.

[0040] As also exemplified with reference to Fig. 6, in some embodiments, the first device 10 may have its timer TIM ( Fig. 2) stop, for example, when the first data DAT1 is available, for example at the reference time specified in Fig. 12 is designated by the reference symbol RPT.

[0041] For example, if the first device 10 is used to process data associated with a tire pressure of a tire of a vehicle 30 ( Fig. 11), the reference time RPT can, for example, characterize a time at which fresh sensor data is available, for example from the sensor 12 ( Fig. 2), and / or a time at which the sensor 12, which may be mounted, for example, on a tire of the vehicle 30, has passed a predetermined reference position, for example a predetermined angular position linked to the rotation of the corresponding wheel of the vehicle 30.

[0042] In this way, in some embodiments, the value of the timer TIM may be used to characterize the time difference t_synch between the previous synchronization T1 of the first device 10 with the second device 20 and the reference time RPT.

[0043] It should be noted that in some embodiments, the preceding synchronization T1 does not necessarily occur directly before the reference time RPT, so that, for example, one or more further subsequent connection events and / or corresponding synchronizations (or resynchronizations) may occur between the synchronization T1 and the reference time RPT. This is also exemplified in Fig. 12, see for example the further connection event 0x2E6, which follows the connection event 0x2E5 associated with the exemplary synchronization T1, but precedes the reference time RPT.

[0044] However, in some embodiments, the value of the timer TIM may be used to characterize the time difference Δt between an immediately preceding synchronization associated with the connection event 0x2E6 and the reference time RPT. In some embodiments, this may be achieved, for example, by restarting the timer TIM at the connection event 0x2E6, for example, after the timer TIM was started earlier, for example, at T1 (or at another time, for example characterized by another preceding connection event).

[0045] Regardless of which (type of) time difference t_synch, Δt is used, in some embodiments, as mentioned above, this time difference t_synch, Δt can be used to establish a temporal reference, for example between the reference time RPT and a respectively preceding (for example directly preceding, in the case of Δt, or not directly preceding, in the case of t_synch) connection event 0x2E6 or 0x2E5, or generally a common time base of the devices 10, 20, as provided for example by the connection event counters CEC, CEC'.

[0046] In other words, in some embodiments ( Fig. 12), both devices 10, 20 may maintain their respective connection event counters CEC, CEC', which in some embodiments may be considered, for example, as a common time base with a first granularity (e.g., corresponding to the duration of the connection interval e3). In some embodiments, time information associated, for example, with the first data DAT1 may be provided by the timer TIM with a second granularity, e.g., an accuracy of the timer TIM, for example, in the form of the time difference t_synch, Δt. In some embodiments, the value of the connection event counter CEC, CEC' may be used together with the value of the timer TIM to provide a time reference, e.g., for sensor data as provided by the sensor 12, e.g., in the form of the first data DAT1.

[0047] In some embodiments, Fig. 7, the method thus comprises: determining 140 the first parameter P1 using the timer TIM, for example using 140a a timer value VAL-TIM of the timer TIM as the first parameter P1.

[0048] In some embodiments, Fig. 7, the method comprises: determining 142 the second parameter P2 using the connection event counter CEC, for example using 142a the number NUM-CE of connection events associated with the second device 20 as the second parameter P2.

[0049] In some embodiments, Fig. 2, the first parameter P1 may be sent from the first device 10 to the second device 20, together with the second parameter P2, and optionally together with the first data DAT1. In some embodiments, this allows the second device 20 to determine a time point associated with the first data DAT1, for example, the reference time point RPT, for example, with an accuracy of the timer TIM, even though the devices 10, 20 synchronize using the connection events, for example, with the first granularity as characterized by the connection interval e3, wherein the first granularity may, for example, be greater than the accuracy or resolution of the timer TIM.

[0050] In this respect, the element T2 in Fig. 12 shows, by way of example, a time at which the first device 10 sends the first parameter P1 and the second parameter P2 as well as the first data DAT1 to the second device 20.

[0051] In some embodiments, Fig. 8, the method comprises at least one of: a) using 150 a wireless data exchange WDX for sending 104, 104a ( Fig. 1), for example, using 150a a WPAN (Wireless Personal Area Network) technology for sending 104, 104a, for example, using 150b a BLE (Bluetooth Low Energy) technology for sending 104, 104a, b) using 152a the wireless data exchange WDX for receiving 110, 110a, 110b ( Fig. 3), for example using 152a a WPAN (Wireless Personal Area Network) technology for receiving 110, 110a, 110b, for example using 152b a BLE (Bluetooth Low Energy) technology for receiving 110, 110a, 110b.

[0052] For example, in some embodiments, the method includes using a BLE technology for both transmitting 104, 104a and receiving 110, 110a, 110b. Thus, in some embodiments, Fig. 2, the first device 10 may, for example, comprise a BLE-enabled transceiver 14. Similarly, in some embodiments, Fig. 2, the second device 20 may, for example, comprise a BLE-enabled transceiver 204.

[0053] In some embodiments, a BLE Connected Mode, as defined in or compatible with the Bluetooth Core Specification, Version 5.4, Version Date 2023-01-31, is used, for example, for transmitting 104, 104a and / or receiving 110, 110a, 110b. Details of the BLE Connected Mode that may be used in some embodiments can be found, for example, in the Bluetooth Core Specification, Version 5.4, Volume 1, Part A, Chapter 4.2.2.6 (page 263).

[0054] In some embodiments, the first device 10 or its transceiver 14 may, for example at least temporarily, assume the role of a peripheral device according to the Bluetooth Core Specification, Version 5.4, see, for example, Volume 6, Part B, Chapter 1.1 (page 2674).

[0055] In some embodiments, the second device 20 or its transceiver 204 may, for example at least temporarily, assume the role of a central unit according to the Bluetooth Core Specification, Version 5.4, see, for example, Volume 6, Part B, Chapter 1.1 (page 2674).

[0056] In some embodiments, Fig. 2, the connection event counter CEC for counting a number of connection events associated with the second device 20 may be a connection event counter (connEventCounter), such as specified in Volume 6, Part B, Chapter 4.5.1 of the Bluetooth Core Specification, Version 5.4. In some embodiments, this may also apply to the connection event counter CEC' of the second device 20. For example, the connection event counter CEC' of the second device 20 may also be a connection event counter (connEventCounter), such as specified in Volume 6, Part B, Chapter 4.5.1 of the Bluetooth Core Specification, Version 5.4.

[0057] In some embodiments, the second data DAT2 from the second device 20 may be received periodically by the first device 10, for example, based on a connection interval (connlnterval), as specified, for example, in Volume 6, Part B, Chapter 4.5.1 of the Bluetooth Core Specification, Version 5.4. For example, the connection interval e3 may be as in Fig. 12, a connection interval parameter (connlnterval) as specified, for example, in Volume 6, Part B, Chapter 4.5.1 of the Bluetooth Core Specification, Version 5.4.

[0058] Further exemplary embodiments, Fig. 9, relate to a method, for example a computer-implemented method, for processing data provided by a first device, for example the first device 10 according to the embodiments, comprising: receiving 180 a first parameter P1 characterizing a time difference between a previous synchronization SYNC of the first device 10 with the second device 20 and a reference time RPT associated with first data DAT1 processed by the first device 10, and a second parameter P2 characterizing a time T1 associated with the previous synchronization SYNC, and optionally the first data DAT1, from the first device 10 at a second device 20.In some embodiments, the method may further comprise processing 182 at least one of the first parameter P1 and / or the second parameter P2 and / or the first data DAT1, for example to determine which time point RPT is associated with the first data DAT1, for example with an accuracy greater than the first granularity corresponding to the connection interval e3.

[0059] Further exemplary embodiments, Fig. 10, refer to a device 200, 200a for carrying out the method according to the embodiments.

[0060] In some embodiments, the device 200 may be configured to perform aspects of the embodiments with respect to the first device 10, for example, to be executed by and / or for the first device 10. In some embodiments, Fig. 2, the first device 10 may comprise the device 200.

[0061] In some embodiments, device 200a may be configured to perform aspects of the embodiments related to, for example, to be executed by and / or for, the second device 20. In some embodiments, Fig. 2, the second device 20 may comprise the device 200a.

[0062] In some embodiments, the device 200, 200a comprises at least one computing unit, for example a processor 202, and at least one memory unit 204 that is associated with (i.e., can be used by) the at least one computing unit 202 to at least temporarily store a computer program PRG and / or data DAT, wherein the computer program PRG is configured, for example, to at least temporarily control an operation of the device 200, 200a, for example the execution of one or more aspects according to the embodiments.

[0063] In some embodiments, the at least one computing unit 202 comprises at least one core (not shown) for executing the computer program PRG or at least parts thereof, for example for executing the method according to the embodiments or at least one or more steps thereof.

[0064] In some embodiments, the at least one computing unit 202 may include or form part of at least one of the following elements: a microprocessor, a microcontroller, a digital signal processor (DSP), a programmable logic element (e.g., FPGA, Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), a hardware circuit, a tensor processor, a graphics processing unit (GPU), or a hardware accelerator. In some embodiments, any combination of two or more of these elements may also be used for the at least one computing unit 202.

[0065] In some embodiments, the memory unit 204 includes at least one of the following elements: a volatile memory 204a, for example, random access memory (RAM), a non-volatile memory 204b, for example, a flash EEPROM.

[0066] In some embodiments, the computer program PRG is at least temporarily stored in the non-volatile memory 204b. Data DAT (e.g., linked to at least one of the first parameter P1 and / or the second parameter P2 and / or the first data DAT1 and / or the second data DAT2), which may be used, for example, for executing aspects of the method according to the embodiments, may be at least temporarily stored in the RAM 204a.

[0067] In some embodiments, the configuration 200, 200a may be used, among other things, to implement at least one of the following elements: a) the connection event counter CEC, CEC', and / or b) the timer TIM. In some embodiments, at least some of the components a) of the connection event counter CEC, CEC', and / or b) of the timer TIM may be implemented at least partially by hardware. In some embodiments, at least some of the components a) of the connection event counter CEC, CEC', and / or b) of the timer TIM may be implemented at least partially by software PRG.

[0068] In some embodiments, an optional computer-readable storage medium SM may be provided, comprising instructions, for example in the form of a computer program PRG', wherein the computer program PRG, when executed by a computer, i.e., by the computing unit 202, may cause the computer 202 to carry out the method according to the embodiments. The storage medium SM may, for example, comprise or represent a digital storage medium such as a semiconductor storage device (e.g., a solid state drive, SSD) and / or a magnetic storage medium such as a floppy disk or a hard disk drive (HDD) and / or an optical storage medium such as a compact disc (CD) or DVD (Digital Versatile Disc), or the like.

[0069] In some embodiments, the device 200, 200a may include an optional data interface 206, for example, for unidirectional or bidirectional data exchange with an external device (not shown). For example, a data carrier signal DCS may be received via the data interface 206, for example, from the external device, for example, via a wired or wireless data transmission medium, for example, via a (virtual) private computer network and / or a public computer network such as the Internet.

[0070] In some embodiments, the data carrier signal DCS may represent or carry the computer program PRG, PRG' according to the embodiments or at least a part thereof.

[0071] Further exemplary embodiments, Fig. 2, refer to a sensor device 10 comprising at least one device 200 according to the embodiments. In some embodiments, the first device 10 may, for example, be a sensor device that, for example, comprises and / or processes data SD associated with at least one sensor 12. In some embodiments, the at least one sensor 12 is configured to determine at least one physical parameter for a tire pressure monitoring system, such as a tire pressure (i.e., the air pressure in a tire) and / or a temperature of the tire, or the like.

[0072] Further exemplary embodiments, Fig. 11, relate to a tire pressure monitoring system 1000 for a vehicle 30, comprising at least one of the following elements: a) a device 200, 200a ( Fig. 10) according to the embodiments, b) a sensor device 10 according to the embodiments.

[0073] In Fig. 11 shows, by way of example, a vehicle 30, wherein a first wheel, for example the right front wheel, comprises a first sensor device 10a, and wherein a second wheel, for example the right rear wheel, comprises a second sensor device 10b. The wheels on the left side of the vehicle 30 may also comprise (further) sensor devices, which in Fig. 11 are not shown for reasons of clarity.

[0074] The tire pressure monitoring system 1000 from Fig. 11 also includes a second device 20 that can exchange data with the sensor devices 10a, 10b, for example, via corresponding BLE data connections a1, a2, for example, using a BLE Connected Mode. In some embodiments, the second device 20 can at least temporarily assume a role as a "central unit" of the BLE data connections a1, a2, and the sensor devices 10a, 10b can, for example, at least temporarily assume a corresponding role as "peripherals."

[0075] Each of the sensor devices 10a, 10b may comprise a configuration similar to the first device 10 of Fig. 2, and thus, for example, be capable of sending at least one of a corresponding first parameter P1 and / or a corresponding second parameter P2 and / or corresponding first data DAT1 (indicating, for example, a corresponding angular position of the associated wheel) to the second device 20, for example repeatedly. Using at least some portions of this information, the second device 20 may, in some embodiments, for example, perform functions associated with evaluating tire pressure.

[0076] In some embodiments, the second device 20 may, for example, execute a self-learning procedure that determines which of the sensor devices 10a, 10b is associated with which of the wheels of the vehicle 30. In some embodiments, one or more of the respective pieces of information P1, P2, DAT1 may be used for self-learning and may, for example, be compared with information derived from further sensors (not shown), such as wheel speed sensors. In some embodiments, the information from a wheel speed sensor, for example of the right front wheel, may be correlated with the respective pieces of information P1, P2, DAT1 provided, for example, by the first sensor device 10a to determine whether the first sensor device 10a is associated with the right front wheel (or another wheel of the vehicle 30).

[0077] Further exemplary embodiments, Fig. 13, relate to a use 300 of the method according to the embodiments and / or of the device 200, 200a according to the embodiments and / or of the sensor device 10, 10a, 10b according to the embodiments and / or of the tire pressure monitoring system 1000 according to the embodiments and / or of the computer program PRG, PRG' ( Fig. 10) according to the embodiments and / or the storage medium SM according to the embodiments and / or the data carrier signal DCS according to the embodiments for at least one of: a) Sending 301 ( Fig. 13) of data, for example the first data DAT1, with a temporal reference to the second device 20, b) providing 302 a time stamp for the first data DAT1, c) enabling 303 the use of a WPAN (Wireless Personal Area Network) technology for the transmission 104, 104a, for example using a BLE (Bluetooth Low Energy) technology, for example a BLE Connected Mode, d) transmitting 304 sensor data SD ( Fig. 2) relating to the tire pressure monitoring, together with linked time information P1, P2, e) performing 305 a, for example, automatic, learning procedure, for example a self-learning procedure, for assigning specific tire pressure values ​​associated with a vehicle 30, for example as detected by at least one sensor device 10a, 10b ( Fig. 11) to a corresponding tire or wheel of the vehicle 30.

[0078] Further exemplary embodiments, Fig. 11, refer to a vehicle 30 comprising at least one first device 10, 10a, 10b and / or at least one second device 20 according to the embodiments.

[0079] Further exemplary aspects and embodiments are disclosed below, which in some embodiments may be combined either individually or in combination with at least one of the aspects and embodiments discussed above.

[0080] In some embodiments, Fig. 12, for example, when a connection is established e1, the connection event counter CEC of the first device, for example the sensor device 10, and the connection event counter CEC' of the second device 20, which may form a gateway, for example, are initialized, for example with the value 0.

[0081] In some embodiments, without loss of generality, it is assumed that the sensor device 10 is configured as a peripheral device in the sense of the above-mentioned Bluetooth Core Specification, version 5.4, and that the gateway 20 is configured as a central device in the sense of the above-mentioned Bluetooth Core Specification, version 5.4.

[0082] In some embodiments, for example at the beginning of a connection event, the central unit 20 sends data (for example the second data DAT2), for example a data packet, or an empty packet (for example without (user) data, for example payload data) to the peripheral device 10, wherein the peripheral device 10 can respond thereto, for example either by sending data or an empty packet to the central unit 20. In some embodiments, as already mentioned above, the connection event counter CEC, CEC' is incremented both in the peripheral device 10 and in the central unit 20 (for example regardless of whether data, for example payload data, is actually exchanged or not).

[0083] In some embodiments, for example when the peripheral device 10 actually receives a data packet, for example in the form of the second data DAT2, from the central unit 20, the peripheral device 10 synchronizes itself with the central unit 20, for example with an internal clock of the central unit 20, which can determine, for example, the connection interval e3 ( Fig. 12) and can trigger data transmissions to the peripheral device 10 based on the connection interval e3. Thus, in some embodiments, an internal clock of the central unit 20 is used to determine the connection interval e3, and by evaluating, e.g., counting, the connection elements, the peripheral device can synchronize with this internal clock of the central unit 20.

[0084] In some embodiments, a BLE link layer (LL) (which in some embodiments may be implemented, for example, in the transceiver 14, 204, see Fig. 2) report a current value of the connection event counter CEC, for example to a sensor software PRG, for example of the peripheral device 10, which is configured to process the first data DAT1. In some embodiments, the reporting of the current value of the connection event counter CEC can be performed during a resynchronization, see, for example, the dashed vertical lines of Fig. 12, which are numbered from 0x001 to 0x2EE. For example, the element T1 in Fig. 12 a point in time linked to a synchronization or resynchronization.

[0085] In some embodiments, for example, in order to be able to detect a remaining time difference t_synch, Δt, the timer TIM ( Fig. 2) is started, which is used to measure the time difference between T1, RPT.

[0086] In some embodiments, a timestamp for the first data DAT1 can be determined, for example encoded, as follows: Payload_data_1 = conn_event_cnt_synch (for example, the value of the connection event counter CEC at time T1 of synchronization), Payload_data_2 = t_synch (for example, the time difference between T1, RPT), wherein the first parameter P1 to be sent to the central unit 20 can comprise or characterize the Payload_data_2, and wherein the second parameter P2 to be sent to the central unit 20 can comprise or characterize the Payload_data_1. Furthermore, the first data DAT1 can be sent to the central unit 20, for example together (e.g., within the same data packet as) the parameters P1, P2.

[0087] In some embodiments, for example to limit a value range associated with the time difference, it is proposed to add a quotient t_synch / e3 from the time difference t_synch and the connection interval e3 to the value conn_event_cnt_synch contained in the element Payload_data_1, and for example to encode only a remainder Δt of the time difference t_synch using the element Payload_data_2, for example according to: Payload_data_1=conn_event_cnt_synch + max{m∈ℤ|m <tsynch / (connectioninterval)}Payload_data_2=Δt= tsynch mod{Connectioninterval}

[0088] In some embodiments, the above-mentioned payload data elements, for example in the form of the parameters P1, P2, for example together with the first data DAT1, can be sent to the central unit 20.

[0089] In some embodiments, it is not relevant when such a transmission of the parameters P1, P2 is carried out, for example together with the first data DAT1, since in some embodiments the central unit 20 can reconstruct the time RPT at any time, for example with the aid of its own connection event counter CEC'.

[0090] In some embodiments, e.g., when the connection event counter CEC' is not accessible in the central unit 20 (e.g., due to a specific implementation of the BLE receiver 204), a timer (not shown) in the central unit 20 may be used to determine the time that has elapsed, e.g., since the connection between the devices 10, 20 was established.

[0091] In some embodiments, a current value of the connection event counter can be determined, for example, generated mathematically, for example in software of the central unit 20, for example by dividing a value characterized by the element Payload_data_1 by the value of the connection interval e3. In some embodiments, this can be facilitated by using a system clock of the central unit 20 as a reference for a common time base for both devices 10, 20. In some embodiments, this can make it possible to reduce the requirements for the BLE / central unit software interface, for example, by eliminating the need to provide the counter for current connection events in the gateway.

[0092] In some embodiments, a pre-calculation of the time since the connection was established (see element e1 in Fig. 12) within the peripheral device 10, for example, by multiplying the value of the connection event counter CEC by the connection interval e3. In some embodiments, it is conceivable that the value of Δt ( Fig. 12) is included in this preliminary calculation. QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited non-patent literature

[0000] Bluetooth Core Specification, Version 5.4, Version Date 2023-01-31 [0013, 0053] Bluetooth Core Specification, Version 5.4, Volume 1, Part A, Chapter 4.2.2.6 (page 263 [0013, 0053] Volume 5, Part B, Chapter 4.5.1

[0014] Volume 6, Part B, Chapter 4.5.1 [0015, 0056, 0057] Adopt Bluetooth Core Specification, Version 5.4,

[0054] Volume 6, Part B, Chapter 1.1 (page 2674 [0054, 0055]

Claims

[1] A method for data processing, comprising: determining (102) on a first device (10) a first parameter (P1) characterizing a time difference between a previous synchronization (SYNC) of the first device (10) with a second device (20) and a reference time (RPT) linked to first data (DAT1) processed by the first device (10), sending (104) the first parameter (P1) and a second parameter (P2) characterizing a time linked to the previous synchronization (SYNC) by the first device (10) to the second device (20). [2] The method of claim 1, wherein the transmitting (104) comprises transmitting (104a) the first data (DAT1). [3] Method according to at least one of the preceding claims, comprising: receiving (110), for example repeatedly receiving (110a), for example periodically receiving (110b), second data (DAT2) from the second device (20), and synchronizing (100; 112) with the second device (20) based on the second data (DAT2). [4] The method of at least one of the preceding claims, comprising: providing (120) a connection event counter (CEC) for counting (122) a number (NUM-CE) of connection events associated with the second device (20), and optionally counting (122) the number (NUM-CE) of connection events associated with the second device (20) using the connection event counter (CEC). [5] Method according to at least one of the preceding claims, comprising: providing (130) a timer (TIM) for determining (132) the time difference (t_synch, Δt) between the previous synchronization (SYNC) of the first device (10) with the second device (20) and the reference time (RPT), and optionally determining (132) the time difference (t_synch, Δt) between the previous synchronization (SYNC) of the first device (10) with the second device (20) and the reference time (RPT) using the timer (TIM). [6] Method according to claim 5, comprising: receiving (135), for example repeatedly receiving (135a), for example periodically receiving (135b), second data (DAT2) or the second data (DAT2) from the second device (20), starting (137), for example restarting (137a), the timer (TIM) upon receipt (135; 135a; 135b) of the second data (DAT2), and optionally stopping (139) the timer (TIM) when the first data (DAT1) is available, for example at the reference time (RPT). [7] Method according to at least one of claims 5 to 6, comprising: determining (140) the first parameter (P1) using the timer (TIM), for example using (140a) a timer value (VAL-TIM) of the timer (TIM) as the first parameter (P1). [8] Method according to at least one of claims 4 to 7, comprising: determining (142) the second parameter (P2) using the connection event counter (CEC), for example using (142a) the number (NUM-CE) of connection events associated with the second device (20) as the second parameter (P2). [9] Method according to at least one of the preceding claims, comprising at least one of: a) using (150) a wireless data exchange (WDX) for the transmission (104; 104a), for example using (150a) a WPAN technology (Wireless Personal Area Network) for the transmission (104; 104a), for example using (150b) a BLE technology (Bluetooth Low Energy) for the transmission (104; 104a), b) using (152) one or the wireless data exchange (WDX) for the reception (110; 110a; 110b), for example using (152a) a WPAN technology (Wireless Personal Area Network) for the reception (110; 110a; 110b), for example using (152b) a BLE technology (Bluetooth Low Energy) for the reception (110; 110a; 110b). [10] Method according to at least one of the preceding claims, wherein the first data (DAT1) are linked to and / or characterize at least one of the following elements: a) sensor data (SD) from at least one sensor (12), b) sensor data (SD-V) linked to at least one vehicle, for example a passenger car (30), c) pressure data (PD) characterizing, for example, a tire pressure of a vehicle (30), d) temperature data (TD) characterizing, for example, a temperature associated with a tire of a vehicle (30), e) acceleration data characterizing, for example, an acceleration of a component attached, for example, to a tire of a vehicle, and / or data derived from the acceleration, such as an angular position, for example linked to a specific point in time, and / or a time difference since reaching or passing a predetermined angular position,and / or a period of a wheel revolution, and / or an angular velocity of a wheel, and / or an orbital speed of a wheel or part of a wheel, and / or a parameter derived from a rotation of a wheel., [11] A method for processing data provided by a first device (10), comprising: receiving (180) a first parameter (P1) from the first device (10) at a second device (20) that characterizes a time difference between a previous synchronization (SYNC) of the first device (10) with the second device (20) and a reference time (RPT) associated with the first data (DAT1) processed by the first device (10), and a second parameter (P2) that characterizes a time associated with the previous synchronization (SYNC) and optionally the first data (DAT1), and optionally processing (182) at least one of the first parameter (P1) and / or the second parameter (P2) and / or the first data (DAT1). [12] Device (200; 200a) for carrying out the method according to at least one of the preceding claims. [13] Sensor device (10; 10a, 10b) comprising at least one device (200; 200a) according to claim 12. [14] Tire pressure monitoring system (1000) for a vehicle (30), comprising at least one of the following elements: a) a device (200; 200a) according to claim 12, b) a sensor device (10; 10a, 10b) according to claim 13. [15] Use (300) of the method according to one of claims 1 to 11 and / or the device (200; 200a) according to claim 12 and / or the sensor device (10; 10a, 10b) according to claim 13 and / or the tire pressure monitoring system (1000) according to claim 14 for at least one of: a) sending (301) data, for example the first data (DAT1), with a time reference to the second device (20), b) providing (302) a time stamp for the first data (DAT1), c) enabling (303) the use of a WPAN technology (Wireless Personal Area Network) for the sending (104;104a), for example using (150b) a BLE (Bluetooth Low Energy) technology, d) sending (304) sensor data relating to the tire pressure monitoring together with associated time information, e) performing (305) a, for example automatic, learning procedure, for example a self-learning procedure, to assign specific tire pressure values ​​associated with a vehicle (30) to a corresponding tire of the vehicle (30);

Images