Secure Remote Software Update via Cryptographic Validation and Image Backup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for updating software in remote devices are costly and inefficient, often requiring device recall and reprogramming, and lack secure and guaranteed mechanisms for ensuring proper updates.

Innovation Solution

A system and method for securely updating remote device software via a remote service center, which includes automatic identification of update needs, secure communication protocols, incremental software downloads, and automatic reinstallation of previous software in case of failure, using a server with a processor and memory to manage updates and ensure device functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If device recall and reprogramming is performed to update software, then software update reliability is improved, but update cost and device downtime increase

Engineering Contradiction:
Improvesoftware update reliabilityVSAvoiddevice downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The remote device autonomously performs software update operations by receiving update packages from the server, executing the updates locally, and self-validating the update results through cryptographic verification. This eliminates the need for manual recall and reprogramming operations, allowing devices to update themselves in the field.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A server acts as an intermediary between the update source and remote devices, managing the distribution of software updates, verifying device eligibility, and coordinating the update process. This centralized coordination enables reliable updates without requiring physical device recall.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If complete software download is performed, then update completeness is improved, but update time and bandwidth consumption increase

Engineering Contradiction:
Improveupdate completenessVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The software update process is segmented into distinct phases: validation phase (where the server verifies device eligibility and update requirements), download phase (where the device receives the update package), and execution phase (where the device applies the update). This segmentation allows for efficient resource usage and enables early termination if validation fails.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The server performs preliminary validation actions before initiating the complete software download, including verifying device identity, checking update requirements, and confirming device eligibility. This preliminary action prevents unnecessary downloads and ensures that only devices that need updates receive them, saving time and bandwidth.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If software update is performed without backup, then update speed is improved, but device operability reliability deteriorates

Engineering Contradiction:
Improveupdate speedVSAvoiddevice operability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements cryptographic validation mechanisms that verify the authenticity and integrity of update packages before execution. This validation acts as a protective cushion that prevents corrupted or malicious updates from compromising device operability, ensuring that only verified updates are applied.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Reliability

If administrative procedures are implemented to correct failed updates, then update reliability is improved, but administrative overhead increases

Engineering Contradiction:
Improveupdate correctnessVSAvoidadministrative overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements automated feedback mechanisms where the device reports update status and validation results back to the server. The server automatically processes this feedback and can initiate corrective actions or provide guidance, eliminating the need for manual administrative procedures to correct failed updates.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS7512939B2System and method of secure updating of remote device software
Publication Date: 2009.03.31 QUADIENT TECH FRANCE
  • US7512939B2 patent drawing
  • US7512939B2 patent drawing
  • US7512939B2 patent drawing

AI summary

A method of securely updating software in a remote device includes copying selected portions of program code in the remote device to a memory, downloading software to the remote device, and upon detecting an unsuccessful download, reinstalling the selected portions of program code.