DNS-Based Remote Object Access via Intermediary Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for accessing remote programming objects are complex, technology-specific, and require significant infrastructure investment, limiting flexibility and ease of use.

Innovation Solution

A system utilizing Domain Name Service (DNS) to transmit requests for remote objects, receive IP addresses, and connect to them, with the option to use DNS Based Object Connection (DBOC) or other protocols like CORBA or Web Services, allowing for infrastructure-independent and flexible access without prior knowledge of the object's structure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional remote object access methods (COM, DCOM, OLE, CORBA, EJB) are used, then remote programming objects can be accessed, but the system becomes complex and requires significant infrastructure investment

Engineering Contradiction:
Improveremote object access capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces DNS servers as intermediaries between clients and remote objects. Instead of direct complex peer-to-peer connections required by traditional methods, clients query DNS servers to obtain connection information (IP addresses and ports) of remote objects. This intermediary layer simplifies the access mechanism while maintaining reliable remote object access capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent makes the existing DNS infrastructure multi-functional by enabling it to serve both traditional domain name resolution and remote object location services. By extending DNS record types (such as PO record) and utilizing existing DNS server capabilities, the system provides universal access to remote objects without requiring dedicated infrastructure, thereby reducing system complexity.

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

2Reliability

If traditional remote object access methods are implemented, then remote programming objects can be accessed, but significant infrastructure investment is required

Engineering Contradiction:
Improveremote object access capabilityVSAvoidinfrastructure investment
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent reuses existing DNS infrastructure for remote object location services. By extending the functionality of widely-deployed DNS servers to handle remote object queries (through new record types like PO records), the system eliminates the need for separate dedicated infrastructure, thereby maintaining reliable access while minimizing infrastructure investment.

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

Solution Approach 2:

The system enables clients to autonomously locate and connect to remote objects by querying DNS servers, without requiring centralized registration or management infrastructure. The DNS infrastructure itself serves the dual purpose of domain resolution and object location, making the system self-sufficient and reducing external infrastructure dependencies.

Inventive Principle:
Principle #25Self-service

3Reliability

If technology-specific methods (COM, DCOM, OLE, .Net, EJB, CORBA) are used for remote access, then remote objects can be accessed, but flexibility and ease of use are limited

Engineering Contradiction:
Improveremote object accessVSAvoidflexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal access mechanism that works across different programming paradigms and platforms. By using DNS as a technology-neutral location service, clients can access remote objects regardless of whether they use COM, DCOM, OLE, .Net, EJB, CORBA, or other protocols. The DNS-based approach provides a common interface that abstracts away technology-specific complexities, thereby enhancing flexibility while maintaining reliable access.

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

4Reliability

If traditional remote object access systems are deployed, then remote programming can be performed, but complex setup and prior knowledge of object structures are required

Engineering Contradiction:
Improveremote programming capabilityVSAvoidease of setup
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent enables automatic object location through DNS queries. Clients can autonomously resolve remote object locations by querying DNS servers with object identifiers, eliminating the need for manual configuration or complex setup procedures. This self-service mechanism significantly improves ease of operation while maintaining reliable remote programming capability.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary object location resolution through DNS queries before actual remote object access. By pre-resolving object locations and connection parameters through DNS, the system eliminates the need for complex runtime discovery or configuration, thereby simplifying operation while ensuring reliable access.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10469441B1Domain name service based remote programming objects
Publication Date: 2019.11.05 OPEN INVENTION NEWTORK LLC
  • US10469441B1 patent drawing
  • US10469441B1 patent drawing
  • US10469441B1 patent drawing

AI summary

The embodiments describe an apparatus for accessing a remote object. The apparatus includes a transceiver. The transceiver is configured to transmit a Domain Name Service request of the remote object to a Domain Name Service server and receive a Domain Name Service response comprising an Internet Protocol of the remote object. The transceiver is further configured to connect to the Internet Protocol of the remote object based on the Domain Name Service response.