IoT Gateway Local Proxy for Service Discovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In IoT deployments, conventional service discovery mechanisms lead to resource consumption and latency due to frequent requests between IoT gateways and service discovery servers, and they tightly couple applications to specific service discovery solutions, reducing portability and requiring developers to learn different APIs.

Innovation Solution

Implementing a local service discovery agent within the IoT Gateway that retrieves and stores endpoint information from service discovery servers, allowing it to provide this information locally and decoupling applications from specific service discovery solutions, thus reducing network queries and enhancing portability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If service endpoint information is retrieved dynamically from a service discovery server, then the endpoint information is always up-to-date, but network bandwidth is consumed and latency increases due to frequent requests

Engineering Contradiction:
Improveendpoint information freshnessVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements a service discovery agent that performs preliminary service discovery operations and caches endpoint information locally. Instead of dynamically querying the service discovery server every time a service is needed, the agent proactively retrieves and stores endpoint information in advance, allowing microservices to access cached data without incurring network overhead.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a distributed caching mechanism where each IoT gateway maintains local service discovery information. This localizes the service discovery function, allowing endpoints to be resolved from local cache rather than requiring remote server queries, thereby reducing network bandwidth consumption while maintaining information freshness through selective updates.

Inventive Principle:
Principle #3Local quality

2Reliability

If service endpoint information is retrieved dynamically, then the system adapts to service changes, but time is lost due to request-response cycles between IoT gateway and service discovery service

Engineering Contradiction:
Improveservice adaptation capabilityVSAvoidservice discovery latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The service discovery agent performs service discovery operations in advance and maintains a local cache of endpoint information. When microservices need to access other services, they query the local cache instead of initiating request-response cycles with remote discovery servers, dramatically reducing service discovery latency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a service discovery agent as an intermediary component between microservices and the remote service discovery server. This agent maintains local cached information and handles service resolution requests, eliminating the need for direct time-consuming communication between microservices and remote servers while preserving adaptation to service changes.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If applications directly use service discovery solutions, then they can access service endpoints, but they become tightly coupled to specific service discovery implementations, reducing portability

Engineering Contradiction:
Improveservice access capabilityVSAvoidapplication portability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The service discovery agent acts as an intermediary layer that abstracts the service discovery mechanism from microservices. Applications interact with the agent through a standardized interface to access service endpoints, while the agent handles the implementation-specific logic of communicating with different service discovery servers. This decoupling allows applications to remain portable across different service discovery implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The service discovery agent provides a universal interface for service access that works across different service discovery implementations. By consolidating the service discovery logic in the agent and providing a standardized access mechanism, the system enables applications to access services without being tied to specific service discovery solution APIs or implementations.

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

4Ease of operation

If developers use specific service discovery APIs, then they can access service endpoints, but they must learn different APIs for different solutions, increasing complexity

Engineering Contradiction:
Improveservice endpoint accessVSAvoidAPI learning curve
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The service discovery agent serves as an intermediary that provides a unified, standardized API for accessing service endpoints. Developers interact with this consistent interface regardless of which underlying service discovery solution is being used, eliminating the need to learn multiple different service discovery APIs and reducing operational complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10469600B2Local Proxy for service discovery
Publication Date: 2019.11.05 DELL PROD LP
  • US10469600B2 patent drawing
  • US10469600B2 patent drawing
  • US10469600B2 patent drawing

AI summary

Systems and methods for a local proxy for service discovery. In some embodiments, an Internet-of-Things (IoT) gateway may include: a processor; and a memory coupled to the processor, the memory including program instructions stored thereon that, upon execution by the processor, cause the IoT gateway to: retrieve, by a service discovery agent, endpoint information maintained by a service discovery server remotely located with respect to the IoT gateway; store the service endpoint information in the memory; receive a service request aimed at a service endpoint; and provide the service endpoint information, from the memory, in response to the service request.