Retransmission Timer Configuration via Handshake Parameters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current machine-to-machine (M2M) communication techniques face challenges in setting optimal retransmission timers, leading to congestion and latency issues due to inappropriate wait time settings, which affect the performance of time-sensitive applications and degrade network security.
Innovation Solution
A method for dynamically configuring retransmission timers based on derived retransmission parameters from handshake messages, considering device and environment characteristics, to adjust wait times for both client and server devices, thereby optimizing handshake processes and reducing network congestion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If fixed wait time settings are used in retransmission timers, then device complexity is reduced, but communication efficiency deteriorates due to congestion and latency issues
Solution Approach 1:
The patent implements dynamic retransmission timer configuration where the server adjusts wait times based on derived retransmission parameters from handshake messages. Instead of using fixed wait time values, the system adapts the retransmission timer settings to match specific device capabilities and environmental conditions, thereby optimizing communication efficiency without excessive complexity
Solution Approach 2:
The server derives retransmission parameters from handshake messages and uses these parameters to configure appropriate wait times. This parameter-based approach allows the system to adjust retransmission timing dynamically based on device characteristics and network conditions, resolving the contradiction between simplicity and efficiency
2Object-generated harmful factors
If longer wait times are set in retransmission timers, then network congestion is reduced, but latency increases affecting time-sensitive applications
Solution Approach 1:
The system derives retransmission parameters from handshake messages that contain information about device capabilities and environmental conditions. Based on these parameters, the server configures optimized wait times that balance congestion reduction with latency requirements, rather than using universally long wait times
Solution Approach 2:
The patent applies different wait time configurations tailored to specific device types and environmental conditions. Each client receives customized retransmission parameters based on its characteristics, allowing optimal performance for time-sensitive applications while still preventing congestion in appropriate scenarios
3Loss of time
If shorter wait times are set in retransmission timers, then latency is reduced for time-sensitive applications, but network congestion increases
Solution Approach 1:
The server derives retransmission parameters from handshake messages and configures wait times that are optimized for each specific client device. This parameter-driven approach allows the system to use shorter wait times when appropriate (reducing latency) while avoiding congestion by adjusting parameters based on network conditions and device capabilities
4Device complexity
If generic retransmission timer settings are used, then device complexity is reduced, but communication security deteriorates
Solution Approach 1:
The server derives retransmission parameters from handshake messages that contain device-specific information. These parameters are used to configure secure and optimized wait times for each client, rather than using generic settings. This approach maintains security by tailoring configurations to specific devices while avoiding excessive complexity
Solution Approach 2:
The system dynamically configures retransmission timers based on derived parameters from each handshake, creating adaptive security configurations that match specific device and environmental conditions rather than relying on static generic settings
Data Source
AI summary
The present techniques generally describe a machine-implemented method for configuring a retransmission timer, the method performed at the server including: receiving, from a client, a first handshake message as part of a first handshake with the client; deriving a retransmission parameter from the first handshake message; setting a first wait time of the retransmission timer based on or in response to the retransmission parameter.