Stream-Aware Connection Maintenance for HTTP/2
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication technologies, such as those using HTTP/2, face inefficiencies in maintaining connections when multiple streams are established, leading to unnecessary communication as they do not effectively manage connection maintenance across independent streams.
Innovation Solution
A communication device and system that include a determination unit to identify no-communication time periods and a connection maintenance unit to send messages for maintaining connections only when necessary, using a PING frame to prevent connection timeouts, thereby reducing unnecessary communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If connection maintenance packets are sent for all streams in a connection, then connection stability is improved, but unnecessary communication increases
Solution Approach 1:
The patent applies local quality by differentiating connection maintenance treatment between streams that have active timers and those that don't. Only streams without active timers receive connection maintenance packets, creating a localized, targeted approach rather than uniform treatment of all streams. This resolves the contradiction by maintaining reliability where needed while eliminating unnecessary communication in streams that already have active maintenance mechanisms.
Solution Approach 2:
The patent implements partial action by sending connection maintenance packets to only some streams (those without active timers) rather than all streams in a connection. This partial approach prevents excessive communication while still ensuring connection stability for streams that require it, directly resolving the contradiction between reliability and energy loss.
2Reliability
If connection maintenance is performed frequently, then connection stability is improved, but communication overhead increases
Solution Approach 1:
The patent implements self-service by allowing streams with active timers to autonomously maintain their own connections without requiring additional maintenance packets from the server. This self-maintenance mechanism reduces communication overhead while preserving connection stability, as the timer-based streams independently manage their own connection health.
Solution Approach 2:
The patent uses feedback mechanisms where the server monitors which streams have active timers and adjusts connection maintenance packet transmission accordingly. This feedback loop prevents excessive communication by only sending maintenance packets when actually needed, resolving the contradiction between reliability and communication overhead.
3Speed
If connection timeout thresholds are shortened, then connection responsiveness is improved, but false disconnections increase
Solution Approach 1:
The patent applies preliminary action by sending connection maintenance packets before timeout thresholds are exceeded. This proactive approach maintains connections that would otherwise be at risk of timeout, preventing false disconnections while preserving responsive connection management. The maintenance packets are sent in advance to keep the connection alive.
Solution Approach 2:
The patent implements beforehand cushioning by using connection maintenance packets as a protective measure against premature timeout disconnections. This cushioning mechanism buffers against the harsh timeout thresholds, allowing shorter thresholds to be used for responsiveness while the maintenance packets prevent false disconnections from occurring.
Data Source
AI summary
When, in communication using a protocol in which at least two streams are established over a connection, a notification that a new stream will be reserved is made, a process for preventing a non-communication state exceeding a predetermined amount of time is initiated and a frame is sent at least every predetermined amount of time in the case where there is no other stream currently reserved, whereas processing is ended without initiating the stated process in the case where there is already a reserved stream.