5G ODoH Network Slicing for Secure Low-Latency DNS

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional DNS queries are not encrypted, leaving private information vulnerable to eavesdropping, and existing Oblivious DNS over HTTPS (ODoH) solutions require manual activation on individual devices, causing processing overhead and latency issues in networks like 5G.

Innovation Solution

Implementing ODoH within a 5G network by using a dedicated network slice for ODoH queries, managed by a network slice controller and carrier NAT device to handle obfuscation, eliminating the need for manual activation and optimizing network resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual activation of ODoH is implemented on individual devices, then DNS query privacy is improved, but device complexity and user configuration burden increase

Engineering Contradiction:
ImproveDNS query privacyVSAvoidmanual activation requirement
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically detects ODoH-capable devices and routes them through the ODoH slice without requiring manual user configuration. The network infrastructure itself performs the service of enabling privacy protection, rather than requiring users to manually activate it.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The network slice controller acts as an intermediary that automatically identifies ODoH-capable devices and directs their traffic through the appropriate encrypted slice, eliminating the need for direct user intervention while maintaining privacy protection.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If ODoH is implemented across the entire network, then DNS query security is improved, but network processing overhead and latency increase

Engineering Contradiction:
ImproveDNS query securityVSAvoidprocessing overhead and latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of applying ODoH encryption uniformly across all network traffic, the system applies encryption selectively only to traffic from ODoH-capable devices. This localized approach maintains security where needed while avoiding the overhead of encrypting all network traffic.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The network is segmented into multiple slices, with only the ODoH-specific slice implementing encrypted processing. This segmentation allows the network to maintain low-latency paths for non-ODoH traffic while providing enhanced security for ODoH traffic through dedicated encrypted resources.

Inventive Principle:
Principle #1Segmentation

3Productivity

If a dedicated ODoH network slice is created, then ODoH query handling is improved, but network infrastructure complexity increases

Engineering Contradiction:
ImproveODoH query handling efficiencyVSAvoidnetwork infrastructure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The ODoH network slice is designed to handle multiple functions including DNS query encryption, device capability detection, and automatic routing decisions. This multi-functionality reduces the need for separate specialized components, thereby managing infrastructure complexity while improving ODoH query handling efficiency.

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

Data Source

PatentUS20260067694A1Secure mobile networking using advanced DNS
Publication Date: 2026.03.05 T MOBILE INNOVATIONS LLC
  • US20260067694A1 patent drawing
  • US20260067694A1 patent drawing
  • US20260067694A1 patent drawing

AI summary

Embodiments of the present disclosure are directed to systems and methods for providing secure network communications, the system comprising a telecommunication network communicatively coupled to a user device, and one or more processors communicatively coupled to the telecommunication network, the one or more processors being configured to, receive a domain name system query from the user computing device, determine that the user computing device is associated with an Oblivious DNS Over HTTPS (ODOH) indicator, and cause transmission of the domain name system query through an ODOH specific slice of the plurality of network slices.