System And Methods For Staging Data And Updating Vehicle Modules Using Staged Data

What is this patent about?

’159 is related to the field of updating software in vehicles, specifically addressing the challenge of reliably reprogramming onboard modules. Traditional methods involve directly writing data to modules via the OBD port , which can be risky if the data is corrupted or the process is interrupted. This can lead to module failure or vehicle malfunction, especially given the complexity of OEM update schemas.

The underlying idea behind ’159 is to shift the processing burden of reprogramming to a smart dongle connected to the OBD port. Instead of directly streaming data to the vehicle's modules, the dongle first receives the entire update package, verifies its integrity using checksums, and then reprograms the module locally. This staging process minimizes the risk of data corruption during transmission, ensuring a more reliable update.

The claims of ’159 focus on a system comprising a user interface device and a programming device (smart dongle). The user interface device receives and stores a reprogram file and displays a GUI to initiate the reprogram process. The smart dongle receives mapping-and-byte data from the user interface device, stores it in a local cache, reprograms the onboard module using this data, and transmits a success message upon checksum verification.

In practice, the user downloads a reprogram file to a device like a phone or tablet. This device then communicates with the smart dongle via Bluetooth or Wi-Fi, sending the update data in a defined sequence of messages. The dongle's local cache stores this data, and additional checksums are performed to ensure data integrity. Only after the data is fully received and verified does the dongle proceed with reprogramming the vehicle's module.

This approach differs significantly from prior solutions by adding a layer of data verification and local processing at the OBD port. By performing checksums and staging the data locally, the system reduces the risk of data transmission errors that can lead to module damage. This is particularly important when dealing with unknown OEM schemas, where the consequences of data corruption can be severe. The system also incorporates recovery and failure operations to handle potential errors during the update process, further enhancing its robustness.