Domain Name Server Mediator for Publish-Subscribe Device Status Detection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

IP network devices cannot determine the status of publish/subscribe devices that are not directly visible or reachable, as they do not implement a publisher/subscriber interface, and conventional PING processes are ineffective for such devices, especially those behind firewalls or in non-IP networks.

Innovation Solution

A method and system that utilize a domain name server to receive status requests, map the device identifier to a publish/subscribe interface, and return a 'good' or 'bad' IP address based on the device's online status, allowing a PING process to determine the device's availability through a publish/subscribe interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional PING processes are used to determine device status, then IP network devices can detect availability of directly reachable devices, but IP devices cannot determine the status of publish/subscribe devices that are not directly visible or reachable

Engineering Contradiction:

Improvedevice status detection capabilityVSAvoidcompatibility with publish/subscribe devices

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a domain name server as an intermediary between IP network devices and publish/subscribe devices. The DNS server receives status requests, queries the publish/subscribe system for device availability, and returns appropriate IP addresses (either the actual device IP or a dummy IP indicating unavailability). This mediator enables IP devices to indirectly determine the status of publish/subscribe devices without direct communication capability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Loss of information

If publish/subscribe device availability data is made available through the publish/subscribe interface, then pub/sub devices can access status information, but devices that do not implement a publisher/subscriber interface (such as IP devices) cannot make use of this data

Engineering Contradiction:

Improveavailability data accessibilityVSAvoidcross-interface compatibility

Core Design Contradiction:

Loss of informationVSAdaptability or versatility

Solution Approach 1:

The domain name server acts as a translator or gateway between the publish/subscribe system and IP network devices. It receives standard DNS queries from IP devices, internally queries the publish/subscribe system for availability data, and converts the pub/sub status information into DNS-compatible responses (returning valid or dummy IP addresses). This enables information from the publish/subscribe interface to be accessed by non-pub/sub devices.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The domain name server performs multiple functions: it serves as a standard DNS resolver for IP devices, a client to the publish/subscribe system for status queries, and a protocol translator between these two different systems. This multi-functionality allows a single component to bridge the gap between incompatible interfaces.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS10666531B2Determining the status of a device through use of a publisher/subscriber interface

Publication Date: 2020.05.26 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A publish/subscribe interface is used to enable a non-publish/subscribe first system (such as an IP network device) to obtain status information about a publish/subscribe device that cannot be pinged by the first system. The first system sends a status request to a domain name server. The status request includes a domain name for the publish/subscribe device. Topic space maintained by a message broker in the publish/subscribe system includes status topics associated with publish/subscribe devices. The status topics contents reflect the current availability of the associated publish/subscribe device.