Mobile Device HTTP Request Top-Level Domain Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile communication devices often experience inconsistencies in accessing web sites and search results due to their location within wireless communication networks, leading to unexpected web sites and search results being received in response to user requests.
Innovation Solution
A mobile communication device associates a home wireless carrier identification with a list of top-level domains, selects a top-level domain based on the home carrier identification, and produces a Hypertext Transfer Protocol (HTTP) request with a Uniform Resource Locator (URL) that includes the selected top-level domain and a second-level domain, ensuring consistent access to web sites and search results regardless of location.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the mobile device uses the current network location to resolve domain names, then the device can access local services efficiently, but the user receives unexpected websites and search results that differ from their home network experience
Solution Approach 1:
The patent introduces a domain name resolution server as an intermediary between the mobile device and the internet. This server acts as a mediator that receives domain name resolution requests from the mobile device, determines the appropriate top-level domain based on the device's home network carrier identification, and returns the resolved domain name. This intermediary ensures that regardless of where the device is physically located, the resolution result consistently reflects the home network carrier's domain, thereby maintaining access consistency while still allowing network adaptability.
2Adaptability or versatility
If the mobile device allows free domain name resolution based on current location, then the device can adapt to local networks, but the user experience becomes inconsistent across different locations
Solution Approach 1:
The patent applies preliminary action by pre-establishing the association between carrier identifications and top-level domains in the domain name resolution server before the mobile device needs to access any website. The server maintains a pre-configured mapping that links home network carrier identifications to their corresponding top-level domains. When a resolution request arrives, the server retrieves the pre-stored association and uses it to determine the top-level domain, eliminating the need for real-time decision-making and ensuring consistent user experience across all locations.
3Device complexity
If the mobile device uses standard DNS resolution without carrier identification, then the resolution process is simple, but the device cannot maintain consistent carrier-specific domain access while roaming
Solution Approach 1:
The patent makes the domain name resolution server universal by enabling it to handle multiple functions: it processes standard DNS resolution requests, identifies the mobile device's home network carrier through carrier identification, determines the appropriate top-level domain based on carrier association, and returns the resolved domain name. This multi-functional server can serve multiple mobile devices from different carriers simultaneously, maintaining carrier-specific domain access reliability without requiring each device to implement complex carrier identification logic locally.
Data Source
AI summary
A mobile communication device is associated with a home wireless carrier that is identifiable by a home carrier identification stored in its memory. The mobile device also maintains a stored list of a plurality of carrier identifications, where each carrier identification is stored in association with one of a plurality of top-level domains. The mobile device reads the home carrier identification from the memory, and selects one of the plurality of top-level domains that is stored in association with the home carrier identification. During operation, the mobile device reads a specified domain name in response to a user-initiated request made via a Web browser or search application. Then, the mobile device produces a Hypertext Transfer Protocol (HTTP) request with a Uniform Resource Locator (URL) having the selected top-level domain and a second-level domain corresponding to the specified domain name. The HTTP request with the URL is submitted via the wireless communication network. Advantageously, consistency in accessing web sites, information, and/or search results may be achieved regardless of location of the mobile station.