DNS View Traffic Steering for Dynamic UE IP Prefix Changes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing DNS traffic steering techniques in edge cloud scenarios are unable to implement user group-based traffic steering due to the lack of access to forwarding components, leading to static and inflexible configurations that do not adapt to changing IP assignments of users and groups.

Innovation Solution

A method that updates network prefixes assigned to DNS views in response to user equipment connecting or disconnecting from a network gateway, enabling dynamic traffic steering based on updated IP addresses and user policies, without requiring tight integration with core user plane nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If DNS traffic steering uses static configuration, then implementation is simple, but it cannot adapt to changing IP assignments of users and user groups

Engineering Contradiction:

Improveadaptability to changing IP assignmentsVSAvoidcomplexity of DNS configuration

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent transforms static DNS configuration into dynamic operation by automatically updating DNS views when UEs connect or disconnect from network gateways. The system monitors UE presence and dynamically assigns or removes network prefixes from DNS views, enabling the DNS traffic steering to adapt to changing IP assignments without manual reconfiguration.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where the DNS server receives information about UE connection status from network gateways and automatically adjusts the DNS view configuration accordingly. This feedback loop ensures that DNS traffic steering always reflects the current state of UE assignments, enabling continuous adaptation to network changes.

Inventive Principle:

Principle #23Feedback

2Measurement precision

If a dedicated forwarding component is defined to implement granular traffic steering, then traffic steering precision is improved, but it requires tight integration with core user plane nodes which is not available in loosely coupled edge cloud scenarios

Engineering Contradiction:

Improveprecision of traffic steeringVSAvoidintegration complexity with core network

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The patent introduces DNS as an intermediary component that enables traffic steering without requiring direct integration with core user plane nodes. By using DNS views to map network prefixes to server IP addresses, the system achieves granular traffic steering at the application layer, eliminating the need for deep integration with underlying network infrastructure while maintaining steering precision.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If existing DNS traffic steering techniques are used, then implementation is straightforward, but they are unable to follow changing IP assignments of users and groups

Engineering Contradiction:

Improveability to follow changing IP assignmentsVSAvoidreliability of traffic steering

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by proactively updating DNS views when UEs connect or disconnect from network gateways, before traffic routing decisions need to be made. This proactive approach ensures that DNS traffic steering is always up-to-date with current UE assignments, maintaining high reliability without waiting for traffic flow to trigger updates.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12615232B2Network traffic management

Publication Date: 2026.04.28 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

There is provided a method performed by an entity for managing traffic between a network gateway and an application server. In response to a user equipment (UE) connecting to or disconnecting from the network gateway, a network prefix assigned to a DNS view is updated (102). The network prefix comprises one or more internet protocol (IP) addresses that each identify a UE that is connected to the network gateway and to which the DNS view is accessible. Traffic between the network gateway and the application server is steered according to the DNS view to which the updated network prefix is assigned.