Multi-function Device Controller Selection Between Server and Cloud
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multi-function peripheral devices (MFPs) face challenges in seamlessly integrating with both on-premise servers and cloud services, leading to inconsistencies in service availability and user experience, especially when network disruptions occur or when devices are moved between locations.
Innovation Solution
An MFP is configured to simultaneously register with both on-premise servers and cloud services, allowing it to dynamically identify and connect with either as the controller, ensuring continuous access to services and maintaining user interface functionality even during network disruptions or device relocations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If an MFP is registered with only one server (either on-premise or cloud), then the configuration is simple and easy to manage, but service availability is reduced when network disruptions occur or devices are moved between locations
Solution Approach 1:
The MFP is configured to register with multiple servers simultaneously (both on-premise and cloud services), enabling it to function with either server as the controller. This multi-functionality ensures service continuity regardless of which server is accessible, resolving the contradiction between reliability and complexity by making the system adaptable to different operational scenarios.
Solution Approach 2:
The system dynamically determines which server (on-premise or cloud) acts as the controller based on real-time conditions such as network availability and device location. This dynamic adaptation allows the MFP to switch between single-server simplicity and multi-server reliability as needed, resolving the contradiction by making the configuration flexible rather than static.
2Adaptability or versatility
If an MFP is configured to work with both on-premise servers and cloud services, then service availability is improved, but the complexity of managing multiple registrations increases
Solution Approach 1:
The system introduces a controller determination mechanism that acts as an intermediary between the MFP and multiple servers. This mediator automatically identifies which server should act as the controller based on predefined criteria, simplifying the management of multiple registrations by eliminating the need for manual configuration and reducing the complexity of handling multiple server relationships.
Solution Approach 2:
The MFP autonomously determines which server to connect to without requiring manual intervention or complex user configuration. The device self-manages the complexity of multiple registrations by automatically selecting the appropriate controller based on its current operational context, thereby improving adaptability while keeping the user experience simple.
3Reliability
If the MFP maintains registration with multiple services, then continuous service access is ensured during network disruptions, but the difficulty of detecting and managing the correct controller increases
Solution Approach 1:
The system pre-establishes registration with multiple servers before any network disruption occurs. This preliminary action ensures that when a disruption happens, the MFP already has the necessary connections in place and can immediately determine the appropriate controller without needing to detect or search for available services, thereby maintaining reliable service access while simplifying controller identification.
Data Source
AI summary
A system comprising a multi-function device 112 configured to communicate with both a server 111 and a cloud service 121. The multi-function device 112 comprises: an output unit 407 configured to send S102, S401 identification information of the multi-function device 112 to the cloud service 121; an input unit 407 configured to receive S106, S403 controller information which identifies either the server 111 or the cloud service 121 as a controller of the multi-function device 112; and a login unit 406 configured to receive S201, S501 authentication information. The output unit 407 is further configured to send S202, S204 an authentication request including the authentication information to the controller 111, 121 identified by the controller information. The input unit 407 is further configured to receive S203, S205 an authentication response from the controller 111, 121 that indicates whether or not the authentication information is accepted.