Location-Based DNS Service Discovery for Large Networks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current DNS service discovery protocols, such as mDNS and WAB DNS-SD, face limitations in scalability and efficiency, particularly in large networks, as they either rely on manual router configurations or generate excessive network traffic, and lack granular location specificity for resources like printers.

Innovation Solution

Implementing a location-based DNS service discovery system using a central DNS server that aggregates network resources by geographic location, allowing devices to query for geo-specific service records through subnetwork addresses or subdomain names, thereby reducing unnecessary broadcasts and enhancing location-aware service discovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If mDNS multicast queries are used for service discovery, then automatic service discovery is enabled on local networks, but the range is limited to link-local networks and requires manual router configuration for larger networks

Engineering Contradiction:

Improveautomatic service discoveryVSAvoidnetwork range

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces a central DNS server as an intermediary to resolve service discovery requests across multiple subnetworks. Instead of relying on mDNS broadcasts that are confined to link-local networks, the DNS server mediates between clients on any subnetwork and service providers, enabling cross-subnetwork service discovery without manual router configuration.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the network service discovery function into two parts: local service registration with the DNS server, and centralized service resolution. This segmentation allows services to be discovered locally without requiring broadcast propagation across the entire network, while still enabling cross-subnetwork access through the DNS server.

Inventive Principle:

Principle #1Segmentation

2Loss of information

If mDNS service announcements are pushed to all network devices periodically, then service information is distributed across the network, but excessive network traffic is generated draining bandwidth and resources

Engineering Contradiction:

Improveservice information distributionVSAvoidnetwork bandwidth and resources

Core Design Contradiction:

Loss of informationVSLoss of energy

Solution Approach 1:

Instead of pushing service information to all devices (many-to-many broadcast), the system inverts the approach: devices pull service information from a central DNS server on demand (one-to-many retrieval). This eliminates unnecessary broadcasts and reduces network traffic to only what is actually needed by each device.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The patent implements a self-service model where network devices autonomously query the DNS server for service information they need, rather than passively receiving pushed announcements. Devices perform DNS lookups for services they wish to discover, eliminating the need for continuous or periodic broadcasts to all devices.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If WAB DNS-SD protocol is used for service discovery across subnetworks, then centralized DNS server is utilized, but manual device configuration is required and location specificity is lost

Engineering Contradiction:

Improvecross-subnetwork service discoveryVSAvoidmanual configuration requirement

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent performs preliminary action by pre-configuring the DNS server with service records and their associated subnetwork locations before any service discovery occurs. Service providers register their services with the DNS server in advance, including their subnetwork location information, so that clients can perform location-aware service discovery without any manual configuration.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system enables devices to automatically perform location-aware service discovery by querying the DNS server with their own subnetwork information. The DNS server automatically returns services appropriate to the client's location, eliminating the need for manual device configuration while maintaining location specificity.

Inventive Principle:

Principle #25Self-service

4Loss of information

If conventional DNS service discovery is used without location awareness, then service information is retrieved from central server, but granular location specificity for resources like printers is not provided

Engineering Contradiction:

Improveservice information retrievalVSAvoidlocation specificity

Core Design Contradiction:

Loss of informationVSMeasurement precision

Solution Approach 1:

The patent applies local quality by associating service records with specific subnetwork locations in the DNS server. Instead of a single global service list, the DNS server stores multiple service records with location qualifiers, allowing clients to retrieve services appropriate to their specific subnetwork location. This enables granular location specificity while maintaining centralized service information retrieval.

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS9917905B2Location-based domain name system service discovery

Publication Date: 2018.03.13 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

Systems and methods are provided for location-based Domain Name System (DNS) service discovery using a central DNS server in which network resources are aggregated by geographic location (e.g., subnets) and defined using DNS service discovery records that are mapped to corresponding geographic locations.