Roll back of data delta updates
AssigneeAurora Labs Ltd.
InventorZohar Fox
Life of this patent
Estimating the term…
Abstract
Disclosed embodiments relate to adjusting vehicle Electronic Control Unit (ECU) software versions. Operations may include receiving a prompt to adjust an ECU of a vehicle from executing a first version of ECU software to a second version of ECU software; configuring, in response to the prompt and based on a delta file corresponding to the second version of ECU software, the second version of ECU software on the ECU in the vehicle for execution; and configuring, in response to the prompt, the first version of ECU software on the ECU in the vehicle to become non-executable.
Claims16
A non-transitory computer readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for adjusting vehicle Electronic Control Unit (ECU) software versions, comprising:
- receiving a prompt to adjust an ECU of a vehicle from executing a first version of ECU software to a second version of ECU software, wherein the first and second versions of ECU software are mapped to a plurality of functional units, and the ECU is configured to utilize a virtual file system (VFS) to manage and track one or more versions of each of the plurality of functional units;
- configuring, in response to the prompt and based on a multidimensional delta file corresponding to differences between dimensions of the first and second versions of ECU software and comprising position independent code, the second version of ECU software on the ECU in the vehicle for automatic execution, wherein:
- the multidimensional delta file includes code changes to segments of code on the ECU, and
- the multidimensional delta file comprises at least one of a binary data dimension, a source attribute dimension, and a map file dimension;
- and
- configuring, in response to the prompt, the first version of ECU software on the ECU in the vehicle to become non-executable, wherein configuring the first version of ECU software to become non-executable comprises:
- updating memory addresses in a single memory component of the ECU corresponding to one or more functional units managed by the VFS, wherein the single memory component in the ECU is configured to store both the first version of ECU software and the second version of ECU software.
A system for adjusting vehicle Electronic Control Unit (ECU) software versions, the system comprising:
- one or more processors;
- and
- one or more memories having instructions that, when executed by the one or more processors, cause the one or more processors to perform operations of:
- receiving a prompt to adjust an ECU of a vehicle from executing a first version of ECU software to a second version of ECU software, wherein the first and second versions of ECU software are mapped to a plurality of functional units, and the ECU is configured to utilize a virtual file system (VFS) to manage and track one or more versions of each of the plurality of functional units;
- configuring, in response to the prompt and based on a multidimensional delta file corresponding to differences between dimensions of the first and second versions of ECU software and comprising position-independent code, the second version of ECU software on the ECU in the vehicle for automatic execution, wherein:
- the multidimensional delta file includes code changes to segments of code on the ECU, and
- the multidimensional delta file comprises at least one of a binary data dimension, a source attribute dimension, and a map file dimension;
- and
- configuring, in response to the prompt, the first version of ECU software on the ECU in the vehicle to become non-executable, wherein configuring the first version of ECU software to become non-executable comprises:
- updating memory addresses in a single memory component of the ECU corresponding to one or more functional units managed by the VFS, wherein the single memory component in the ECU is configured to store both the first version of ECU software and the second version of ECU software.
A computer-implemented method for adjusting vehicle Electronic Control Unit (ECU) software versions, the method comprising:
- receiving a prompt to adjust an ECU of a vehicle from executing a first version of ECU software to a second version of ECU software, wherein the first and second versions of ECU software are mapped to a plurality of functional units, and the ECU is configured to utilize a virtual file system (VFS) to manage and track one or more versions of each of the plurality of functional units;
- configuring, in response to the prompt and based on a multidimensional delta file corresponding to differences between dimensions of the first and second versions of ECU software and comprising position-independent code, the second version of ECU software on the ECU in the vehicle for automatic execution, wherein:
- the multidimensional delta file includes code changes to segments of code on the ECU, and
- the multidimensional delta file comprises at least one of a binary data dimension, a source attribute dimension, and a map file dimension;
- and
- configuring, in response to the prompt, the first version of ECU software on the ECU in the vehicle to become non-executable, wherein configuring the first version of ECU software to become non-executable comprises:
- updating memory addresses in a single memory component of the ECU corresponding to one or more functional units managed by the VFS, wherein the single memory component in the ECU is configured to store both the first version of ECU software and the second version of ECU software.
Dependencies are inferred from the claim text.