Unified User Account Management for Multifunction Peripheral History
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques fail to integrate and manage use history information across multifunction peripherals and information processing applications, leading to inconsistencies and incorrect user account recordings, especially when users perform print requests through both device inputs and web applications.
Innovation Solution
A multifunction peripheral system that associates use history information with an execution user, allowing seamless integration of data from both device inputs and web applications, ensuring accurate user account management by designating users through input sections or applications, and updating records accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If use history information is managed separately for multifunction peripheral operations and application operations, then each system can independently track its own usage, but use history information cannot be integrated and managed as a unified user account
Solution Approach 1:
The patent merges the use history information management of the multifunction peripheral and the application into a unified user account system. The control section integrates usage data from both pull printing (direct device operations) and push printing (application-initiated operations) under the same user account, eliminating information loss while maintaining manageable system architecture through centralized control.
Solution Approach 2:
The user account system is designed to serve multiple functions: it tracks usage for both direct device operations and application operations, manages print quotas across different operation modes, and provides unified authentication. This multi-functionality allows the same user account to handle diverse operations without requiring separate management systems.
2Ease of operation
If push printing is implemented through web applications, then user convenience is improved, but use history information may be recorded under incorrect user accounts
Solution Approach 1:
The control section implements feedback mechanisms to verify user identity across different operation modes. When a print request is received from a web application, the system checks the user account information and provides feedback to ensure correct attribution. This feedback loop prevents misattribution of use history information while maintaining the convenience of remote printing.
Solution Approach 2:
The control section acts as an intermediary between the web application and the use history information storage. It receives print requests from applications, verifies user identity, and ensures that use history information is recorded under the correct user account. This intermediary function maintains measurement precision while allowing convenient application-based operations.
3Adaptability or versatility
If separate management systems are used for pull printing and push printing, then each printing method can be independently controlled, but user account management becomes complex and error-prone
Solution Approach 1:
The patent combines the user account management for pull printing and push printing into a unified system. The control section manages both printing methods under the same user account framework, allowing independent control of each printing method while simplifying user account management. This eliminates the complexity of maintaining separate management systems while preserving the versatility of different printing approaches.
Data Source
AI summary
In a case of a first function of carrying out a cooperative processing in accordance with an instruction from a user of a multifunction peripheral (10), the user is set as an execution user. In a case of a second function of carrying out a cooperative processing in accordance with an instruction from an application, a user instructed by the application is set as an execution user. Further, in a case where an execution user of a cooperative processing carried out using the first function and an execution user of a cooperative processing carried out using the second function are identical, use history information of the execution user is managed as use history information of a single user. This makes it possible to appropriately manage use history information of a cooperative processing.


