Web Protocol Session for Cross-Device Content Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for interacting with content across devices, such as remote desktop and proprietary file transfer protocols, are cumbersome, resource-intensive, and limited in their ability to efficiently transfer and display content between devices, often resulting in latency and user interface issues.
Innovation Solution
Establishing a web protocol session between devices allows for peer-to-peer communication, enabling a first electronic device to instruct a second device to open and display content items, such as emails or media files, using web protocols like HTTP or Comet long-polling, which simulates server-push functionality for efficient content transfer and display.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Area of stationary object
If remote desktop protocols are used to transmit content between devices, then content can be displayed on a larger screen, but graphics processing resources at the host computer are consumed and latency occurs
Solution Approach 1:
The patent extracts the graphics processing function from the host computer and relocates it to the client device. Instead of transmitting rendered video frames from the host, the system transmits the content data itself to the client, which then renders the content locally on its own display hardware, eliminating the need for continuous graphics processing at the host.
Solution Approach 2:
The system creates a copy of the content data and transmits it to the client device for local rendering. Rather than copying video output, the patent copies the underlying content representation, allowing the client to independently render and display the content without requiring graphics processing resources at the host.
2Quantity of substance
If proprietary file transfer protocols are used, then files can be transferred between devices, but the protocols are limited to file transfer rather than content interaction and are tightly embedded in the operating system
Solution Approach 1:
The patent implements a universal content interaction protocol that works across different operating systems and device types. The system uses standard web protocols (HTTP, HTTPS, WebSockets) that are universally supported, enabling content sharing, viewing, and interaction between diverse devices without requiring proprietary, OS-specific implementations.
Solution Approach 2:
The system introduces a web server as an intermediary that mediates content sharing between devices. Instead of direct peer-to-peer proprietary protocol communication, the web server receives content from the source device and serves it to the client device through standard web protocols, providing flexibility and cross-platform compatibility.
3Quantity of substance
If content is transmitted via email or USB connection, then content can be accessed on a different device, but the process is cumbersome and time-consuming
Solution Approach 1:
The system establishes continuous web protocol connections (using techniques like long-polling or WebSockets) that allow real-time content sharing and interaction. Instead of discrete, interruptive transfer methods like email or USB connections, the continuous connection enables immediate content transmission and ongoing interaction without breaking the workflow.
Solution Approach 2:
The patent replaces mechanical connection methods (USB cables, physical media insertion) with electronic web protocol communication. This substitution eliminates the need for physical connections and manual file management operations, enabling instant content sharing through network-based protocols.
Data Source
AI summary
Methods and apparatus for enabling content interaction at a connected electronic device re described. An example method includes establishing a web protocol session between a web server executing on a first electronic user device and a client executing on a second electronic user device via a direct radio frequency connection between the first electronic user device and the second electronic user device, wherein the first electronic user device and the second electronic user device are associated with a same user, the establishing including sending an open request from the client to the web server; and transmitting a response to the open request from the web server to the client, the response including a universal resource identifier identifying a location of content for presenting, on the second electronic device, the application executing on the first electronic device.