Semi-autonomous Touch Controller State Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current touch I/O device controllers require frequent communication with the host device to manage operational sub-states, leading to burdensome processing, power consumption, and communication bandwidth usage, resulting in noticeable delays and potential loss of user input.
Innovation Solution
Implementing semi-autonomous operation for touch I/O device controllers with predefined sub-states (idle, wait for finger, finger on, pre-capture, capture, navigate, and hold) that allow the device to switch states based on host commands or pre-set sub-state variables, reducing the need for constant host monitoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If the host frequently communicates with the touch I/O device controller to control operational sub-states, then the host can maintain control over the device, but host processing resources, power resources, and communication bandwidth are consumed
Solution Approach 1:
The patent segments the control system into two parts: the host device that sets high-level policies and the touch I/O device controller that autonomously manages operational sub-states. This segmentation allows the controller to operate independently within defined parameters, reducing the frequency of host communications and thereby reducing host power consumption while maintaining overall control.
Solution Approach 2:
The touch I/O device controller is designed to self-manage its operational sub-states based on predefined policies without requiring constant host intervention. The controller autonomously transitions between states such as fingerprint capture, navigation, and idle states, reducing the need for frequent host communications and associated power consumption.
2Extent of automation
If the host frequently communicates with the touch I/O device controller to control operational sub-states, then the host can maintain control over the device, but communication bandwidth between host and controller is consumed
Solution Approach 1:
By segmenting control authority between the host (policy setting) and controller (state management), the system reduces the volume of communications required. The controller independently manages state transitions within its segmented authority, minimizing bandwidth consumption while maintaining host oversight through periodic policy updates.
Solution Approach 2:
The controller performs self-service by autonomously managing its operational states without requiring constant host commands. This self-management reduces communication bandwidth usage as the controller only needs to communicate with the host when policy changes are needed or when reporting significant events, rather than for every state transition.
3Reliability
If the host monitors and controls the touch I/O device controller, then the host can ensure correct operation, but noticeable delays occur in responding to user input
Solution Approach 1:
The patent segments decision-making authority by allowing the controller to autonomously manage operational states while the host retains control over policy settings. This segmentation enables immediate local responses to user inputs without host intervention delays, while the host ensures reliability by setting and updating operational policies that guide controller behavior.
Solution Approach 2:
The controller provides self-service by immediately processing user inputs and transitioning between operational states without waiting for host confirmation. This autonomous operation eliminates response delays while maintaining reliability through adherence to host-defined policies that ensure correct operational behavior.
4Extent of automation
If the host frequently communicates with the touch I/O device controller to control operational sub-states, then the host can maintain control over the device, but host processing resources are consumed
Solution Approach 1:
The patent segments processing responsibilities between the host and controller. The host focuses on higher-level tasks such as setting policies and managing applications, while the controller handles lower-level tasks of state management and input processing. This segmentation improves host processing efficiency by offloading routine operations to the autonomous controller.
Solution Approach 2:
The controller performs self-service by autonomously managing its operational states and processing inputs without requiring host intervention. This reduces the processing burden on the host, allowing it to focus on more complex tasks and improving overall system productivity.
Data Source
AI summary
A touch I/O device controller may operate in an idle state, a wait for finger on state, and a finger on state. The finger on state may include a hold sub-state, a capture sub-state, a navigation sub-state, and a pre-capture sub-state. The controller may switch states and/or sub-states based on commands received from its host or based on a sub-state variable set by the host. When the controller detects a finger of a user and enters the finger on state, the touch I/O device may enter a particular sub-state based on the sub-state variable. Further, when a fingerprint is captured in capture sub-state, the controller may switch sub-states based on the value of the sub-state variable. In various implementations, the host may provide one or more APIs that may be utilized by applications to directly influence the controller and/or request that the host do so.