US2023176850A1PendingUtilityA1
Vehicle update system and method
Est. expiryDec 7, 2041(~15.4 yrs left)· nominal 20-yr term from priority
G06F 8/65H04L 67/12H04L 67/34B60R 16/023B60R 16/033G06F 8/654
51
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
A vehicle update system includes a server that stores a new version of vehicle software, and a vehicle update device that determines an update method of the vehicle software according to a vehicle state and a communication state with the server to improve a customer’s satisfaction by minimizing failure of update.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A vehicle update system comprising:
a server configured to store a new version of vehicle software; and a vehicle update device configured to determine an update method of the vehicle software according to a vehicle state and a communication state with the server.
2 . The vehicle update system of claim 1 , wherein the vehicle update device includes a storage configured to store the new version of the vehicle software therein.
3 . The vehicle update system of claim 2 , wherein the update method of the vehicle software includes:
an Over-The-Air (OTA) method of updating the vehicle software using the new version of the vehicle software downloaded from the server; and a USB method of updating the vehicle software using the new version of the vehicle software received from the storage.
4 . The vehicle update system of claim 3 , wherein the vehicle update device is configured to determine the USB method as the update method when a vehicle is in an ignition-off state or when a communication speed is less than a reference speed according to the communication state with the server.
5 . The vehicle update system of claim 4 , wherein the vehicle update device is configured to compare an update time required to complete updating using the OTA method with an update time required to complete updating using the USB method when the vehicle is switched to an ignition-on state from the ignition-off state and when the communication speed is greater than or equal to the reference speed after the update method has been determined to be the USB method.
6 . The vehicle update system of claim 5 , wherein the vehicle update device is configured to switch the update method to the OTA method when the update time required to complete the updating using the OTA method is less than the update time required to complete the updating using the USB method.
7 . The vehicle update system of claim 5 , wherein the vehicle update device is configured to maintain the USB method as the update method when the update time required to complete the updating using the OTA method is not less than the update time required to complete the updating using the USB method.
8 . The vehicle update system of claim 3 , wherein the vehicle update device is configured to determine an available time of a vehicle battery and an update time required to perform updating to the new version and to determine the update method of the vehicle software by comparing the update time with the available time of the vehicle battery.
9 . The vehicle update system of claim 8 , wherein the vehicle update device is configured to determine the USB method as the update method when the available time of the vehicle battery is less than the update time.
10 . The vehicle update system of claim 8 , wherein the vehicle update device is configured to determine the OTA method as the update method when the available time of the vehicle battery is not less than the update time.
11 . The vehicle update system of claim 9 , wherein the vehicle update device is configured to stop the updating of the vehicle software in the OTA method, to inform the stop of the updating, and to switch the update method of the vehicle software to the USB method when communication with the server is not normal while the vehicle software is being updated in the OTA method.
12 . The vehicle update system of claim 11 , wherein the vehicle update device is configured to inform a remaining time until the updating of the vehicle software is completed through the OTA method, and configured to switch the update method of the vehicle software to the USB method when the vehicle is switched to an ignition-off state while the vehicle software is being updated in the OTA method.
13 . The vehicle update system of claim 12 , wherein the vehicle update device is configured to compare a time required to complete the updating of the vehicle software in the OTA method with a time required to complete the updating of the vehicle software in the USB method when the vehicle is switched to an ignition-on state from the ignition-off state while the vehicle software is being updated in the USB method.
14 . The vehicle update system of claim 13 , wherein the vehicle update device is configured to switch the update method to the OTA method when the time required to complete the updating of the vehicle software in the OTA method is less than the time required to complete the updating of the vehicle software in the USB method.
15 . The vehicle update system of claim 13 , wherein the vehicle update device is configured to maintain the USB method as the update method when the time required to complete the updating of the vehicle software in the OTA method is not less than the time required to complete the updating of the vehicle software in the USB method.
16 . A vehicle update method comprising:
determining, by a controller, a communication state with a server storing a vehicle state and a new version of a vehicle software; and determining, by the controller, an update method of the vehicle software according to the vehicle state and the communication state with the server.
17 . The vehicle update method of claim 16 , wherein the vehicle includes a storage configured to store the new version of the vehicle software therein.
18 . The vehicle update method of claim 17 , wherein the update method of the vehicle software includes:
an Over-The-Air (OTA) method of updating the vehicle software using the new version of the vehicle software downloaded from the server; and a USB method of updating the vehicle software using the new version of the vehicle software received from the storage.
19 . The vehicle update method of claim 18 , further including:
determining, by the controller, the update method as the USB method when a vehicle is in an ignition-off state or when a communication speed is less than a reference speed according to the communication state with the server.
20 . The vehicle update method of claim 19 , further including:
comparing, by the controller, an update time required to complete updating using the OTA method with an update time required to complete updating using the USB method when the vehicle is switched to an ignition-on state from the ignition-off state or when the communication speed is greater than or equal to the reference speed after the update method has been determined to be the USB method.
21 . The vehicle update method of claim 20 , further including:
switching, by the controller, the update method to the OTA method when the update time required to complete the updating using the OTA method is less than the update time required to complete the updating using the USB method.Join the waitlist — get patent alerts
Track US2023176850A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.