Mobile system including firmware verification function and firmware update method thereof
US-10206114-B2 · Feb 12, 2019 · US
US12169708B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12169708-B2 |
| Application number | US-202318495971-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 27, 2023 |
| Priority date | Sep 14, 2015 |
| Publication date | Dec 17, 2024 |
| Grant date | Dec 17, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A gateway device is connected to a plurality of electronic controllers on-board a vehicle. The gateway device acquires firmware update information, which includes at least a part of updated firmware to be applied to a first electronic controller, patch data, and information indicating where to apply the patch data. When the gateway device determines that the first electronic controller does not include a firmware cache for performing a pre-update firmware cache operation, the gateway device executes a proxy process. In this regard, the gateway device requests the first electronic controller to transmit boot ROM data to the gateway device, merges the patch data and existing firmware to create updated boot ROM data with updated firmware, and transmits the updated boot ROM data to the first electronic controller that updates the boot ROM data and resets the first electronic controller with the updated firmware.
Opening claim text (preview).
What is claimed is: 1. A gateway device connected via one or more networks to a plurality of electronic controllers on-board a vehicle, the gateway device comprising: one or more memories; and circuitry, that in operation, acquires firmware update information, the firmware update information including at least a part of updated firmware to be applied to a first electronic controller from among the plurality of electronic controllers on-board the vehicle, the firmware update information including patch data and information indicating where to apply the patch data, determines, by accessing the one or more memories, whether or not the first electronic controller satisfies a first condition based on first information about the first electronic controller, wherein the first information is whether the first electronic controller includes a firmware cache for performing a pre-update firmware cache operation, and causes, when the first condition is determined not to be satisfied, the gateway device to execute a proxy process, wherein the gateway device requests the first electronic controller to transmit boot ROM data to the gateway device, merges the patch data and existing firmware to create updated boot ROM data with updated firmware, and transmits the updated boot ROM data to the first electronic controller that updates the boot ROM data and resets the first electronic controller with the updated firmware. 2. The gateway device according to claim 1 , wherein the circuitry, further in operation, determines, by accessing the one or more memories, whether or not the first electronic controller satisfies a second condition based on second information about the first electronic controller, wherein the second information is whether the first electronic controller is capable of performing a signature verification operation, which is determined prior to transmittal of the updated firmware, causes, when the second condition is determined to be satisfied, the first electronic controller to execute a first process related to updating firmware of the first electronic controller, and causes, when the second condition is determined not to be satisfied, a first device on-board the vehicle, other than the first electronic controller, to execute the first process related to updating the firmware of the first electronic controller by proxy. 3. The gateway device according to claim 2 , wherein the second information indicates a processing capability of the first electronic controller. 4. The gateway device according to claim 2 , wherein the second information indicates whether or not the first electronic controller includes a function of executing the first process, and the circuitry determines that the second condition is satisfied when the first electronic controller includes the function of executing the first process, and the second condition is determined not to be satisfied when the first electronic controller does not include the function of executing the first process. 5. The gateway device according to claim 2 , wherein the firmware update information includes a signature attached to the updated firmware, and the first process is a process of verifying the signature. 6. The gateway device according to claim 5 , wherein when the second condition is determined not to be satisfied, the circuitry selects, as the first device, an electronic controller that is other than the first electronic controller and that includes a key to use for verifying the signature from among the plurality of electronic controllers. 7. The gateway device according to claim 2 , wherein the first process is a process of saving pre-update firmware held by the first electronic controller. 8. The gateway device according to claim 2 , wherein when the second condition is determined not to be satisfied, the circuitry selects, as the first device, a second electronic controller other than the first electronic controller from among the plurality of electronic controllers. 9. The gateway device according to claim 2 , wherein when the second condition is determined not to be satisfied, the circuitry selects the gateway device as the first device. 10. The gateway device according to claim 1 , wherein the plurality of electronic controllers communicates over the one or more networks in accordance with a controller area network (CAN) protocol. 11. An in-vehicle network system provided with a plurality of electronic controllers on-board a vehicle that communicate over one or more networks, and a gateway device connected to the one or more networks, the gateway device comprising: one or more memories; and circuitry, that in operation, acquires firmware update information, the firmware update information including at least a part of updated firmware to be applied to a first electronic controller from among the plurality of electronic controllers on-board the vehicle, the firmware update information including patch data and information indicating where to apply the patch data, determines, by accessing the one or more memories, whether or not the first electronic controller satisfies a first condition based on first information about the first electronic controller, wherein the first information is whether the first electronic controller includes a firmware cache for performing a pre-update firmware cache operation, and causes, when the first condition is determined not to be satisfied, the gateway device to execute a proxy process, wherein the gateway device requests the first electronic controller to transmit boot ROM data to the gateway device, merges the patch data and existing firmware to create updated boot ROM data with updated firmware, and transmits the updated boot ROM data to the first electronic controller that updates the boot ROM data and resets the first electronic controller with the updated firmware. 12. A method used in an in-vehicle network system provided with a plurality of electronic controllers on-board a vehicle that communicate over one or more networks, the method comprising: acquiring firmware update information, the firmware update information including at least a part of updated firmware to be applied to a first electronic controller from among the plurality of electronic controllers, the firmware update information including patch data and information indicating where to apply the patch data; determining, by accessing the one or more memories, whether or not the first electronic controller satisfies a first condition based on first information about the first electronic controller, wherein the first information is whether the first electronic controller includes a firmware cache for performing a pre-update firmware cache operation; and causing, when the first condition is determined not to be satisfied, the gateway device to execute a proxy process, wherein the gateway device requests the first electronic controller to transmit boot ROM data to the gateway device, merges the patch data and existing firmware to create updated boot ROM data with updated firmware, and transmits the updated boot ROM data to the first electronic controller that updates the boot ROM data and resets the first electronic controller with the updated firmware.
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title
Single bridge functionality, e.g. connection of two networks over a single bridge · CPC title
Architecture of a communication node (current supply arrangements H04L12/10; intermediate storage or scheduling H04L49/90) · CPC title
Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.