URL Restructuring for Distributed Cache Lookup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Distributed caching systems face inefficiencies in retrieving object data due to slow HTTP redirecting and increased latency, which hinders fast data access and load balancing across multiple caches.
Innovation Solution
The method involves restructuring URLs to create a hierarchical naming architecture, allowing DNS servers to efficiently direct users to the appropriate cache by removing the domain name, replacing slashes with dots, reversing the order, and appending the domain name, enabling faster DNS lookup and reduced latency in retrieving object data from distributed caching systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If object data is distributed across multiple caches with HTTP redirecting, then data can be retrieved from optimal cache locations, but retrieval latency increases due to multiple redirects
Solution Approach 1:
The patent introduces an intermediary component (URL restructuring module) that transforms the original URL into a hierarchical format before DNS lookup. This intermediary processing enables the DNS system to directly resolve the optimal cache location without requiring multiple HTTP redirect steps, thereby reducing retrieval latency while maintaining accurate data retrieval from the correct cache location.
Solution Approach 2:
The patent performs preliminary URL restructuring into a hierarchical naming architecture before the actual data retrieval process begins. By pre-processing the URL to encode cache location information in a DNS-friendly format, the system prepares the request in advance to bypass multiple redirect steps, thus reducing retrieval latency while ensuring the request reaches the correct cache.
2Productivity
If object data is distributed across multiple caches, then load balancing is improved, but system complexity increases due to URL management
Solution Approach 1:
The patent changes the parameter structure of URLs by transforming them into a hierarchical naming architecture. Instead of using traditional flat URLs requiring complex redirect logic, the system encodes cache location information directly into the URL hierarchy (e.g., domain.subdomain.object), which simplifies URL management while enabling efficient load balancing across distributed caches.
Solution Approach 2:
The patent segments the URL into hierarchical components that correspond to different levels of the cache structure. By dividing the URL into domain, subdomain, and object segments, each representing a specific cache hierarchy level, the system simplifies URL management and enables straightforward load balancing without complex redirect logic.
3Adaptability or versatility
If conventional UEs are used without URL restructuring capability, then device compatibility is maintained, but DNS lookup efficiency is reduced
Solution Approach 1:
The patent implements a universal URL restructuring mechanism that works across different device types and UE capabilities. The restructuring is performed by the server or proxy before the request reaches the UE, making the hierarchical URL format universally compatible with all DNS systems and devices while maintaining fast lookup speeds through the structured format.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Method and arrangement for retrieving object data. A method performed by a communication network node 204 of enabling retrieval of an object, such as an element of web-page, is provided. The location of the 5 object is defined by a Uniform Resource Locator, URL, in a distributed caching system 200. The method comprises restructuring 2:1 the URL into a format being readable by a DNS server, and sending 2:2 a DNS query comprising the restructured URL to the DNS server 206. Furthermore, the method comprises receiving 2:3 an IP -address of a cache 202a, 202b, 202c in the distributed caching system 200, wherein the cache 202a, 202b, 202c stores the object. Moreover, the method comprises sending 2:4 an http -get request for the object to the cache 202a, 202b, 202c having the received IP-address, and receiving 2:5 an http-response comprising the object from the cache 202a, 202b, 202c. By providing DNS-servers with information of objects' locations, and restructuring URLs into a format which is readable by the DNS-servers, end users may make use of the fast looking up capability of the DNS-servers for finding objects' locations.