Firmware Memory Partitioning for Reliable Device Rollback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic devices face issues with normal operation and reliable rollback during upgrades, leading to a significant decrease in residual value and user dissatisfaction due to potential errors and failed upgrades.

Innovation Solution

An upgradable electronic device and method that ensures normal operation and reliable rollback by backing up existing program data to a different area of the internal memory when the size is less than or equal to half of the memory space, and updating the data using upgrade data from a management server, with external memory backup options if necessary.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If program data is backed up to external memory, then backup reliability is improved, but device complexity increases

Engineering Contradiction:
Improvebackup reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the memory into multiple areas (first area for current program data, second area for backup program data, third area for upgrade data) within the existing internal memory structure. This segmentation allows reliable backup without adding external memory components, resolving the contradiction between backup reliability and device complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The internal memory is designed to serve multiple functions: storing current program data, storing backup program data, and storing upgrade data. This multi-functionality eliminates the need for separate external memory for backup purposes, maintaining simplicity while ensuring reliable backup through proper memory area utilization.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Device complexity

If backup area is allocated in internal memory, then device complexity is reduced, but backup capacity is limited

Engineering Contradiction:
Improvedevice complexityVSAvoidbackup capacity
Core Design Contradiction:
Device complexityVSQuantity of substance

Solution Approach 1:

The patent dynamically determines the size of the backup area based on the actual size of the program data being backed up. The backup area is allocated within the internal memory according to the program data size, allowing flexible utilization of available memory space. This dynamic approach maximizes backup capacity within the existing internal memory without requiring fixed external memory allocations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of memory utilization by allocating backup area as a percentage or proportion of the total internal memory based on program data size. This parameter-based approach allows the system to adapt backup capacity to actual needs, maximizing the use of internal memory while maintaining simplicity.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If upgrade data is stored in internal memory, then device complexity is reduced, but memory space becomes insufficient

Engineering Contradiction:
Improvedevice complexityVSAvoidmemory space
Core Design Contradiction:
Device complexityVSQuantity of substance

Solution Approach 1:

The patent segments the internal memory into distinct areas: first area for current program data, second area for backup program data, and third area for upgrade data. This segmentation ensures that upgrade data is stored separately from program data, preventing memory space conflicts while maintaining a simple overall structure without requiring external memory.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent resolves the memory space constraint by organizing data storage in a dimensional manner through memory area segmentation rather than simply increasing storage capacity. By creating separate memory regions for different data types, the system can store upgrade data without compromising program data storage, effectively utilizing the memory dimensionality.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

4Reliability

If rollback is implemented, then reliability is improved, but upgrade time increases

Engineering Contradiction:
ImprovereliabilityVSAvoidupgrade time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary backup of program data to the second memory area before executing the upgrade. This preliminary action ensures that if the upgrade fails, the system can quickly restore the backup without time-consuming operations. The backup is prepared in advance, so when rollback is needed, it can be executed rapidly, minimizing time loss while maintaining reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a copy of the program data in the second memory area as a backup. This copying operation is performed before upgrade, and the copy can be quickly restored if needed. The copy mechanism allows for rapid rollback without requiring complex restoration procedures, thus improving reliability while minimizing the time penalty for rollback capability.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP4216054B1Upgradable electronic device and method for upgrading electronic device
Publication Date: 2025.11.12 LG ELECTRONICS INC
  • EP4216054B1 patent drawingFigure 1
  • EP4216054B1 patent drawingFigure 2
  • EP4216054B1 patent drawingFigure 3~4

AI summary

An upgradable electronic device is disclosed. The electronic device includes: a main controller including a single-chip microcomputer including an internal memory and a processing unit; and a communication unit receiving upgrade data from outside the electronic device, wherein, when existing program data stored in a first area of the internal memory has a size less than or equal to a reference size, the processing unit updates the existing program data stored in the first area based on the upgrade data after backing the existing program data up to a second area of the internal memory, the second area being different from the first area.