Dynamic Mobile Network Timeout Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices face challenges in selecting optimal timeout values for network operations, as low values lead to erroneous timeouts and high values result in user delays, without a method to balance these effectively.

Innovation Solution

A system that determines timeout values for mobile devices based on analytics data from a database, considering network provider, connection type, device type, geographic area, and operation type, to optimize the balance between minimizing erroneous timeouts and user delays.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If a low timeout value (e.g., 0.25 seconds) is configured for the mobile device, then the amount of time spent waiting for a response before timing out is reduced, but a greater amount of network operations are erroneously timed out

Engineering Contradiction:
Improvewait time for network operation responseVSAvoidaccuracy of timeout detection
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The timeout value is made dynamic rather than static. The system continuously monitors network conditions, operation types, and device states to adjust the timeout value in real-time. This allows the timeout to adapt to changing conditions, reducing both erroneous timeouts and unnecessary waiting time.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The timeout parameter is changed based on multiple factors including operation type, network conditions, device state, and historical data. By modifying this single parameter dynamically based on contextual information, the system resolves the contradiction between fast timeout and accurate timeout detection.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If a high timeout value (e.g., 2.5 seconds) is configured for the mobile device, then the amount of network operations erroneously timed out is reduced, but the mobile device waits too long before timing out a network operation causing noticeable delays to the user

Engineering Contradiction:
Improveaccuracy of timeout detectionVSAvoiduser perceived delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The timeout value adjusts dynamically based on the specific operation type and current network conditions. Critical operations receive shorter timeouts while less time-sensitive operations can tolerate longer timeouts, resolving the contradiction between reliability and user perceived delay.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Different timeout values are applied to different network operations based on their specific requirements. Instead of using a single global timeout value, the system applies localized timeout settings tailored to each operation type, network condition, and device state.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8971908B1Apparatus and method for configuring network connection parameters of a mobile device
Publication Date: 2015.03.03 GOOGLE LLC
  • US8971908B1 patent drawing
  • US8971908B1 patent drawing
  • US8971908B1 patent drawing

AI summary

According to some embodiments of the present disclosure, techniques for determining a timeout value for a mobile device are disclosed. The techniques include receiving a request for a timeout value from a mobile device. The request includes a current network provider identifier and a first current connection type identifier. The techniques further include accessing an analytics database that stores a plurality of realized latency values, each realized latency value corresponding to a different previously performed network operation. Each realized latency value has a network provider identifier indicating a network provider and a connection type identifier indicating a type of associated therewith. The techniques further include retrieving one or more of the plurality of realized latency values from the analytics database based on the current network provider identifier and the first connection type identifier. The techniques also include determining the timeout value based on the retrieved realized latency.