Firmware Version Management for MFP Action Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for setting multifunction peripherals (MFPs) face challenges in managing action configuration data across different firmware versions, leading to potential mismatches and difficulties in correctly setting action configuration values, especially when there are time lags between data creation and device setup, and when different personnel are involved in the process.
Innovation Solution
An information processing system that includes a first management unit for firmware and a second management unit for action configuration data, allowing for the creation and transmission of action configuration data based on the specified schema version, enabling correct setting even with newer firmware versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If action configuration data is created based on a specific firmware version and schema, then the setting can be automated and efficient, but the data cannot be correctly applied when a different firmware version is used
Solution Approach 1:
The system dynamically adapts action configuration data to different firmware versions by introducing a version identification mechanism. When setting data is created, it records the schema version used. During application, the system identifies the current firmware version and automatically selects or transforms the appropriate configuration data, making the system flexible rather than fixed to a single version.
Solution Approach 2:
The patent changes the parameter of firmware version compatibility by embedding version identification information within the action configuration data structure. This allows the same data format to carry version metadata, enabling the system to adjust behavior based on the firmware version without changing the fundamental data creation process.
2Reliability
If firmware version and action configuration data are managed as a fixed set, then compatibility is ensured, but flexibility to update to newer firmware versions is lost
Solution Approach 1:
The patent segments the coupling between firmware and action configuration data by separating version identification from version locking. Instead of treating them as an indivisible fixed set, the system divides the data into configurable elements that can be independently managed. The version information is extracted and used as a selection criterion rather than a binding constraint.
Solution Approach 2:
The system transitions from a static firmware-data pairing to a dynamic selection process. The action configuration data includes version metadata that enables runtime determination of compatibility, allowing the system to adapt to newer firmware versions while maintaining compatibility guarantees through version matching logic.
3Manufacturing precision
If action configuration data is created with detailed schema specifications, then setting precision is improved, but difficulty in judging correctness increases when personnel are different
Solution Approach 1:
The patent implements a feedback mechanism where the system automatically verifies whether action configuration data can be correctly applied to the target firmware version. The version identification and matching process provides immediate feedback on compatibility, eliminating the need for manual judgment by different personnel about whether settings are correct for the given firmware version.
Data Source
AI summary
An information processing system including a device and a client terminal which is able to create action configuration data for implementing a plurality of functions in the device includes a first management unit configured to manage a first version of firmware for implementing a plurality of functions in the device and a second version of a schema usable in the firmware of the first version, a second management unit configured to manage the action configuration data, which has been created based on information managed by the first management unit, and the second version, and a transmission unit configured to, in response to a request from the device, specify the action configuration data managed by the second management unit and to transmit the specified action configuration data and the first version to the device.