Gateway Device Switching Remote Control Modes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote control technologies for computing devices face limitations in seamlessly switching between hardware-based and software-based modes, particularly in terms of availability and user experience, with hardware-based modes being available before the operating system boots but lacking features like hardware-accelerated graphics, and software-based modes providing better user experience but only after the OS is booted.
Innovation Solution
Implementing a gateway device or client device with monitor and switch code that automatically switches remote control between hardware-based and software-based modes based on the availability of each mode, using remote desktop or KVM sessions to emulate input and display interfaces, and encapsulating/decoding I/O and display communication to provide seamless switching.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hardware-based remote control mode is used, then remote access is available before OS boots and in low-power states, but features like hardware-accelerated graphics are not available
Solution Approach 1:
The system dynamically switches between hardware-based and software-based remote control modes based on the host device's power state. When the OS is running, it uses software-based mode to access features like hardware-accelerated graphics. When the OS is not running or in low-power state, it switches to hardware-based mode to maintain remote access availability.
Solution Approach 2:
The gateway device acts as an intermediary between the client device and host device, managing the switching between different remote control modes. It monitors the power state of the host device and routes remote control traffic through the appropriate mode (hardware-based or software-based) to optimize both availability and feature access.
2Adaptability or versatility
If software-based remote control mode is used, then features like hardware-accelerated graphics are available, but remote access is only possible after OS is booted
Solution Approach 1:
The system dynamically adjusts the remote control mode based on operational requirements. Software-based mode is activated when the OS is running to enable advanced features, while hardware-based mode is activated when the OS is not running to ensure continuous availability. This dynamic adaptation resolves the contradiction between feature availability and access availability.
Solution Approach 2:
The system changes the operational parameters of remote control by switching between two distinct modes. The gateway device monitors system state parameters (OS running status) and adjusts the remote control mode parameter accordingly, enabling the system to optimize both feature availability and access availability under different conditions.
3Adaptability or versatility
If manual switching between remote control modes is implemented, then feature selection is possible, but user intervention is required and seamless switching is not achieved
Solution Approach 1:
The gateway device automatically monitors the host device's power state and performs mode switching without requiring user intervention. The system self-manages the selection between hardware-based and software-based remote control modes by detecting OS running status and autonomously routing traffic through the appropriate mode, thereby eliminating the need for manual user actions.
Solution Approach 2:
The gateway device continuously monitors feedback from the host device regarding its power state and OS running status. Based on this real-time feedback, the gateway device automatically adjusts the remote control mode to maintain optimal performance and availability, eliminating the need for manual switching while ensuring the correct mode is used at all times.
4Ease of operation
If automatic mode switching is implemented, then seamless remote access is achieved, but system complexity increases
Solution Approach 1:
The gateway device serves as an intermediary that centralizes the complexity of mode switching logic. Instead of implementing complex switching mechanisms in both client and host devices, the gateway device alone handles monitoring, decision-making, and traffic routing between different remote control modes, thereby achieving seamless switching while concentrating complexity in a single manageable component.
Data Source
AI summary
A host device has a hardware-based remote control mode and a softwarebased remote control mode. The availability of each of the hardware- and software-based remote control modes is monitored. Client device remote control of the host device is selectively switched between the hardware- and softwarebased remote control modes, based on the monitored availability of each remote control mode.