EASDF Domain Partitioning for Roaming IP Address Conflicts

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In roaming scenarios involving edge computing, the allocation of private IP addresses by different PLMNs can lead to IP address duplication, causing conflicts in the Edge Application Server Discovery Function (EASDF) due to UEs using the same IP address for DNS requests, which complicates the identification and management of UE contexts.

Innovation Solution

Implementing an enhanced Edge Application Server Discovery Function (EASDF) that utilizes domain-specific identifiers, such as PLMN IDs or abstract roaming interface IDs, to differentiate and manage DNS contexts, ensuring that UEs with identical private IP addresses are handled by distinct EASDFs or partitions, thereby avoiding IP address conflicts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple UEs are allocated private IP addresses by different network elements in roaming scenarios, then edge computing services can be provided to multiple users, but IP address duplication occurs causing conflicts in edge application server discovery

Engineering Contradiction:
Improveedge computing service provisionVSAvoidIP address uniqueness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the edge computing service infrastructure by introducing domain-specific identifiers (such as PLMN IDs, EASDF IDs, or DNS domain names) that partition the service space. Each network element (EASDF, DNS server) is associated with specific domain identifiers, creating distinct service domains that prevent IP address conflicts while allowing multiple UEs to access edge computing services simultaneously.

Inventive Principle:
Principle #1Segmentation

2Reliability

If edge computing network elements are dedicated to specific network domains, then IP address conflicts are prevented, but network element selection complexity increases

Engineering Contradiction:
ImproveIP address conflict preventionVSAvoidnetwork element selection
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces domain-specific identifiers as intermediary elements that mediate between UEs and edge computing network elements. These identifiers (PLMN ID, EASDF ID, DNS domain names) serve as keys that automatically route requests to the appropriate network element without requiring complex selection logic, thereby maintaining simplicity while ensuring reliable conflict prevention.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If domain-specific identifiers are incorporated in DNS responses and EASDF context creation, then IP address disambiguation is achieved, but signaling overhead increases

Engineering Contradiction:
ImproveIP address disambiguationVSAvoidsignaling data
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent makes domain-specific identifiers multi-functional by using the same identifiers across multiple protocols and interfaces (DNS responses, EASDF context creation, NAF discovery, PDU session establishment). This universal approach avoids duplicating identification information in different formats, thereby achieving reliable IP address disambiguation while minimizing redundant signaling overhead.

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

Data Source

PatentEP4354828B1V-easdf in home routed roaming
Publication Date: 2026.04.29 NOKIA SOLUTIONS & NETWORKS OY
  • EP4354828B1 patent drawingFigure 1A~1B
  • EP4354828B1 patent drawingFigure 2A~2B
  • EP4354828B1 patent drawingFigure 3A~3B

AI summary

An apparatus, in an edge computing related network element, is provided, which comprises at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receiving a request to create a context for serving a session for a user equipment, the request including information indicating a network domain of applicability of the user equipment, and answering to the request with addressing information depending on the network domain of applicability received in that request.