Client Device Connection Establishment via Multi-Protocol Requests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client devices often face connectivity issues when defaulting to Wi-Fi networks that are not connected to the Internet or restrict certain communication protocols, leading to 'dead hotspots' and impaired video streaming, while cellular networks may be more reliable but costly.
Innovation Solution
A method where a client computer attempts to connect to a server by transmitting multiple requests with varying differences, such as protocols or access points, to determine the most optimal connection for communication, ensuring connectivity and protocol compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If the client device defaults to Wi-Fi network connection, then connection cost is reduced and local network access is improved, but Internet connectivity reliability deteriorates and protocol compatibility is restricted
Solution Approach 1:
The system performs preliminary actions by transmitting multiple connection requests with different protocols (TCP, UDP, HTTP, HTTPS) simultaneously or in rapid succession before actual data transfer begins. This allows the system to pre-determine which protocol-path combination will work reliably, avoiding later connectivity failures and the need to switch networks during active communication.
Solution Approach 2:
The invention changes communication parameters by varying protocols (TCP/UDP, HTTP/HTTPS) and transmission paths across multiple attempt requests. By modifying these parameters systematically, the system can adapt to different network conditions and restrictions, finding a working configuration even when default Wi-Fi settings fail due to protocol blocking or connectivity issues.
2Speed
If the client device uses Wi-Fi network connection, then connection speed is improved, but protocol compatibility deteriorates due to restricted communication protocols
Solution Approach 1:
The connection establishment process is segmented into multiple independent attempt requests, each using a different protocol combination. Instead of relying on a single protocol that may be restricted, the system divides the connection task into separate TCP-based and UDP-based attempts, allowing video streaming traffic to potentially bypass protocol restrictions by using alternative pathways.
Solution Approach 2:
The client device implements multi-functionality by supporting multiple communication protocols (TCP, UDP, HTTP, HTTPS) and being capable of switching between them. This universal approach ensures that regardless of which protocol is restricted or blocked by the Wi-Fi network, the device can fall back to an alternative protocol that maintains both speed and compatibility.
3Reliability
If the client device transmits multiple connection requests with different protocols, then connection reliability is improved, but device complexity increases
Solution Approach 1:
The system implements self-service by automatically managing the complexity of multiple protocol attempts without requiring user intervention. The client device autonomously transmits various connection requests, monitors their success or failure, and selects the working protocol-path combination, thereby improving reliability while keeping the user experience simple and unchanged.
Solution Approach 2:
The connection establishment process incorporates feedback mechanisms where the system monitors the outcome of each protocol attempt and uses this information to guide subsequent connection decisions. Based on feedback from successful or failed attempts, the system can adjust its protocol selection strategy, avoiding known failing paths and prioritizing working configurations for future connections.
Data Source
AI summary
One example includes transmitting a first request for data from a client device to a server, transmitting a second request for the data from the client device to the server, wherein the second request is transmitted prior to receiving a response to the first request, and receiving the data from the server at the client device responsive to the second request being sent from a different access point than an access point used to send the first request.