Application State Reset for Registration Data Consistency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing information processing systems face issues with maintaining application settings correctly, leading to potential erroneous operations such as wrong recipient transmission in facsimile applications, due to unclear states after registration information changes across different applications.

Innovation Solution

An information processing apparatus with a receiving unit for registering changes and a returning unit that resets the application to a state before the operator's operation, ensuring accurate settings by maintaining or resetting only relevant information, thereby preventing unintended changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If registration information is changed in one application, then the updated information is reflected in that application, but other applications that use the same registration information may continue to use outdated information, leading to inconsistent states and potential erroneous operations

Engineering Contradiction:

Improveaccuracy of application settingsVSAvoidcomplexity of state management across applications

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system implements feedback by notifying other applications when registration information changes occur. The notification unit sends change notifications to applications that are using the changed registration information, allowing them to update their states accordingly. This ensures consistency across applications while maintaining a manageable complexity through targeted notifications rather than universal updates.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system segments the state management by tracking which applications are using which registration information. Instead of treating all applications uniformly, the system identifies and notifies only those applications that are actually affected by the change. This segmentation approach reduces unnecessary updates and simplifies the overall state management complexity.

Inventive Principle:

Principle #1Segmentation

2Reliability

If the system notifies all applications of registration information changes, then consistency is maintained across applications, but the notification overhead and processing time increase

Engineering Contradiction:

Improveconsistency of registration informationVSAvoidtime for notification and state updates

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system applies local quality by sending notifications only to the specific applications that are using the changed registration information, rather than notifying all applications universally. This targeted approach maintains consistency where needed while minimizing unnecessary notification overhead and processing time for applications that are not affected by the change.

Inventive Principle:

Principle #3Local quality

3Reliability

If the system automatically resets applications when registration information changes, then erroneous operations are prevented, but the user loses recent settings and operations that may still be valid

Engineering Contradiction:

Improveprevention of erroneous operationsVSAvoiduser convenience in maintaining settings

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system implements dynamic behavior by providing users with a choice: either automatically reset affected applications or receive notification and manually decide whether to reset. This dynamic approach adapts to user needs, preventing erroneous operations when automatic reset is chosen, while preserving user convenience when manual control is selected. The system flexibility resolves the contradiction by allowing different behaviors based on user preference.

Inventive Principle:

Principle #15Dynamics

4Measurement precision

If the system maintains detailed tracking of which applications use which registration information, then accurate notifications can be sent, but the system complexity and memory requirements increase

Engineering Contradiction:

Improveaccuracy of tracking application-state relationshipsVSAvoidcomplexity of tracking and notification system

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The system applies partial action by tracking only the necessary relationships between registration information and applications that actually use them. Instead of maintaining comprehensive tracking of all possible application-state relationships, the system tracks only those that are currently active and relevant. This reduces the complexity and memory requirements while maintaining sufficient accuracy for effective notifications.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS10547754B2Information processing apparatus

Publication Date: 2020.01.28 FUJIFILM BUSINESS INNOVATION CORP

AI summary

An information processing apparatus includes a receiving unit that receives change of registration information that is made after an operator's operation is performed on an application; and a returning unit that returns a state of at least part of the application to a state before the operator's operation in a case where the receiving unit receives the change of the registration information.