Multi-Interface HTTPS Traffic Distribution Controller
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless communication systems, terminals can only use one network interface for HTTPS sessions, preventing simultaneous data transfer over multiple networks like Wi-Fi and cellular networks, which limits traffic distribution and download performance for large content.
Innovation Solution
A terminal configuration with multiple network interfaces and a controller that generates TCP connections across these interfaces to manage HTTPS traffic distribution, allowing simultaneous data transfer over multiple networks based on content size thresholds.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a terminal uses a single network interface for HTTPS sessions, then security and protocol compatibility are maintained, but traffic distribution capability and download performance are limited
Solution Approach 1:
The patent segments HTTPS traffic into multiple parallel connections distributed across different network interfaces (e.g., Wi-Fi and cellular). Each interface handles a portion of the content download simultaneously, enabling traffic distribution while maintaining HTTPS security through separate SSL/TLS sessions per interface.
Solution Approach 2:
The patent transitions from single-interface sequential download to multi-interface parallel download by adding the network interface dimension. Multiple TCP connections are established across different physical interfaces, allowing simultaneous data transfer and improving overall download performance while maintaining protocol compatibility.
2Adaptability or versatility
If a terminal connects to multiple networks simultaneously, then traffic distribution is enabled, but protocol compatibility and session management complexity increase
Solution Approach 1:
The patent introduces a connection manager as an intermediary component that handles session management across multiple network interfaces. This mediator coordinates TCP connections and SSL/TLS sessions, distributing traffic appropriately while maintaining protocol compatibility and reducing management complexity through centralized control.
Solution Approach 2:
The patent creates a universal session management mechanism that works across different network interfaces (Wi-Fi, cellular, etc.) and protocol versions. The connection manager provides multi-functional capabilities including session establishment, traffic distribution, and protocol adaptation, enabling seamless operation across diverse network environments.
3Speed
If HTTPS sessions are used over multiple network interfaces, then data transfer rate increases, but session establishment overhead and processing complexity increase
Solution Approach 1:
The patent performs preliminary actions by pre-establishing TCP connections and SSL/TLS sessions across multiple network interfaces before actual content download begins. The connection manager proactively sets up these sessions in advance, reducing establishment overhead during the actual download process and enabling faster data transfer.
Solution Approach 2:
The patent maintains continuous useful action by keeping multiple TCP connections and SSL/TLS sessions active simultaneously across different network interfaces. Rather than establishing and tearing down sessions sequentially, the system maintains continuous parallel connections, eliminating session establishment delays and maximizing data transfer rate throughout the download process.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An embodiment of the present invention relates to a method and device for distributing traffic by a terminal in a wireless communication system, and the method according to an embodiment of the present invention comprises generating a first Security Socket Layer (SSL) connection through a first network interface with a server that provides content using Hypertext Transfer Protocol Security (HTTPS) if a HTTPS request is received from an application; generating a second SSL connection through a second network interface to the server based on information on the content; and receiving, through the first and second network interfaces, content data distributed and transmitted through the first and second SSL connections from the server.