Touch Event Synchronization via Bypassed Data Path
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing touchscreen devices face challenges in accurately and efficiently synchronizing touch events across multiple devices due to latency and errors caused by traversing multiple layers of the network protocol stack, leading to performance and reliability issues.
Innovation Solution
The implementation of a data path that bypasses system memory, operating systems, and user space applications by using local buffers and Vendor Defined Messages (VDMs) within the System on a Chip (SoC) to directly communicate between touch control and network interface circuitry, reducing latency to sub-microsecond levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If touch events traverse multiple layers of the network protocol stack, then standard communication protocols are followed, but latency increases and synchronization accuracy deteriorates
Solution Approach 1:
The patent extracts the touch event data from the standard network protocol stack processing path and creates a dedicated bypass path. Touch events are captured at the application layer and transmitted directly through a simplified protocol path, removing them from the complex multi-layer stack processing that causes latency. This extraction allows touch events to follow a streamlined path while other data continues through standard protocols.
Solution Approach 2:
The patent introduces a specialized intermediary component (touch event handler/driver) that sits between the application layer and network layer. This intermediary captures touch events, packages them in a simplified format, and transmits them directly to the remote device without full protocol stack processing. The intermediary acts as a mediator that enables direct touch event transmission while maintaining compatibility with the overall system architecture.
2Speed
If touch events are processed through standard network protocols, then communication reliability is maintained, but transmission speed and synchronization performance worsen
Solution Approach 1:
The patent segments the data transmission into two distinct paths: a standard path for general data communication and a dedicated path for touch events. The touch event path is segmented from the general network traffic, allowing it to be processed with higher priority and simpler protocols. This segmentation enables speed optimization for time-critical touch events while maintaining standard reliability protocols for other communications.
Solution Approach 2:
The patent changes the protocol parameters for touch event transmission by using a simplified packet format with reduced header information and optional compression. Touch events are transmitted with modified parameters including smaller packet sizes, reduced acknowledgment requirements, and adjusted timing parameters. These parameter changes enable faster transmission while maintaining sufficient reliability for touch synchronization purposes.
3Loss of time
If a simplified data path is used for touch events, then latency is reduced, but system complexity and implementation difficulty increase
Solution Approach 1:
The patent implements a universal touch event handling mechanism that can operate across different operating systems and hardware platforms. The touch event bypass path uses standardized interfaces and protocols that can be integrated into existing systems without requiring complete redesign. The solution provides multi-functionality by handling both local touch processing and remote synchronization through the same simplified path, reducing the need for separate complex implementations.
Solution Approach 2:
The patent performs preliminary actions by pre-configuring the touch event data path during system initialization or device pairing. Buffer allocations, protocol parameters, and connection settings are established in advance, allowing the simplified path to operate efficiently without requiring complex real-time decisions. This preliminary setup reduces the operational complexity during actual touch event transmission.
Data Source
AI summary
Systems, apparatus, articles of manufacture, and methods are disclosed. An example apparatus to synchronize event data includes first circuitry to implement a user interface controller. The user interface controller of the example apparatus is to detect a user input, transmit a message including event data to a network interface controller (NIC), the event data corresponding to the user input, and provide the event data to a driver to cause an event corresponding to the event data to be rendered by the apparatus. The example apparatus also includes second circuitry to implement the NIC. The NIC of the example apparatus is to store the event data from the message in a local buffer of the NIC, obtain the event data from the local buffer using a direct memory access (DMA) request, and transmit a packet including the event data over a network.