Web Socket Routing Table for Media Device Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current HTTP communication is inefficient due to its half-duplex nature and overhead from repetitive request and response messages, which hampers the delivery of media content and related information across user devices and server applications.
Innovation Solution
Implementing web sockets to establish full-duplex connections between client media devices and server applications, utilizing a routing table to manage communications and overcome limitations in HTTP and web socket specifications, allowing for efficient message transmission and reception without the need for constant polling or response messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If HTTP communication is used between client media devices and server applications, then compatibility and simplicity are maintained, but communication efficiency deteriorates due to half-duplex nature and overhead from repetitive request and response messages
Solution Approach 1:
The patent changes the communication mode parameter from HTTP's half-duplex request-response model to WebSocket's full-duplex persistent connection model. This allows simultaneous bidirectional communication without the overhead of repeated HTTP handshakes, directly improving communication efficiency while maintaining protocol simplicity through standardized WebSocket implementation.
Solution Approach 2:
The patent establishes persistent WebSocket connections that remain open and active throughout the communication session, eliminating the need to repeatedly establish and tear down HTTP connections. This continuous connection enables real-time media content delivery and interaction without communication interruptions or overhead.
2Productivity
If web sockets are implemented to enable full-duplex communication, then communication efficiency improves, but constraints and limitations from web socket specification arise that require additional routing infrastructure
Solution Approach 1:
The patent introduces a second device acting as an intermediary with routing table functionality. This mediator manages the complexity of WebSocket connection routing by maintaining mapping between device identification codes and WebSocket connections, allowing first devices to communicate efficiently with application services without each device needing to manage complex routing logic independently.
Solution Approach 2:
The patent extracts the routing management functionality from individual devices and centralizes it in a dedicated second device. This separation allows the routing table to be maintained independently, reducing the complexity burden on communication endpoints while enabling efficient message routing through the centralized routing infrastructure.
3Reliability
If routing tables are used to direct communications through web sockets, then message delivery accuracy improves, but overhead from routing table lookups and management increases
Solution Approach 1:
The patent performs preliminary actions by establishing WebSocket connections and registering device identification codes in the routing table before actual media content communication begins. This pre-registration enables O(1) lookup complexity during message routing, significantly reducing routing decision time compared to dynamic routing methods while ensuring accurate message delivery.
Data Source
AI summary
Systems and methods are described herein for connecting client devices to applications on a server using web sockets. In one aspect, the systems and methods described provide for a routing table that may be used to direct communications between a client device and an application on a web server. The routing table may overcome challenges of implementing web sockets under current constraints of the web socket specification, the HTTP specification, and server implementations.