Improvements in or relating to storage of accelerometer data
By receiving and comparing parameter values in the vehicle sensor, storing new values or differences only when the difference exceeds the threshold, and recording data time with the timestamp, the problem of large capacity occupancy when storing accelerometer data in the vehicle is solved, and the implementation of the Complete capture and efficient storage of signals 2 seconds before the event.
Patent Information
- Application Number
- CN202080008104.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-02-07
- Filing Date
- 2020-01-14
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-01-14
AI Technical Summary
When storing accelerometer data in a vehicle, it is necessary to always maintain sensor data for 2 seconds, resulting in a large memory capacity occupancy, and the signals generated before the event cannot be captured, and the complete event reconstruction cannot be provided.
By receiving and comparing parameter values in the vehicle sensor, the new value or difference value is stored only when the difference exceeds the threshold, the counter records the number of consecutive same values, and realizes efficient storage of data, reduces the storage amount, and record data time with time stamps. .
It effectively reduces the amount of data required to store, realizes efficient storage of vehicle sensor data and complete capture of signals in the first 2 seconds of events, and improves storage efficiency and event reconstruction capabilities.
Smart Images

Figure CN113272658B_ABST
Abstract
Description
[0001] The present invention relates to storage of accelerometer data in a vehicle, and in particular to efficiently storing accelerometer data.
[0002] Many modern vehicles include sensors, such as accelerometers. After an event, such as a collision, it is often useful to be able to view the signals provided by these sensors before, during, and after the event so that certain aspects of the event can be reconstructed. This can allow, for example, determinations as to whether a safety system, such as an airbag, was activated based on signals from the vehicle's sensors, was triggered correctly or at the right time.
[0003] To this end, some vehicles will begin recording signals generated by certain vehicle sensors once it is determined that an event such as a collision is occurring. However, signals recorded in this manner will not provide a complete picture, as signals generated before the event begins to occur will not be captured.
[0004] Therefore, it has been proposed to always keep a record of the signal generated by the sensor in a memory for a certain period of time immediately before the current moment. This period of time may be, for example, 2 seconds. When an event such as a collision occurs, this data may be retained, and the signal from the sensor may also be recorded as the event continues. Therefore, using this technique, after an event, the researcher should be able to retrieve a record of the sensor signal throughout the event starting from 2 seconds before the event began.
[0005] While this technique is advantageous, it does require that the vehicle include memory in which 2 seconds of sensor data is always retained (ie, at any given moment, data relating to the previous 2 seconds). This can be a relatively large amount of data.
[0006] The present invention seeks to provide such an improved system.
[0007] Therefore, one aspect of the present invention provides a method for storing data related to vehicle parameters, wherein the data is provided by a vehicle sensor, the method comprising the following steps: receiving a series of first values and second values from the vehicle sensor at a certain time interval, wherein each first value represents a parameter sensed by the vehicle sensor and each second value relates to a function of the vehicle sensor; for each new first value received: (a) comparing the new first value with the previous first value received; (b) if the difference between the new first value and the previous first value is below a difference threshold, storing the difference in a memory; or (c) if the difference between the new first value and the previous first value is above a difference threshold, storing the difference in a memory. if the difference threshold is less than the new first value, the new first value is stored in the memory, thereby maintaining a counter to record the number of consecutive second values with the same value that have been received; and for each new second value received: (a) the new second value is compared with the previous second value received; (b) if the new second value is the same as the previous second value, the counter is incremented; or (c) if the new second value is different from the previous second value, the previous second value is recorded in the memory together with the current counter value, and then the counter is reset; and (d) if the counter has reached the counter threshold, the new second value is recorded in the memory together with the counter threshold, and the counter is reset.
[0008] Advantageously, the step of storing the difference between the new first value and the previous first value comprises storing a data word having a first length; the step of storing the new first value comprises storing a data word having a second length; and the first length is smaller than the second length.
[0009] Preferably, the step of storing a new first value comprises storing a data word comprising one or more bits indicating that the data word comprises the first value.
[0010] Conveniently, the step of storing the difference between the new first value and the previous first value comprises storing a data word comprising one or more bits indicating that the data word comprises the difference between two consecutive first values.
[0011] Advantageously, one or more bits comprise a header which occurs at the beginning of a data word.
[0012] Preferably, the one or more bits comprise a single bit.
[0013] Conveniently, the method further comprises the step of recording time stamp data indicating the time at which the data relating to the vehicle parameter was stored.
[0014] Advantageously, the method further comprises the step of recording separate time stamp data in conjunction with the first value and in conjunction with the second value.
[0015] Preferably, the method further comprises the steps of recording timestamp data at periodic intervals in conjunction with a second value; and if the counter is in the process of incrementing after an interval since recording a previous timestamp data, waiting until data relating to the second value is recorded, and then recording the timestamp data in conjunction with the second value.
[0016] Conveniently, the method comprises the steps of: receiving a data packet comprising a new first value and a new second value from a vehicle sensor; and separating the new first value and the new second value.
[0017] Advantageously, recording the previous second value together with the current counter value in the memory comprises storing a data word comprising the previous second value and the current counter value in the memory; and wherein recording the new second value together with the counter threshold in the memory comprises storing a data word comprising the new second value and the counter threshold in the memory.
[0018] Another aspect of the present invention provides a method comprising: recording a first value and a second value in a memory of a vehicle according to any of the above items to store the first value and the second value relating to a set time period immediately before a current moment, and overwriting the first value and the second value relating to a time exceeding the set time period before the current moment.
[0019] Another aspect of the present invention provides a computer program product comprising computer program code, which, when run on a computer, is operable to cause the computer to perform all of any of the above steps.
[0020] Another aspect of the present invention provides a computer readable medium storing the computer program code according to the above.
[0021] Another aspect of the present invention provides a vehicle having a vehicle sensor, which, when in use, generates a series of first values and second values from the vehicle sensor, wherein each first value represents a parameter sensed by the vehicle sensor and each second value relates to a function of the vehicle sensor, wherein the first values and the second values are transmitted from the vehicle sensor to a vehicle processor and stored in a memory of the vehicle according to any of the above items.
[0022] Advantageously, the series of first and second values comprises a series of linked first and second values, wherein within each linked first and second value, the first value represents a parameter sensed by a vehicle sensor and the second value relates to the function of the vehicle sensor in sensing the parameter to generate the first value.
[0023] Preferably the sensor is an accelerometer, and preferably wherein the vehicle comprises a plurality of sensors, wherein data from each of the sensors is stored in the memory according to any of the above.
[0024] In order that the present invention may be more easily understood, embodiments of the present invention will now be described with reference to the accompanying drawings, in which:
[0025] Figure 1 shows a graph of acceleration and data validity versus time;
[0026] Figure 2 Shows Figure 1 the acceleration of the data shown and the change in data validity with respect to time;
[0027] Figures 3 to 7 shows the stages in the encoding of acceleration data;
[0028] Figures 8 to 14 shows stages in the decoding of acceleration data; and
[0029] Figures 15 to 23 Stages in the encoding of validity data are shown.
[0030] Modern vehicles may include an accelerometer that generates an acceleration value and a validity flag every 250 μs.
[0031] The acceleration value may typically take the form of a 10-bit signed word having a range between -512 and +511.
[0032] The validity flag can be a single bit, either 0 or 1. The validity flag indicates whether the data provided by the sensor is reliable, e.g., the sensor has not been disconnected, as can sometimes happen during a crash. If an acceleration value is accompanied by a validity flag value indicating that the data is reliable, then the researcher will use or consider that acceleration value. However, if an acceleration value is accompanied by a validity flag value indicating that the data is unreliable, then the researcher will not use or consider that acceleration value. The researcher may apply a backup strategy, such as considering signals generated by other sensors at the same time.
[0033] If there are eight such sensors in a vehicle, the minimum required bandwidth is
[0034] 8×(10+1)bits / (250μs)=352kbit / s=44ko / s
[0035] As described above, if the data from all sensors is maintained for a period of 2 seconds, the memory (such as RAM) required to store this information is 88ko.
[0036] The skilled reader will appreciate that RAM is relatively expensive, and this therefore represents an expensive parameter when selecting a microcontroller for a vehicle.
[0037] Embodiments of the present invention may reduce the amount of storage required to maintain this data.
[0038] The inventors have noticed that, under normal circumstances, acceleration values do not usually change rapidly. Furthermore, the validity flag will usually be "true" or "false" for a fairly long sequence of samples and will not alternate between consecutive samples.
[0039] Therefore, rather than storing the value received at each sampling time, storing the difference between the current sample and the previous sample (or data representing the difference) can reduce the amount of data to be stored.
[0040] Figure 1 is a schematic diagram of acceleration 1 that can be sensed by an accelerometer during a collision event with respect to time. In this figure, acceleration 1 has a value close to zero during most of the time represented, but has a significantly higher value during a portion of time (indicated by reference numeral 5) when the impact event occurs.
[0041] Figure 1 Also shown on the same time scale is the value 2 of the validity flag relating to this sensor. Figure 1 As can be seen in FIG, the validity flag takes only two values, namely, a relatively high value of 3 (indicating a "true" signal, or an indication that the data from the sensor is reliable) and a relatively low value of 4 (indicating a "false" signal, or an indication that the data from the sensor is unreliable).
[0042] Figure 2 A graph is shown comprising a line 6 showing the difference in acceleration at each plotted point compared to the previous plotted point.
[0043] It can be seen that outside the region representing the shock event, the line 6 varies relatively little and lies almost entirely between the values -4 and +3.
[0044] Figure 2 Also included is a line 7 which shows the difference in the value of the validity mark at each plotted point compared to the previous plotted point. In the scale of the graph, the value occupied by this line 7 over a large part of the graph corresponds to zero.
[0045] It can be seen that the line 7 is almost constant.
[0046] A scheme for encoding the data according to an embodiment of the present invention is described below.
[0047] For acceleration values, if the difference between the value of a sample and the value of the previous sample is below a predetermined threshold, the difference value itself is stored for that sample. In a preferred embodiment, the data is stored together with a header indicating that the following value is a difference value (or delta value).
[0048] Alternatively, if the difference between the value of a sample and the value of the previous sample is above a predetermined threshold, the value of the sensed acceleration is stored for that sample.In a preferred embodiment, the data is stored with a header indicating that the following value is a direct sensor value (rather than a delta value).
[0049] exist Figure 1 and Figure 2 In the data example shown, storing the data in this way would require 2228 bits for the delta value and 484 bits for the sensed value, so a total of 2712 bits would be required.
[0050] In contrast, if all direct sensor values had been stored (which is the case for conventional systems), 6010 bits would be required. Thus, the above scheme allows for an acceleration value storage efficiency of 221% or a compression ratio of 2.2.
[0051] For the value of the validity mark, when the validity mark changes value, it is recommended to store the date of recording the number of samples, just before this date, the validity mark maintains the same value. In a preferred embodiment, a count of the number of samples that the validity mark maintains the same value is maintained. If the validity mark maintains the same value for a predetermined number of samples, an entry is stored in the memory to record this, and the count is restarted. For example, if the validity mark maintains the same value for 127 samples, an entry recording this can be stored in the memory.
[0052] See again Figure 1 For the data shown, this technique may require 3×8 bits to store the initial long unchanged portion of the data, 8 bits to store the negative pulse, and another 8 bits to store the last portion of the data after the negative pulse. This means that a total of 40 bits are required. In contrast, if a validity flag had been recorded for each sample in a conventional manner, this would require 601 bits. In this example, for the validity flag, the technique therefore allows a storage efficiency of 1502% or a compression ratio of 15.
[0053] In conjunction with the figures given above for both the acceleration value and the validity flag, a total of 2752 bits are required using the scheme according to the invention, compared to a total of 6611 bits required using the conventional method. This therefore allows an overall storage efficiency of 240% or a compression ratio of 2.4.
[0054] Figures 3 to 23 A representation of data storage using this technique is shown.
[0055] First, refer to the acceleration. Figure 3 It is shown that in a particular sample a value of 5 is received. The previous acceleration value was 0, so this results in a delta value of 5. This is below the threshold, so (as described above) the delta value will be stored. Figure 3The data 10 stored in the memory 11 is shown to include a header bit 12 indicating that the following data is a delta value. In this example, a header value of 0 is used to indicate that the following data is a delta value, but any other suitable scheme may be used. The data 10 stored in the memory 11 also includes 4 bits 13 for encoding the delta value itself.
[0056] Go to Figure 4 , in the next sample a new value of 8 is received. The difference between this sample and the previous value is 3, which is again below the threshold, so the difference is stored as the delta value. Figure 4 Again, the data 10 to be stored in the memory 11 is shown to include a header bit 12 (which is again 0) and four bits 13 for encoding a delta value. Figure 4 In FIG. 1 , it can be seen that two Δ values are now stored in the memory 11 .
[0057] Figure 5 A new sample is shown being received having a value of 1. The new difference value is -7, which is again stored in the memory 11 as a header bit 12 and four data bits 13.
[0058] Figure 6 shows that a new sample is received, which has a value of -200. Therefore, the difference is -201, which is above the threshold. Therefore, this sample is not stored as a delta value, but rather as a direct sensor value. As in Figure 6 As can be seen in FIG. 1 , the data 14 to be stored in the memory 11 includes a header bit 15 indicating that the following data is a direct sensor value (in this example, header bit 1 is used to indicate that the following data is a direct sensor value). The data 14 to be stored in the memory 11 also includes 10 data bits 16 for encoding the direct sensor value itself. As described above, this data 14 is stored in the memory 11 together with the previously stored data.
[0059] refer to Figure 7 , in the next sample, the acceleration value is -195. Therefore, the difference between this sample and the previous sample is 5, which is below the threshold and is stored as a delta value with a single header bit 12 and four data bits 13.
[0060] Figure 8 There is shown data which has been stored in the memory 11. One possible process for decompressing this data to recover the original information will now be shown.
[0061] As in Fig. 9 As can be seen in FIG. 1 , the first bit 17 of the stored information is analyzed. Since the first bit 17 is 0, this indicates that the following four bits will be data representing the data value. Reading the next four bits 18, as Fig.10Since the previous value of the acceleration is known to be zero, it can be determined that the new value 38 (encoded by these five bits 17, 18) is 5.
[0062] exist Fig.11 , the next bit 19 is read, and again this is zero, indicating that the next four bits 20 will encode a delta value. These four bits 20 are read, allowing the delta value encoded by these bits 20 to be determined to be 3. This is added to the previous sample value (i.e., 5) to give a new value 39 which is 8.
[0063] exist Fig.12 , the next bit 21 is read again. This is zero, indicating that the next four bits 22 will encode a delta value. These four bits 22 are read and their value is added to the previous sample, allowing the value 40 encoded by these next five bits 21, 22 to be determined to be 1.
[0064] exist Fig.13 , the next single bit 23 is read. This bit 23 is 1, indicating that the next ten bits 24 will encode the sensed value of acceleration. These next ten bits 24 are then read to determine that the new sample 41 has a value of -200 (since this is a direct sensor value, the previous sample value is not considered here).
[0065] Finally, reference Fig.14 , the next single bit 25 is read and found to have a value of 0. This indicates that the following four bits 26 will encode a delta value. These bits 26 are read and the delta value 5 thus encoded is added to the previous sample value -200 to obtain a new sample value 42 which is -195.
[0066] A skilled reader will readily understand how this scheme can recover the original sample values from the compressed data in a straightforward manner.
[0067] The storage of validity flag values will now be described.
[0068] Fig.15 and subsequent figures include graphs schematically illustrating effectiveness data (left hand side), and representations of data recorded into a memory (right hand side).
[0069] First reference Fig.15 , a first validity flag value 27 of 1 is received. A counter 28 records the number of samples for which the validity flag value remains the same. At this stage, the counter 28 has a value of 1 (ie this is the first value to be received).
[0070] Go to Fig.16 , a second validity flag value 29 is received. Again, this is 1, so the counter 28 is incremented by 1 to 2. Similarly, Fig.17As shown, the next validity flag value 30 is 1, and the counter 28 is incremented by 1 to 3.
[0071] Subsequent validity flag values are received, each also having a value of 1, until 127 consecutive validity flag values are 1. The resulting situation is Fig.18 , where the counter 28 has been incremented to 127. At this stage, as described above, the counter value (127) is recorded in the memory 31 together with the flag value 34 representing the value of the validity flag during these increments of the counter. Fig.18 As can be seen in FIG. 4 , this storage of data is represented by the first row 43 in the memory 31 , which first row includes the flag value 34 and the counter value, representing the fact that the validity flag remained at 1 for 127 samples.
[0072] When the next validity flag value, which is again 1, is received, the counter 28 is incremented to 1. Another validity flag value 32 of 1 causes the counter 28 to be incremented to 2. Fig.19 shown.
[0073] Go to Fig. 20 , the next validity flag value 33 is 0, i.e., the value of the validity flag has changed since the previous sample. The existing value of the counter 28 (i.e., 2) is stored in the memory together with the flag value 35 (i.e., 1) corresponding to the counter value. This Fig. 20 4 is represented by the second row 44 in the memory 31. The counter 28 is reset and incremented to 1.
[0074] like Fig.21 As shown, 49 additional consecutive samples are received, each with a validity flag value of 0. Therefore, counter 28 is incremented to 50. At the next sample (by Fig. 22 ), the validity counter has the value 1, i.e. different from the value in the previous sample, so the counter value 50 is stored in the memory 31 together with the flag value 36 of 0, indicating the fact that the validity flags of 50 consecutive samples are 0. The counter 28 is reset and incremented to 1.
[0075] like Fig.23 As shown, the next (and final) sample value provides a validity flag value of 1, and the counter 28 is incremented to 2. Because this is the end of the data, the counter value of 2 is stored in the memory 31 along with the flag value 37 of 1 as the final row 46, indicating that the validity flag has a value of 1 for 2 separate samples.
[0076] The skilled reader will appreciate that decompression of this data will be straightforward. To reconstruct the original data represented by each row stored in memory, the tag value in that row is repeated a number of times corresponding to the counter value in that row. For example, the first row 43 has a tag value 34 of 1 and a counter value of 127. Thus, this first row 43 represents 127 consecutive values of 1.
[0077] In this example, the decompression of the remaining rows will be clear to the skilled reader.
[0078] In the discussion above, if the tag value remains the same for 127 consecutive samples, it is recorded in the memory and the counter is reset. However, larger or smaller thresholds may be used. In the example given above, a new value is received every 250 μs, so 127 samples will be received in about 0.03s. Therefore, a new "row" in the memory will be recorded every 0.03s or longer (depending on whether the tag value changes during the time considered). In this example, the goal is to always record 2 seconds of activity in the vehicle's memory, and accordingly, the system may also use a higher threshold count value to record entries in the memory less frequently, thereby achieving greater compression while still reliably recording relevant activity in the vehicle's memory.
[0079] It is expected that the validity flag value will change relatively rarely. In practice, the validity flag may have three values: "unavailable" (when no data is received from the sensor), "valid" (when the sensor is working correctly), and "failed" (when the sensor is not considered to be working correctly), and therefore the signal from the sensor will not be trusted (or the signal will undergo further analysis before it is considered trustworthy).
[0080] In a preferred approach, when the vehicle's electronic control unit (ECU) is turned on, the flag will have the value "unavailable" until it starts receiving signals from the sensor, at which point the value will change to "valid" or "failed" and cannot revert back to "unavailable". Therefore, there will be no switching of the value involving the "unavailable" state.
[0081] It is expected that the value will be "valid" for most (or indeed almost all) of the time that the sensor is in use. If the value changes to "failed", it may take a relatively long time (from at least hundreds of microseconds to several seconds) to change back to "valid". Therefore, it is not expected that there will be any rapid switching between the "valid" state and the "failed" state.
[0082] In view of this, it is expected that the writing of validity flag values according to the present invention will achieve a high degree of compression.
[0083] In use of a system embodying the invention, signals are received and compressed from one or more vehicle sensors (particularly accelerometers) using a method embodying the invention and stored in a memory of the vehicle as described above. The system will need to store data representing a certain time period, e.g., 2s, immediately before the current moment (at any time). Data corresponding to a time more than 2 seconds in the past will preferably be deleted and will more preferably be overwritten by new data representing more recent sensor readings.
[0084] It is contemplated that when compressed data is written to memory in embodiments of the present invention, timestamp information is also periodically written to memory in conjunction with the compressed sensor value to indicate the time at which the sensor value was obtained. If a researcher analyzes the data, for example after a collision, this timestamp information will allow the accelerometer data and validity marker data to be assigned the correct time values and also correlated with each other so that the researcher can fully reconstruct the compressed signal at a later stage.
[0085] A skilled reader will appreciate that a timestamp may include a header indicating the time at which the information that follows indicates the time, followed by a string of numbers encoding the time.
[0086] It is preferred to include as few timestamps as possible to minimize the total amount of data that needs to be encoded.
[0087] In one example, the timestamp information can be written to the memory at periodic intervals (such as every 1 second or every 2 seconds) so that every 2 second window contains at least one timestamp. The data in the memory can then be decompressed and analyzed based on the time given by the timestamp. These time periods are only examples, and timestamp information can be included at any suitable interval.
[0088] In a preferred embodiment, the timestamp information is written to the memory in a manner that interferes with data compression as little as possible.
[0089] For accelerometer data, each time a signal is received from the accelerometer (either a difference value or a new direct sensor value), a new value is written to the memory, so timestamp information may be included between any two values written to the memory. The timestamp information may be written at periodic time intervals, or after a specific number of values written to the memory (or following any other suitable scheme).
[0090] However, for the validity flag, data may be written to the memory only when the state of the validity flag changes or when a count limit is reached. If a timestamp is written to the memory while the state of the validity flag is constant and in the process of counting, this will interfere with the effective encoding of the data into the memory. Therefore, for the validity flag, the system may attempt to write a timestamp to the memory at certain intervals (for example, after a certain length of time since the last data stamp, or after a certain amount of data values have been written since the last data stamp). If the system is in the process of performing a count of the same validity flag value, the system will wait until the validity flag data is written to the memory (because the validity flag value changed, or because the count limit was reached). The timestamp is then written to the memory after the validity flag data is written.
[0091] When the data is decompressed, such as after a collision, the acceleration data and the validity marker data are each converted into a series of continuous data values, i.e., reconstructing the compressed original data. By utilizing the timestamps included in the data sequence, each of the data values can be associated with a time when the data value was initially generated or received.
[0092] Once this is done, pairs of acceleration data values and validity flag data values that were initially generated or received at the same time (or substantially the same time) may be linked together to obtain a complete set of acceleration data values accompanied by corresponding validity flag values.
[0093] It is anticipated that data will be written to one or more memories, and the data controller will identify data older than a preset threshold (as discussed herein, this threshold may be 2s) to be deleted and / or overwritten by newer data. This preferably occurs "rolling", i.e., older data sensor data in one area of memory is continuously overwritten by newer sensor data.
[0094] In a preferred embodiment, in normal operation, an area of memory is set aside for storing sensor data (i.e., a rolling window of data is stored when the vehicle is not involved and does not appear likely to be involved in a collision.) If the signals from the sensors are changing rapidly, the size of the set aside memory area can be calculated based on a conservative estimate of how much memory will be needed to hold 2s of data.
[0095] Thus, during normal driving of the vehicle, a rolling 2s window of data from the accelerometer is continuously stored in a compact and efficient manner.
[0096] When it is determined that the vehicle is involved in an accident or collision situation (or that the vehicle may be involved in such a situation, or may enter such a situation), the data from the accelerometer is still recorded in the memory using the type of compression techniques described above. However, the data is no longer deleted from the memory, and the new data is recorded in the memory to add to all existing data already stored in the memory. In this way, once the collision is over, the vehicle's memory can store accelerometer data from 2 seconds before the time when the collision was determined to have occurred, during the collision, and until after the collision is over. This should provide researchers with all relevant data to analyze the collision event.
[0097] In a preferred embodiment, if it is determined that the vehicle may be involved in or may enter a collision situation, accelerometer data may be recorded and any existing data may not be deleted. However, if the vehicle is ultimately not involved in a collision, older data may be deleted and the system may return to normal operation of its rolling window of stored data. For example, when a collision situation is determined to be likely, the vehicle's processor may provide a signal or change a flag value. When in this situation, the stored accelerometer data may not be deleted. When the signal changes or the flag value returns to normal, the older data is deleted. As an alternative, a certain length of time (e.g., 30 seconds) after the signal that a collision event may occur is first received, if a collision event has not occurred, the system may assume that a collision event has not occurred and return to normal operation.
[0098] The above techniques provide an efficient and effective way to compress related data streams, one of which represents a "floating" variable that can take any value within a relatively wide range, and one of which can take only a more limited range of values, specifically a flag or true / false indicator that can take only one of two different values. The invention is particularly suitable for encoding and storing data generated by one or more accelerometers on a vehicle, resulting in an acceleration value and a corresponding value indicating whether the acceleration value is considered valid.
[0099] However, data from sources other than accelerometers can also be encoded. Examples of other data that can be efficiently encoded in this way include:
[0100] Data indicating the angle of rotation of the steering wheel or the amount by which the vehicle pedal is depressed, together with a corresponding verification mark;
[0101] Data encoding the forward speed of the vehicle, together with a corresponding verification mark; or
[0102] Data representing the rotational rate of the vehicle engine drive shaft or vehicle wheels, together with a corresponding verification mark.
[0103] When used in this specification and claims, the terms "comprises" and "comprising" and variations thereof mean including the specified features, steps or integers. The terms should not be interpreted as excluding the presence of other features, steps or components.
[0104] The features disclosed in the preceding description or in the subsequent claims or in the drawings, expressed in their specific form or in the form of a means for performing the disclosed function or a method or process for obtaining the disclosed result, may be used alone or in any combination of such features to realize the invention in its various forms, as the case may be.
Claims
1. A method for storing data relating to vehicle parameters, wherein the data is provided by vehicle sensors, the method comprising the following steps: receiving a series of first values and second values from the vehicle sensor at time intervals, wherein each first value represents a parameter sensed by the vehicle sensor and each second value relates to a validity flag of the vehicle sensor; For each new first value received: (a) comparing the new first value with the previous first value received; (b) if the difference between the new first value and the previous first value is below a difference threshold, storing the difference in a memory; or (c) if the difference between the new first value and the previous first value is above a difference threshold, storing the new first value in the memory, maintaining a counter that records the number of consecutive second values having the same value that have been received; as well as For each new second value received: (a) comparing the new second value with the previously received second value; (b) if the new second value is the same as the previous second value, incrementing the counter; or (c) if the new second value is different from the previous second value, recording the previous second value together with the current counter value in the memory, and then resetting the counter; as well as (d) if the counter has reached a counter threshold, recording the new second value together with the counter threshold in the memory and resetting the counter.
2. The method according to claim 1, wherein: The step of storing the difference between the new first value and the previous first value comprises storing a data word having a first length; The step of storing the new first value comprises storing a data word having a second length; and The first length is smaller than the second length. 3 . The method of claim 1 , wherein storing the new first value comprises storing a data word comprising one or more bits indicating that the data word comprises the first value.
4. The method of claim 1 , wherein the step of storing the difference between the new first value and the previous first value comprises storing a data word comprising one or more bits indicating that the data word comprises the difference between two consecutive first values.
5. A method according to claim 3 or 4, wherein the one or more bits comprise a header occurring at the beginning of the data word.
6. The method according to any one of claims 1 to 4, further comprising the step of recording time stamp data indicating the time at which the data relating to the parameter of the vehicle was stored.
7. The method according to any one of claims 1 to 4, further comprising the following steps: recording timestamp data at periodic intervals in conjunction with the second value; as well as If the counter is in the process of being incremented after an interval since the recording of the previous time stamp data, waiting until data relating to the second value is recorded is performed and then recording the time stamp data in conjunction with the second value.
8. The method according to any one of claims 1 to 4, comprising the following steps: receiving a data packet including the new first value and the new second value from the vehicle sensor; and separating the new first value and the new second value.
9. The method according to any one of claims 1 to 4, wherein: Recording the previous second value together with the current counter value in the memory comprises storing a data word comprising the previous second value and the current counter value in the memory; and wherein recording the new second value together with the counter threshold in the memory comprises storing a data word comprising the new second value and the counter threshold in the memory.
10. The method according to any one of claims 1 to 4, further comprising the step of recording separate time stamp data in conjunction with the first value and in conjunction with the second value.
11. A method comprising: A method according to any preceding claim recording first and second values in a memory of a vehicle to store first and second values relating to a set time period immediately before a current moment and to overwrite first and second values relating to a time exceeding the set time period before the current moment.
12. A computer program product comprising computer program code operable, when said code is run on a computer, to cause the computer to perform all of the steps of any preceding claim.
13. A computer readable medium storing the computer program code according to claim 12.
14. A vehicle having a vehicle sensor, the vehicle, in use, generating a series of first values and second values from the vehicle sensor, wherein each first value represents a parameter sensed by the vehicle sensor and each second value relates to a validity flag of the vehicle sensor, Wherein the first value and the second value are transmitted from the vehicle sensor to a vehicle processor and stored in a memory of the vehicle according to the method of any one of claims 1 to 11.
15. The vehicle of claim 14, wherein the series of first and second values comprises a linked series of first and second values, wherein: Within each linked first value and second value, the first value represents a parameter sensed by the vehicle sensor, and the second value relates to a validity flag in sensing the parameter to generate the first value.
16. A vehicle as claimed in claim 14 or 15, wherein the sensor is an accelerometer.
17. A vehicle according to claim 14 or 15, wherein the vehicle comprises a plurality of sensors, wherein according to the method of any one of claims 1 to 11, the data from each of the sensors is stored in the memory.
Citation Information
Patent Citations
Abnormality detection method for monitor object device, device for the same and machine readable recording medium for recording program
JP1999272508A
A sensor or its method of storing differences of sensed data into the different area of its storage
KR101058155B1
Systems and methods for variable-length encoding and decoding for enhancing computer systems
US20190020645A1
Traffic accident data recorder and traffic accident reproduction system
US5446659A
Vehicle sensor
WO2017029381A1
