Terminal Device HTTP/3 and HTTP/2 Connection Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional communication devices fail to preferentially select a new communication protocol with higher speed when the communication destination device is compatible, leading to suboptimal communication performance.
Innovation Solution
A terminal device that establishes both HTTP/3 and HTTP/2 connections and uses HTTP/3 if the HTTP/3 connection is successfully established, allowing for efficient selection of a communication protocol based on compatibility and speed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a communication device uses a conventional communication protocol, then compatibility is ensured, but communication speed is reduced
Solution Approach 1:
The terminal device performs preliminary actions by starting processes for establishing both HTTP/3 and HTTP/2 connections simultaneously before actual communication begins. This allows the device to proactively determine protocol compatibility and select the optimal protocol (HTTP/3 for speed, HTTP/2 for compatibility) without sacrificing either communication speed or compatibility during the communication process.
2Adaptability or versatility
If a communication device establishes multiple connection processes, then protocol selection flexibility is improved, but device complexity increases
Solution Approach 1:
The connection establishment process is segmented into separate, independent processes for HTTP/3 and HTTP/2 protocols. Each protocol connection is established and managed independently, allowing the terminal device to handle multiple protocol connections without increasing overall system complexity. The device can select which connection to use based on establishment success, maintaining flexibility while keeping management straightforward.
Data Source
AI summary
A terminal device including: a controller; and a communicator that performs Hyper Text Transfer Protocol (HTTP) communication with a communication destination, wherein the controller starts processes for respectively establishing a first connection for using HTTP/3 and a second connection for using HTTP/2, and proceeds with communication using the HTTP/3 through the communicator if the first connection is successfully established.