DNS-Based Home Domain Identification for Roaming Wireless Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wireless communication technologies face challenges in identifying the home domain of multi-mode devices roaming between conventional and IP-based or SIP-based networks, leading to issues during registration and call setup, as they often lack the necessary domain name information, resulting in incorrect domain assignment and impaired call-back capabilities.

Innovation Solution

A method and system that utilize a remote information processing system, such as a DNS server, to retrieve and determine the domain name associated with a device's unique identifier, allowing for efficient domain name determination and translation of conventional IDs into URIs for IP-based systems, thereby facilitating seamless roaming and call setup across different network types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a gateway uses a single host name to identify all call originators in a conventional wireless network, then the configuration is simple, but the domain name assignment becomes incorrect when devices from other domains roam into the network

Engineering Contradiction:
Improvegateway configuration simplicityVSAvoiddomain name identification accuracy
Core Design Contradiction:
Ease of manufactureVSMeasurement precision

Solution Approach 1:

The patent introduces a Domain Name System (DNS) server as an intermediary between the gateway and the domain name information. Instead of hardcoding domain names in the gateway, the system queries the DNS server to dynamically resolve domain names based on device identifiers (IMSI, UFMI). This mediator enables accurate domain name assignment for both home devices and roaming devices without complicating gateway configuration.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-configuring domain name mappings in the DNS server before roaming devices arrive. When a device roams into the network, the gateway queries the DNS server which already contains the necessary domain name information, eliminating the need for complex real-time domain determination logic in the gateway itself.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If the gateway queries DNS for each individual device registration, then accurate domain name identification is achieved, but the number of DNS queries increases significantly

Engineering Contradiction:
Improvedomain name identification accuracyVSAvoidregistration processing efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent implements partial action by querying the DNS server only when necessary - specifically when a device roams into the network or when domain name information is not already cached. For devices already registered or home devices, the gateway uses cached information or simple local identification, avoiding unnecessary DNS queries. This selective approach maintains accuracy while improving efficiency.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary DNS queries for identifier ranges before devices actually need registration. By pre-resolving domain names for groups of devices (based on IMSI or UFMI ranges), the gateway can serve multiple devices without repeated DNS lookups, reducing overall query volume while maintaining accurate domain name assignment.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If identifier translation is performed using the gateway's domain name, then call setup is simplified, but call-back functionality fails for roaming devices

Engineering Contradiction:
Improvecall setup simplicityVSAvoidcall-back capability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The DNS server acts as a mediator that provides the correct domain name for identifier translation. When a roaming device originates a call, the gateway queries the DNS server using the device's identifier (IMSI/UFMI) to obtain the device's home domain name. This ensures that the call setup uses the correct domain for routing, and call-back functionality works properly because the target device can route calls back to the correct home domain using the same DNS resolution mechanism.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8244885B2Using domain name service for identifying a home domain of a roaming device
Publication Date: 2012.08.14 MOTOROLA SOLUTIONS INC
  • US8244885B2 patent drawing
  • US8244885B2 patent drawing
  • US8244885B2 patent drawing

AI summary

A method, information processing system, and wireless communication network determine a domain name associated with at least one device for providing services to the at least one device in a network. A service request (604) that includes a unique identifier associated with at least one device (102) is received. A query of a remote information processing system (218) is issued for retrieving a plurality of identifier ranges (610). Each of the identifier ranges is associated with one of a plurality of domain names. An identifier range comprising at least the unique identifier associated with the at least one device (102) is identified in the plurality of identifier ranges (614). A domain name associated with the identified identifier range is determined (616). The domain name that has been determined is associated with the at least one device (102).