History Information Management Device Usage-Based Deletion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Image processing devices face limitations in storing and managing setting history information, leading to unintentional deletion of valuable data when storage capacity is reached, without considering the utility value of the information.

Innovation Solution

A history information management device that stores a predetermined limit of setting history information and deletes it based on usage frequency, ensuring that non-essential data is removed first, thereby preserving valuable user data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If setting history information is deleted when storage capacity is reached, then storage capacity is secured for new data, but valuable setting history information may be unintentionally deleted

Engineering Contradiction:
Improvestorage capacityVSAvoidvaluable setting history information
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent changes the deletion criterion from a simple storage capacity threshold to a composite parameter that includes usage frequency and importance level. The controller evaluates multiple parameters (number of times the setting was used, recency of use, and user-defined importance) to determine which setting history information to delete, thereby preserving valuable information while maintaining storage capacity.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system implements feedback mechanisms where the controller continuously monitors the usage of setting history information and adjusts deletion decisions based on this feedback. The usage frequency and importance levels are tracked and fed back into the deletion determination process, allowing the system to learn and adapt to user preferences over time.

Inventive Principle:
Principle #23Feedback

2Loss of information

If setting history information is stored with high capacity, then more historical data is preserved, but the device cannot maintain operation when storage is full

Engineering Contradiction:
Improvesetting history information preservationVSAvoiddevice operation continuity
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent implements dynamic deletion policies that adapt based on current storage conditions and usage patterns. Rather than using a fixed deletion rule, the system dynamically evaluates which setting history information to retain or delete based on real-time usage frequency and importance levels, allowing flexible management of storage capacity while ensuring operational continuity.

Inventive Principle:
Principle #15Dynamics

3Device complexity

If deletion policy is based on oldest execution date, then storage management is simple, but important recent settings may be deleted

Engineering Contradiction:
Improvedeletion policy complexityVSAvoidimportant setting history information
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent transforms the deletion policy from a single-parameter (oldest execution date) system to a multi-parameter evaluation system that considers usage frequency, recency of use, and user-defined importance levels. This allows the system to make more informed deletion decisions while maintaining manageable complexity through automated evaluation.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11875077B2History information management device, image processing device, and history information management method
Publication Date: 2024.01.16 SHARP KK
  • US11875077B2 patent drawing
  • US11875077B2 patent drawing
  • US11875077B2 patent drawing

AI summary

A history information management device includes a storage capable of storing a predetermined limit number of pieces of setting history information pertaining to execution of a job; and a controller that controls execution of the job by using the setting history information. In a case where the number of pieces of the stored setting history information has reached the predetermined limit number, the controller deletes, from the storage, the setting history information according to a result of use of the setting history information.