Shared Emulator Segmentation for MFP Model Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The development of applications for multifunction peripherals (MFPs) is hindered by the need for multiple emulators, each requiring significant time, labor, and storage, as well as frequent updates and version upgrades, which complicate the process of providing a prompt correspondence to various MFP models.
Innovation Solution
An information processing system that separates inter-model common processing from model-dependent processing, where inter-model common processing is implemented in a shared emulator provided to developers, and model-dependent processing is handled by external devices such as real machines, virtual real machines, or model-API implementing units, allowing for efficient verification and correspondence to different MFP models.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple emulators are provided for different MFP models, then each model can be verified accurately, but the time, labor, and storage required for emulator maintenance and updates increases significantly
Solution Approach 1:
The emulator is segmented into two distinct parts: a common emulator containing inter-model common processing that can be shared across all MFP models, and model-specific processing components that handle device-dependent operations. This segmentation allows the common emulator to be maintained once while supporting multiple models, significantly reducing maintenance time and labor.
Solution Approach 2:
The common emulator is designed with universal functionality to handle inter-model common processing for multiple MFP models simultaneously. By making the emulator multi-functional and model-agnostic for common operations, a single emulator instance can serve multiple models, eliminating the need to maintain separate emulators for each model.
2Reliability
If multiple emulators are provided for different MFP models, then each model can be verified accurately, but the storage space and labor for managing plug-in modules increases
Solution Approach 1:
The emulator architecture is segmented into a shared common emulator portion and separate model-specific portions. This segmentation allows the bulk of the emulator code (common processing) to be stored once and reused, while only minimal model-specific data needs to be maintained separately, significantly reducing total storage requirements.
Solution Approach 2:
Instead of maintaining separate complete emulator copies for each model, the system uses a single common emulator that can be copied or instantiated multiple times with minimal model-specific configurations. This approach reduces storage space while still enabling verification for multiple models.
3Productivity
If a single emulator is provided for multiple models, then maintenance and storage burden is reduced, but the ability to handle model-specific processing accurately is compromised
Solution Approach 1:
The emulator is segmented into common processing functions that are shared across models and model-specific processing functions that are handled separately. This segmentation enables a single common emulator to maintain high productivity while model-specific accuracy is preserved through dedicated processing components.
Solution Approach 2:
An intermediary mechanism is introduced that allows the common emulator to delegate model-specific processing to external devices or model-specific processing units. This intermediary approach maintains the simplicity and maintainability of the common emulator while ensuring accurate model-specific verification through specialized components.
Data Source
AI summary
An information processing system includes: an information processing apparatus including: a shared operation unit that performs verification of operation of inter-model common processing common to multiple models out of processes of an application with a first program for realizing operation common to the models, and sends a result of the operation verification to the application; a processing requesting unit that requests an external device to perform verification of operation of model-dependent processing specific to each model with a second program for realizing operation specific to each model; and an acquiring unit that acquires a result of the verification of operation of model-dependent processing from the external device, and sends the result to the application, and external devices that perform verification of operation of model-dependent processing specific to each model out of the processes of the application with the second program for realizing operation specific to each model.