Edge Platform Deployment Using DNS Location Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The shift to edge platforms in network-based computing creates challenges such as slow session transitions, inefficient resource use, and privacy issues in data communication between telecommunication network operators and content providers, leading to high latency and increased costs.

Innovation Solution

A system and method for managing content deployment that includes modifying DNS requests with location information to select the nearest edge platform, optimizing resource use, and ensuring user privacy by keeping client device location information within the network operator's components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If computing resources are concentrated at centralized data centers, then resource availability is sufficient, but network bandwidth consumption increases and processing efficiency decreases

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent segments computing resources from centralized data centers and distributes them to multiple edge platforms located at different network peripheries. This segmentation allows user data to be processed locally at the edge platform closest to the client device, reducing the need for long-distance data communication and thereby reducing network bandwidth consumption while improving processing efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by placing computing resources at distributed edge platforms throughout the network periphery rather than concentrating them centrally. Each edge platform provides localized processing capabilities, enabling data to be processed closer to where it is generated and consumed, which improves processing efficiency and reduces network bandwidth requirements.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If session transition between edge platforms is implemented, then user mobility is supported, but connection latency increases

Engineering Contradiction:
Improveuser mobility supportVSAvoidconnection latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by establishing a persistent session context that is maintained across edge platform transitions. When a user device moves from one edge platform to another, the new edge platform retrieves the existing session context rather than requiring a complete session re-establishment. This preliminary preparation of session information enables seamless handovers with minimal latency, supporting user mobility without significant connection delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a session management intermediary that facilitates smooth transitions between edge platforms. This intermediary component manages session state and coordinates the handover process, allowing user devices to switch between edge platforms without experiencing significant connection latency while maintaining adaptability to user mobility.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If more computing resources are added to edge platforms, then resource strain is reduced, but the distributed nature of edge computing is undermined

Engineering Contradiction:
Improveresource availabilityVSAvoidresource concentration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements universality by creating a unified session management system that operates across multiple distributed edge platforms. Rather than adding excessive resources to individual platforms, the system enables any edge platform to handle user sessions through standardized session context sharing. This multi-functional approach ensures resource availability is maintained across the distributed network without concentrating computing resources at any single location, preserving the fundamental distributed nature of edge computing.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Productivity

If user location data is shared with content providers, then service optimization is improved, but user privacy is compromised

Engineering Contradiction:
Improveservice optimizationVSAvoiduser privacy
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent extracts only the necessary location information needed for service optimization while removing sensitive personal identifiers. The system retrieves user device location data to determine the optimal edge platform for content delivery, but excludes other private user information from being shared with content providers. This selective extraction enables service optimization through location-aware routing while preserving user privacy by not exposing unnecessary personal data.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP4578176B1System and method for on-demand edge platform computing
Publication Date: 2026.04.22 GOOGLE LLC
  • EP4578176B1 patent drawingFigure 1
  • EP4578176B1 patent drawingFigure 2
  • EP4578176B1 patent drawingFigure 3

AI summary

Systems and methods for managing deployment of applications and services within a network having a plurality of edge platforms. A domain name service (DNS) request from a client device requesting for content from a third-party provider is modified to include location information indicating a client device location. A deployment manager uses the location information in the modified request to select a nearby edge platform for servicing the request. Changes to the edge platform servicing the request may be imitated based on changes in location information received in future requests. The deployment manager may also maintain a database to track resources that are already deployed in nearby edge platforms, conserving resources when selecting the edge platforms to service requests. The deployment manager also directs third-party content providers to the edge platform using a separate service so that communication with third-party content providers does not share the location information.