HTTP/2 Server Push for Real-Time IoT Resource Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current HTTP protocols, such as HTTP/1.1, are inefficient for handling dynamic applications like near real-time stock quotes, as they rely on a pull model, leading to high latency and bandwidth inefficiencies, particularly in IoT scenarios where asynchronous events need to be notified promptly.
Innovation Solution
Implementing HTTP/2 with its built-in server push mechanism, bidirectional communication, and prioritization of streams, along with methods like persistent connections and WebSocket protocol, to enable efficient server-initiated communication and resource monitoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If periodic polling is used to ensure clients are informed of server events, then response latency is reduced, but bandwidth efficiency deteriorates due to unnecessary client-server exchanges
Solution Approach 1:
The patent inverts the traditional client-pull model by implementing server-push capability through HTTP/2. Instead of clients periodically polling servers to check for events, the server proactively pushes event notifications to clients when events occur. This is achieved through HTTP/2 server push mechanism where the server can send responses without waiting for client requests, fundamentally reversing the communication initiative from client-pull to server-push.
Solution Approach 2:
The patent applies preliminary action by establishing persistent HTTP/2 connections and stream reservations in advance. Clients pre-reserve streams for receiving push notifications, and servers prepare to push events immediately when they occur without waiting for client requests. This pre-establishment of communication channels eliminates the need for repeated connection setup and polling actions.
2Loss of time
If HTTP/1.1 persistent connections are used to reduce connection overhead, then connection establishment time is reduced, but the protocol still cannot support server-initiated communication
Solution Approach 1:
The patent makes the HTTP connection universally applicable for both client requests and server pushes by leveraging HTTP/2's bidirectional stream-based architecture. A single persistent TCP connection carries both client-to-server requests and server-to-client push notifications simultaneously through different streams. This multi-functional use of the same connection eliminates the need for separate connections for different communication directions.
Solution Approach 2:
The patent transitions from HTTP/1.1's single-directional request-response model to HTTP/2's multi-dimensional stream-based model. While HTTP/1.1 persistent connections maintain a single communication lane, HTTP/2 opens multiple parallel streams within the same connection, allowing clients and servers to independently initiate and receive multiple simultaneous exchanges in both directions without interfering with each other.
Data Source
Figure 1A~1B
Figure 2
Figure 3
AI summary
Methods are described that can enable resource monitoring over HTTP/2. These methods may rely on using multiple streams over persistent connections and on the HTTP/2 Push mechanism. Furthermore, a mechanism is proposed that can enable resource monitoring over multiple servers.