Connectivity Detection via Third-Party Server Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Client computing devices and applications incorrectly determine Internet connectivity when a dedicated server for connectivity checks is down, leading to false negatives and disrupted interactions with third-party services, especially in scenarios involving proxy servers.

Innovation Solution

The solution involves sending a request to a third-party service and, upon receiving a response, attempting to contact a connectivity check server to verify Internet connectivity. If no response is received from the connectivity check server, it is assumed to be down, and if a response is received, it is verified whether it comes from the correct server; if not, the application concludes there is no connectivity and takes necessary steps.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the application contacts the dedicated server to check Internet connectivity, then the connectivity status can be determined, but false negatives occur when the dedicated server is down

Engineering Contradiction:
Improveconnectivity detection accuracyVSAvoidservice availability
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent introduces a third-party connectivity check server as an intermediary between the application and the Internet. Instead of relying solely on the dedicated server, the application uses this independent intermediary to verify connectivity status, thereby avoiding false negatives when the dedicated server is down.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a feedback mechanism where the application sends a request to the connectivity check server and processes the response to determine connectivity status. This feedback loop allows the application to accurately assess whether it has Internet access by analyzing the server's response or lack thereof.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If the application assumes no connectivity when the dedicated server is down, then false negatives are avoided, but actual connectivity is incorrectly detected as lost

Engineering Contradiction:
Improveconnectivity status accuracyVSAvoidservice interaction continuity
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent employs a simple, lightweight connectivity check mechanism that uses basic HTTP requests and response analysis. This disposable-like approach allows rapid connectivity verification without complex infrastructure, enabling quick determination of connectivity status and immediate resumption of service interactions.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Reliability

If the application continuously checks connectivity through the dedicated server, then connectivity status is monitored, but service interactions are disrupted during server outages

Engineering Contradiction:
Improveconnectivity monitoringVSAvoidservice accessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments the connectivity checking function from the dedicated server operations. By separating the connectivity verification task and assigning it to an independent third-party server, the system can monitor connectivity status without being affected by dedicated server outages, maintaining both monitoring reliability and service accessibility.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9692669B2Determination of internet access
Publication Date: 2017.06.27 ADOBE INC
  • US9692669B2 patent drawing
  • US9692669B2 patent drawing
  • US9692669B2 patent drawing

AI summary

Internet access or connectivity is determined by sending a request to a third-party service to which connectivity is desired with an application on a client computing device and responsive to receiving a response, attempting to rule out a false positive response from an entity other than the third-party service.