UPF DNS Query Redirection for Location-Based MEC Server Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing DNS query mechanisms in mobile edge computing networks often fail to select the optimal MEC server due to lack of UE location information, leading to suboptimal connections and user privacy concerns, and existing solutions like Session and Service Continuity modes are inadequate for changing IP addresses during ongoing TCP/IP connections.

Innovation Solution

Implementing a UPF with a MEC Support Function that detects DNS queries, replaces IP addresses using Network Address Translation, and interacts with the SMF to select and establish connections with optimal MEC servers, ensuring user privacy and efficient data routing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the UE sends DNS queries to the default DNS server without location-based selection, then the connection setup is simple, but the connection quality and latency are suboptimal

Engineering Contradiction:
Improveconnection qualityVSAvoidDNS selection mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a MEC Support Function (MSF) as an intermediary between the UPF and the DNS server. The MSF intercepts DNS queries, determines the UE's location, and redirects queries to appropriate MEC servers. This mediator resolves the contradiction by enabling intelligent DNS selection without requiring complex changes to the UE or DNS server infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary location-based DNS server selection before the actual data transmission begins. The UPF detects DNS queries early in the communication flow and proactively redirects them to the optimal MEC server based on UE location, avoiding the need for reconnection or retry mechanisms later.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If the system uses existing Session and Service Continuity modes to change IP addresses, then mobility is supported, but ongoing TCP/IP connections are disrupted

Engineering Contradiction:
ImproveIP address changing capabilityVSAvoidongoing connection stability
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent extracts the IP address translation function from the complex Session and Service Continuity mechanism and implements it directly in the UPF through Network Address Translation. This separates the location-based routing function from the connection management function, allowing IP addresses to be changed without disrupting TCP sessions.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system replaces the mechanical reconnection process required by traditional mobility management with a transparent Network Address Translation mechanism. The UPF automatically translates IP addresses in ongoing connections, substituting the need for TCP-level reconnection handshakes with a network-layer address translation process that occurs transparently to the application layer.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Speed

If the system redirects DNS queries to MEC servers based on UE location, then connection quality improves, but additional control messages and processing are required

Engineering Contradiction:
Improveconnection establishment speedVSAvoidcontrol plane messaging
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent combines multiple functions into the UPF: packet detection, location determination, DNS query redirection, and IP address translation. By merging these functions into a single network element, the system reduces the number of separate control plane messages and processing steps compared to a distributed architecture where each function resides in a separate component.

Inventive Principle:
Principle #5Merging (Combining)

4Stability of the object's composition

If the system implements transparent IP address translation in the UPF, then ongoing sessions remain stable, but the UPF requires enhanced functionality and processing capacity

Engineering Contradiction:
Improvesession continuityVSAvoidUPF functionality
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The UPF is designed with multi-functionality, serving as a universal network element that performs traditional routing, packet inspection, location-based DNS redirection, and Network Address Translation. This universal design consolidates multiple specialized functions into one device, managing complexity through integration rather than proliferation of separate components.

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

Data Source

PatentEP4221150B1System, apparatus and method to support data server selection
Publication Date: 2025.10.29 HUAWEI TECH CO LTD
  • EP4221150B1 patent drawingFigure 1
  • EP4221150B1 patent drawingFigure 2
  • EP4221150B1 patent drawingFigure 3

AI summary

A communication system includes a user plane function (UPF) configured to receive a domain name system (DNS) query from a user equipment (UE). The DNS query includes a first destination address of a first DNS server. The DNS query is for determining an address of a data server in proximity to the UE. According to the first destination address of the first DNS server, the UPF obtains, from a session management function (SMF), a second destination address of a second DNS server for providing the address of the data server. The SMF is configured to provide, to the UPF, the second destination address of a second DNS server.