Peripheral Firmware Download Control via Rewrite Permit Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing firmware downloading methods fail to prevent incompatible program data from being downloaded to new-model card readers, leading to system failures and operational issues when old-model program data is stored in higher-level devices.

Innovation Solution

Incorporating a rewrite control unit in the peripheral that checks for rewriting permit data in the download file, allowing only compatible program data to be rewritten, and returning a completion response without rewriting if the data is not permitted, ensuring that only program data compatible with the new-model card reader is downloaded.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the peripheral rejects downloading incompatible program data, then compatibility is improved, but the downloading process may fail and cause system failure

Engineering Contradiction:
ImprovecompatibilityVSAvoiddownloading process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The peripheral performs preliminary identification of its own model type before the downloading process begins. This preliminary action allows the peripheral to determine in advance whether the stored program data is compatible with its model, enabling it to reject incompatible data proactively and prevent system failure while maintaining a smooth downloading process for compatible data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The peripheral provides feedback to the higher-level device about its model type and compatibility status during the downloading process. This feedback mechanism allows the higher-level device to understand whether the peripheral can accept the program data being transferred, enabling the peripheral to reject incompatible data while keeping the downloading process operational for compatible data.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If the peripheral downloads program data without verification, then the downloading process is simple, but incompatible program data may be downloaded causing system failure

Engineering Contradiction:
Improvedownloading processVSAvoidsystem stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The peripheral performs preliminary identification of its own model type before the downloading process begins. This preliminary action allows the peripheral to determine in advance whether the stored program data is compatible with its model, enabling it to reject incompatible data proactively and prevent system failure while maintaining a smooth downloading process for compatible data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The peripheral provides feedback to the higher-level device about its model type and compatibility status during the downloading process. This feedback mechanism allows the higher-level device to understand whether the peripheral can accept the program data being transferred, enabling the peripheral to reject incompatible data while keeping the downloading process operational for compatible data.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8954621B2Peripheral, method of controlling peripheral, and firmware downloading system
Publication Date: 2015.02.10 SANKYO SEIKI MFG CO LTD
  • US8954621B2 patent drawing
  • US8954621B2 patent drawing
  • US8954621B2 patent drawing

AI summary

A peripheral may be connected to a higher-level device. Firmware program data may be downloaded from the higher-level device to the peripheral. The peripheral may include a rewrite control unit for controlling rewriting the program data stored in the peripheral. The program data stored in the peripheral may be rewritten by use of the program data sent from the higher-level device, and then a response, notifying that data rewriting has normally been completed, may be returned to the higher-level device, if the download file includes rewriting permit data. A response, notifying that data rewriting has normally been completed, may be returned to the higher-level device, without rewriting the program data stored in the peripheral by use of the program data sent from the higher-level device, if the download file does not include rewriting permit data.