Webtop Hostname Pre-Resolution for Faster Resource Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing webtop systems experience delays and decreased performance due to high network latency and load during hostname resolution, leading to increased user response times and reduced predictability in accessing enterprise resources.

Innovation Solution

Implementing a method that determines hostname pre-resolution data based on user usage patterns and access policies, storing this data in a DNS resolver cache before resource access requests, allowing for immediate redirection to the corresponding server without waiting for DNS server responses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hostname resolution is performed through DNS server during resource access, then security and access control can be maintained, but response time increases and system performance decreases due to network latency

Engineering Contradiction:
Improveaccess controlVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs hostname resolution in advance by determining usage pattern data of users for the webtop and pre-resolving hostnames for frequently accessed resources before they are actually requested. This preliminary action stores resolution data locally, eliminating the need for real-time DNS queries during resource access, thus maintaining security while reducing response time.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If DNS resolution is performed for each resource access request, then accurate resource routing is achieved, but system load increases and performance predictability decreases

Engineering Contradiction:
Improveresource routing accuracyVSAvoidsystem performance
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system determines usage pattern data and identifies frequently accessed resources, then pre-resolves their hostnames and stores the resolution data locally. When users access these pre-resolved resources, the system can immediately redirect to the corresponding servers without performing DNS resolution at access time, thereby maintaining routing accuracy while significantly improving system performance and predictability.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If intermediary services are implemented for access regulation, then security and accessibility are improved, but network latency and response time increase

Engineering Contradiction:
ImprovesecurityVSAvoidaccess speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system performs hostname resolution in advance for frequently accessed resources based on usage patterns, storing the results locally. This preliminary action allows the intermediary service to quickly redirect users to resources without performing real-time DNS resolution, thereby maintaining security through controlled access while improving access speed by eliminating network latency associated with DNS queries.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12563012B2Managing webtop resource hostname resolution
Publication Date: 2026.02.24 F5 NETWORKS INC
  • US12563012B2 patent drawing
  • US12563012B2 patent drawing
  • US12563012B2 patent drawing

AI summary

Technology related to resolution of hostname for webtop resource access is disclosed. In one example, a method includes receiving request for accessing one or more resources from the webtop associated with the user. A usage pattern data of the user for the webtop is determined. For the requested resource, hostname pre-resolution data is determined based on the usage pattern data and an access policy before a given resource is requested for access. A response for the resource access request is generated based on the determined hostname pre-resolution data and the access policy. The response for the resource access request comprises an address of at least one corresponding backend server for redirecting the user to access the requested resource.