Thin Client Interceptor for Peripheral Data Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current thin client protocols, such as Microsoft's RDP, are limited in their ability to efficiently route and process data for peripheral devices, especially in environments where additional protocol layers are not available, like cell phones, due to the requirement for separate data transmission channels and specific operating system support.
Innovation Solution
The method involves receiving information at an electronic device, extracting a subset of data within a negotiated range, processing it, and directing it to other peripheral devices, allowing for independent control of remote peripheral devices without needing higher-level communication protocols, and embedding input data into data streams for remote devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If thin client protocols like RDP are used to provide remote access functionality, then reliable and fast point-to-point communication is achieved, but the system requires separate data transmission channels and specific operating system support which limits device compatibility
Solution Approach 1:
The patent introduces an intermediary process that intercepts data calls between applications and peripheral devices, acting as a mediator that translates and routes data without requiring the underlying operating system or protocol stack to support thin client functionality. This intermediary layer enables thin client operation on devices that would otherwise be incompatible
Solution Approach 2:
The patent segments the thin client functionality into a separate intercepting process that operates independently from the operating system kernel and protocol stacks. By dividing the functionality into modular components (interceptor, data extraction module, routing module), the system achieves protocol independence and broader device compatibility while maintaining reliable communication
2Adaptability or versatility
If additional protocol layers are added to enable thin client functionality on diverse devices, then device compatibility is improved, but system complexity and cost increase
Solution Approach 1:
The patent extracts the thin client protocol functionality from the operating system kernel and network stack, placing it in a separate user-space process. This extraction eliminates the need to modify or add protocol layers to the operating system, reducing complexity while maintaining compatibility across different devices and operating systems
Solution Approach 2:
The intercepting process serves multiple functions: it intercepts data calls, extracts relevant data, routes data to appropriate peripheral devices, and manages multiple communication channels. This multi-functional approach eliminates the need for separate protocol implementations for different devices, reducing overall system complexity
3Ease of operation
If thin client functionality is integrated into the operating system with full protocol support, then communication capability is improved, but the requirement for separate data transmission channels limits support for devices like cell phones
Solution Approach 1:
The patent implements dynamic data channel creation where the intercepting process identifies available communication channels on the host device and adapts the data transmission path accordingly. When separate data channels are unavailable (as in cell phones), the system dynamically uses alternative channels, enabling thin client functionality across diverse device types
Solution Approach 2:
The system changes the parameters of data transmission by extracting only the necessary data subsets from intercepted calls and transmitting them through available channels. By modifying data transmission parameters (data format, channel selection, timing), the system accommodates devices with different communication capabilities without requiring dedicated thin client channels
Data Source
AI summary
An apparatus and method of adding thin client functionality are disclosed. One example method provides generating a call function directed to an electronic device and at least one peripheral device. The method also includes redirecting the call function to an auxiliary device, extracting payload data from information sent to the at least one peripheral device, discarding values outside a previously negotiated range from the extracted payload data, performing at least one of incrementing and decrementing the remaining values of the payload data to create a data subset, and redirecting the data subset to at least one other peripheral device resulting in output information being sent to the at least one other peripheral device.