IP Library › Granted Patent US 12,293,178
Granted Patent B2
US 12,293,178 · App. 18/179,774 · Granted May 6, 2025

Vehicular software update system and method therefor

Inventors: Yoon Sik Jung (Seoul, KR); Myeong Gyu Jeong (Seoul, KR); Jin Ah Kim (Gyeonggi-Do, KR); Hak Jun Kim (Goyang-Si, KR); Min Gi Kim (Wonju-Si, KR); Hyeok Sang Jeong (Hwaseong-Si, KR); Young Jee Yang (Seongnam-Si, KR)
Assignees: Hyundai Motor Company; Kia Corporation
G06F8/65B60W50/06B60W2556/45
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,293,178
App. No.
18/179,774
Granted
May 6, 2025
Kind
B2
Abstract

A vehicular software update system includes a management controller coupled to a vehicle and at least one performance controller that receives software for over-the-air (OTA) update in the background from the management controller. The management controller determines a network load of the vehicle and adjusts a transmission speed of the software for OTA update, the software being transmitted to the at least one performance controller, based on a driving state of the vehicle and the network load of the vehicle.

Claims (62)

1. A vehicular software update system, comprising:

a management controller coupled to a vehicle; and

at least one processor configured to receive, from the management controller, software for over-the-air (OTA) update,

wherein the management controller is configured to:

determine a network load of the vehicle;

adjust, based on a driving state of the vehicle and the network load of the vehicle, a transmission speed of the software for OTA update; and

transmit, to the at least one processor and based on the adjusted transmission speed, the software for OTA update,

wherein the management controller is configured to adjust the transmission speed by decreasing, based on a determination that the driving state of the vehicle corresponds to a traveling state, the transmission speed in response to a determination that the network load of the vehicle is greater than or equal to a reference value.

2. The vehicular software update system of claim 1 , wherein the management controller is configured to determine, based on a detection of a controller area network (CAN) message, the network load of the vehicle.

3. The vehicular software update system of claim 1 ,

wherein the at least one processor is configured to execute a foreground process while receiving the software for OTA update in a background process, and

wherein the management controller is configured to transmit the software for OTA update at a first transmission speed by decreasing the transmission speed from a second transmission speed to the first transmission speed slower than the second transmission speed.

4. The vehicular software update system of claim 1 ,

wherein the management controller is configured to adjust the transmission speed by determining, based on a software package and based on event properties, a background transmission interval to correspond to a message interval, wherein the message interval corresponds to a larger value between a minimum message interval associated with reprogramming in the at least one processor and a minimum message interval for each channel,

wherein the software package comprises the minimum message interval associated with reprogramming in the at least one processor, and

wherein the event properties comprise at least one of: the minimum message interval for each channel, or information of a processor associated with OTA update among the at least one processor.

5. The vehicular software update system of claim 1 , wherein the management controller is further configured to:

determine, based on event properties, a processor associated with OTA update among the at least one processor;

allow, based on a determination that the driving state of the vehicle corresponds to an end of traveling, communication with the processor associated with OTA update among the at least one processor, in response to a determination that the network load of the vehicle is greater than or equal to the reference value; and

adjust the transmission speed by prohibiting communication with a processor not associated with OTA update among the at least one processor, and

wherein the event properties comprise at least one of: a minimum message interval for each channel, or information of the processor associated with OTA update.

6. The vehicular software update system of claim 5 , wherein the management controller is configured to, after an OTA update is completed, allow communication with the processor not associated with OTA update.

7. The vehicular software update system of claim 1 , wherein the management controller is configured to reallocate, based on a determination that the driving state of the vehicle corresponds to an end of traveling, a central processing unit (CPU) resource to at least one module in the management controller, in response to a determination that a CPU load is greater than or equal to a reference value.

8. The vehicular software update system of claim 7 , wherein the management controller is further configured to:

group, based on a degree associated with OTA update, the at least one module;

assign, based on the degree associated with OTA update, a priority to at least one group comprising the at least one module; and

allocate, based on the priority and the CPU load, the CPU resource to the at least one module.

9. The vehicular software update system of claim 8 , wherein the management controller is further configured to set a priority of a group with a high degree associated with OTA update among a plurality of groups to be higher than a priority of a group with a low degree associated with OTA update among the plurality of groups, and

wherein the management controller is configured to allocate more CPU resources to a group with a high priority than a group with a low priority.

10. The vehicular software update system of claim 7 , wherein the management controller is configured to, after an OTA update is completed, reallocate the CPU resource to the at least one module using a predetermined default value.

11. A vehicular software update method, comprising:

determining, by a management controller, a network load of a vehicle;

adjusting, by the management controller and based on a driving state of the vehicle and the network load of the vehicle, a transmission speed of software for over-the-air (OTA) update; and

transmitting, by the management controller and based on the adjusted transmission speed, the software for OTA update to at least one processor that receives the software for OTA update in a background process,

wherein the adjusting of the transmission speed comprises:

decreasing, by the management controller and based on a determination that the driving state of the vehicle corresponds to a traveling state, the transmission speed in response to a determination that the network load of the vehicle is greater than or equal to a reference value.

12. The vehicular software update method of claim 11 , further comprising:

determining, by the management controller and based on a detection of a controller area network (CAN) message, the network load of the vehicle.

13. The vehicular software update method of claim 11 , further comprising executing, by the at least one processor, a foreground process while the at least one processor receives the software for OTA update in the background process,

wherein the transmitting the software for OTA update is performed at a first transmission speed by decreasing the transmission speed from a second transmission speed to the first transmission speed slower than the second transmission speed.

14. The vehicular software update method claim 11 , wherein the adjusting of the transmission speed comprises:

determining, by the management controller and based on a software package and based on event properties, a transmission interval to correspond to a message interval, wherein the message interval corresponds to a larger value between a minimum message interval associated with reprogramming in the at least one processor and a minimum message interval for each channel,

wherein the software package comprises the minimum message interval associated with reprogramming in the at least one processor, and

wherein the event properties comprise at least one of: the minimum message interval for each channel, or information of a processor associated with OTA update among the at least one processor.

15. The vehicular software update method of claim 11 , wherein the adjusting of the transmission speed comprises:

determining, by the management controller and based on event properties, a processor associated with OTA update among the at least one processor;

allowing, by the management controller and based on a determination that the driving state of the vehicle corresponds to an end of traveling, communication with the processor associated with OTA update among the at least one processor, in response to a determination that the network load of the vehicle is greater than or equal to the reference value; and

adjusting, by the management controller, the transmission speed by prohibiting communication with a processor not associated with OTA update among the at least one processor, and

wherein the event properties comprise at least one of: a minimum message interval for each channel, or information of the processor associated with OTA update.

16. The vehicular software update method of claim 15 , further comprising:

after an OTA update is completed, allowing, by the management controller, communication with the processor not associated with OTA update.

17. The vehicular software update method of claim 11 , further comprising:

reallocating, by the management controller and based on a determination that the driving state of the vehicle corresponds to an end of traveling, a central processing unit (CPU) resource to at least one module in the management controller, in response to a determination that a CPU load is greater than or equal to a reference value.

18. The vehicular software update method of claim 17 , wherein the reallocating of the CPU resource to the at least one module comprises:

grouping, by the management controller and based on a degree associated with OTA update, the at least one module;

assigning, by the management controller and based on the degree associated with OTA update, a priority to at least one group comprising the at least one module; and

allocating, by the management controller and based on the priority and the CPU load, the CPU resource to the at least one module.

19. The vehicular software update method of claim 18 , wherein a priority of a group with a high degree associated with the OTA update among a plurality of groups is set to be higher than a priority of a group with a low degree associated with OTA update among the plurality of groups, and

wherein the vehicular software update method further comprises:

allocating, by the management controller, more CPU resources to a group with a high priority than a group with a low priority.

20. The vehicular software update method of claim 17 , further comprising:

after an OTA update is completed, reallocating, by the management controller, the CPU resource to the at least one module using a predetermined default value.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2023
From: JUNG, YOON SIK; JEONG, MYEONG GYU; KIM, JIN AH; KIM, HAK JUN; KIM, MIN GI; JEONG, HYEOK SANG; YANG, YOUNG JEE
To: HYUNDAI MOTOR COMPANY; KIA CORPORATION
Reel/Frame 062908/0855 →
Priority Claims (1)
KR 10-2022-0106968 · Aug 25, 2022 · national
Continuity (1)
Related Publication 20240069888A1 · Feb 29, 2024
References Cited (19)
US 8706798B1 · Suchter · 2014 [cited by examiner]
US 10154501B2 · Meredith et al. · 2018 [cited by applicant]
US 11580593B2 · Onodera · 2023 [cited by examiner]
US 20180317067A1 · Ameixieira · 2018 [cited by examiner]
US 20210081192A1 · Jeong · 2021 [cited by examiner]
US 20220104285A1 · Hirashima · 2022 [cited by examiner]
CN 103403707A · 2013 [cited by examiner]
CN 111630936A · 2020 [cited by examiner]
CN 112052017A · 2020 [cited by applicant]
JP 2020188407A · 2020 [cited by applicant]
JP 2021105922A · 2021 [cited by applicant]
JP 2022023690A · 2022 [cited by applicant]
KR 102231503B1 · 2021 [cited by applicant]
KR 1020210038851A · 2021 [cited by applicant]
KR 1020210145400A · 2021 [cited by applicant]
WO WO2020023325A1 · 2020 [cited by examiner]
Engilish PDF version of Badic et al. CN 111630936 A, published date Sep. 4, 2020. [cited by examiner]
Engilish PDF version of CAi et al. et al. CN 112052017 A, published date Jun. 28, 2018. [cited by examiner]
English PDF version of Choudhry et al. CN 112052017 A1 pubished date Nov. 20, 2013. [cited by examiner]