Proxy DNS Resolution for SIP Message Forwarding

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

DNS name resolving by user agents in SIP communications can lead to delays due to limited bandwidth and increased communication time, especially when accessing hosts associated with host names or domain names in SIP messages.

Innovation Solution

A method where a proxy entity queries a Domain Name Server to obtain IP addresses associated with host names or domain names and includes these IP addresses in SIP messages before forwarding them, thereby eliminating the need for user agents to perform DNS queries, utilizing higher bandwidth access and reducing message length.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If the user agent performs DNS name resolving itself, then the user agent can independently resolve host names to IP addresses, but this leads to increased call setup time and delayed message processing due to limited bandwidth and additional communication overhead

Engineering Contradiction:

Improvecall setup timeVSAvoiduser agent independence

Core Design Contradiction:

Loss of timeVSEase of operation

Solution Approach 1:

The proxy entity performs DNS name resolving in advance by querying the DNS server for the host name contained in the SIP message before forwarding the message to the user agent. This preliminary resolution action eliminates the need for the user agent to perform DNS queries later, thereby reducing call setup time and message processing delay while maintaining system efficiency

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The proxy entity acts as an intermediary between the DNS server and the user agent. It receives the SIP message containing the host name, queries the DNS server on behalf of the user agent, obtains the IP address, and forwards the message with the resolved IP address to the user agent. This intermediary approach leverages the proxy's higher bandwidth access to accelerate DNS resolution

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If the user agent contacts the DNS server directly, then the user agent can obtain the IP address, but this increases communication time and consumes network resources due to limited bandwidth access

Engineering Contradiction:

Improvemessage processing speedVSAvoidnetwork resource consumption

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The proxy entity serves as an intermediary that consolidates DNS queries. Instead of multiple user agents individually querying the DNS server (which would consume significant network resources), the proxy entity performs the DNS query on behalf of multiple user agents, thereby reducing overall network resource consumption and improving message processing speed through its higher bandwidth access

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent combines multiple DNS resolution operations into a single query performed by the proxy entity. By merging the DNS resolution function at the proxy level, the system reduces redundant network communications and optimizes resource utilization, leading to faster message processing and reduced energy consumption

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS9313168B2Method and server entity for forwarding a message containing a host name or domain name in an internet based communications network

Publication Date: 2016.04.12 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

Method and server entity for forwarding a message containing a host name or domain name in an interne based communications network from a User Agent (UA) to the communications network or vice versa. The method comprises the steps of querying, by a proxy entity, a Domain Name Server (DNS) for obtaining from the Domain Name Server an Internet Protocol (IP) address associated with the host name or domain name, and including the Internet Protocol address in the message prior to forwarding the message to the communications network or User Agent, respectively, by the proxy entity.