# US 2019/0377564 A1 · Low-power device recovery using a backup firmware image > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0377564 A1 - Document ID: US20190377564A1 - Status: Published application - Kind: A1 - Application number: 16/550,649 - Filed: 2019-08-26 - Published: 2019-12-12 - Earliest claimed: 2018-04-16 - Assignees: Infineon Technologies AG - Applicants: Infineon Technologies AG - Inventors: Dragos Ionel POENARU - Web page: https://patentgrep.com/patent/US20190377564A1 ## CPC - G06F 8/63: {Image based installation; Cloning; Build to order} - B60C 23/0471: {System initialisation, e.g. upload or calibration of operating parameters} - B60C 23/0479: {Communicating with external units being not part of the vehicle, e.g. tools for diagnostic, mobile phones, electronic keys or service stations} - G06F 3/0607: {by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device} - G06F 3/065: {Replication mechanisms} - G06F 3/0652: {Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket} - G06F 3/0673: {Single storage device} - G06F 11/1433: {during software upgrading} - G06F 11/1443: {Transmit or communication errors} - G06F 11/1446: Point-in-time backing up or restoration of persistent data - H04L 1/08: by repeating transmission, e.g. Verdan system {(H04L1/1858 and H04L1/189 take precedence)} - G06F 8/65: Updates (security arrangements therefor G06F21/57) - G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)} - H04B 7/24: for communication between two or more posts (wireless communication networks H04W) - Y02D 30/70: in wireless communication networks - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - B60C: VEHICLE TYRES; TYRE INFLATION; TYRE CHANGING; CONNECTING VALVES TO INFLATABLE ELASTIC BODIES IN GENERAL; DEVICES OR ARRANGEMENTS RELATED TO TYRES - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04B: TRANSMISSION - Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE ## Abstract Some examples described herein may involve receiving, via a wireless transmission, a firmware code update that is to be installed in a main memory of the electronic device, determining that the firmware code update is not successfully received; determining, based on determining that the firmware code update is not successfully received, that a secondary memory, of the electronic device, includes a firmware image; and installing the backup firmware image, from the secondary memory, in the main memory to provide the set of functionalities to the electronic device ## Claims ### Claim at position 1 1-20. (canceled) ### Claim 21 A method, comprising: determining, by a device, that a firmware code update that is to be installed in the device is not successfully received; determining, by the device and based on determining that the firmware code update is not successfully received, an amount of power remaining in a battery of the device; and installing, by the device and based on determining that the amount of power remaining in the battery does not satisfy a threshold, a backup firmware to provide a set of functionalities to the device. ### Claim 22 (depends on 21) The method of claim 21, further comprising: determining that a backup memory is stored in a memory of the device; and wherein installing the backup firmware comprises: installing the backup memory from the memory. ### Claim 23 (depends on 21) The method of claim 21, further comprising: detecting a failure associated with at least one of: a transmission of the firmware code update, the firmware code update, or a memory of the device; and wherein determining that the firmware code update is not successfully received comprises: determining, based on detecting the failure, that the firmware code update is not successfully received. ### Claim 24 (depends on 21) The method of claim 21, further comprising: broadcasting a signal indicating that the device has limited functionality. ### Claim 25 (depends on 24) The method of claim 24, further comprising: receiving, based on broadcasting the signal, another transmission of the firmware code update. ### Claim 26 (depends on 21) The method of claim 21, further comprising: determining, based on determining that the firmware code update is not successfully received, that the amount of power remaining in the battery satisfies the threshold; and sending, based on determining that the amount of power remaining in the battery satisfies the threshold, a request for at least a portion of the firmware code update to be resent. ### Claim 27 (depends on 26) The method of claim 26, further comprising: determining, based on sending the request, that a successive transmission of the firmware code update failed; wherein determining the amount of power remaining in the battery comprises: determining, based on determining that the successive transmission of the firmware code update failed, the amount of power remaining in the battery; and wherein installing the backup firmware comprises: installing, based on determining that the amount of power remaining in the battery does not satisfy the threshold, the backup firmware. ### Claim 28 A device, comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, configured to: determine that a firmware code update that is to be installed in the device is not successfully received; determine, based on determining that the firmware code update is not successfully received, an amount of power remaining in a battery of the device; and install, based on determining that the amount of power remaining in the battery does not satisfy a threshold, a backup firmware to provide a set of functionalities to the device. ### Claim 29 (depends on 28) The device of claim 28, wherein the one or more processors are further configured to: determine that the backup firmware is stored in a memory of the device; and wherein the one or more processors, when installing the backup firmware, are configured to: install the backup firmware from the memory. ### Claim 30 (depends on 28) The device of claim 28, wherein the one or more processors are further configured to: detect a failure associated with at least one of: a transmission of the firmware code update, the firmware code update, or a memory of the device; and wherein the one or more processors, when determining that the firmware code update is not successfully received, are configured to: determine, based on detecting the failure, that the firmware code update is not successfully received. ### Claim 31 (depends on 28) The device of claim 28, wherein the one or more processors are further configured to: broadcast a signal indicating that the device has limited functionality. ### Claim 32 (depends on 31) The device of claim 31, wherein the one or more processors are further configured to: receive, based on broadcasting the signal, another transmission of the firmware code update. ### Claim 33 (depends on 28) The device of claim 28, wherein the one or more processors are further configured to: determine, based on determining that the firmware code update is not successfully received, that the amount of power remaining in the battery satisfies the threshold; and send, based on determining that the amount of power remaining in the battery satisfies the threshold, a request for at least a portion of the firmware code update to be resent. ### Claim 34 (depends on 33) The device of claim 33, wherein the one or more processors are further configured to: determine, based on sending the request, that a successive transmission of the firmware code update failed; wherein the one or more processors, when determining the amount of power remaining in the battery, are configured to: determine, based on determining that the successive transmission of the firmware code update failed, the amount of power remaining in the battery; and wherein the one or more processors, when installing the backup firmware, are configured to: install, based on determining that the amount of power remaining in the battery does not satisfy the threshold, the backup firmware. ### Claim 35 A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to: determine that a firmware code update that is to be installed in the device is not successfully received; determine, based on determining that the firmware code update is not successfully received, an amount of power remaining in a battery of the device; and install, based on determining that the amount of power remaining in the battery does not satisfy a threshold, a backup firmware to provide a set of functionalities to the device. ### Claim 36 (depends on 35) The non-transitory computer-readable medium of claim 35, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: determine that the backup firmware is stored in a memory of the device; and wherein the one or more instructions, that cause the one or more processors to install the backup firmware, cause the one or more processors to: install the backup firmware from the memory. ### Claim 37 (depends on 35) The non-transitory computer-readable medium of claim 35, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: detect a failure associated with at least one of: a transmission of the firmware code update, the firmware code update, or a memory of the device; and wherein the one or more instructions, that cause the one or more processors to determine that the firmware code update is not successfully received, cause the one or more processors to: determine, based on detecting the failure, that the firmware code update is not successfully received. ### Claim 38 (depends on 35) The non-transitory computer-readable medium of claim 35, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: broadcast a signal indicating that the device has limited functionality. ### Claim 39 (depends on 38) The non-transitory computer-readable medium of claim 38, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: receive, based on broadcasting the signal, another transmission of the firmware code update. ### Claim 40 (depends on 35) The non-transitory computer-readable medium of claim 35, wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: determine, based on determining that the firmware code update is not successfully received, that the amount of power remaining in the battery satisfies the threshold; send, based on determining that the amount of power remaining in the battery satisfies the threshold, a request for at least a portion of the firmware code update to be resent; determine, based on sending the request, that a successive transmission of the firmware code update failed; wherein the one or more instructions, that cause the one or more processors to determine the amount of power remaining in the battery, cause the one or more processors to: determine, based on determining that the successive transmission of the firmware code update failed, the amount of power remaining in the battery; and wherein the one or more instructions, that cause the one or more processors to install the backup firmware, cause the one or more processors to: install, based on determining that the amount of power remaining in the battery does not satisfy the threshold, the backup firmware.