Directory Server Mediator for RPC Service Discovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Client systems face challenges in automatically discovering RPC services on different or additional RPC servers without additional configuration, limiting scalability and service availability.

Innovation Solution

Registering information about RPC servers and interface definitions on a directory server, allowing client systems to query and execute RPC services on available servers using the registered information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If RPC services are provided on pre-specified RPC server systems according to pre-specified RPC interfaces, then the client system can execute the service by sending the RPC request to the RPC server system, but the client system cannot automatically discover the availability of services on different RPC servers without additional configuration

Engineering Contradiction:
ImproveService discovery capabilityVSAvoidConfiguration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

A directory server is introduced as an intermediary component between client systems and RPC server systems. The directory server maintains a database of RPC service availability information and provides query interfaces for clients to discover services without direct configuration of multiple servers. This mediator enables automatic service discovery while simplifying the client's operational complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The directory server provides universal access to RPC service discovery functionality across different server systems. Instead of requiring clients to be configured for specific servers, the directory server serves multiple clients and multiple server systems through a standardized query interface, enabling universal service discovery capability.

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

2Adaptability or versatility

If the same service is provided on different RPC servers for scaling, then service availability and scalability are improved, but the client systems require additional configuration to indicate the RPC servers on which each RPC service is accessible

Engineering Contradiction:
ImproveService scalabilityVSAvoidClient configuration requirement
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The directory server acts as a mediator that automatically maintains and publishes service availability information across multiple RPC servers. When services are deployed on different servers for scaling, the directory server records this information and makes it accessible to clients through queries, eliminating the need for clients to be manually configured for each server.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service discovery where clients automatically query the directory server to find available services and servers without requiring manual configuration. The directory server autonomously maintains the service registry, allowing clients to discover and select services dynamically based on availability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7366734B2Enabling client systems to discover services accessible by remote procedure calls (RPC) on server systems
Publication Date: 2008.04.29 ORACLE INT CORP
  • US7366734B2 patent drawing
  • US7366734B2 patent drawing
  • US7366734B2 patent drawing

AI summary

Information representing the RPC servers on which each RPC service is currently being provided, is maintained on a directory server. A client may query the directory server and determine a specific one of the RPC servers on which to cause execution of a desired RPC service. Each RPC server may also register the service interface using which the corresponding RPC services can be accessed. As a result, the same RPC service may potentially be accessed with a different service interface on different RPC servers. Another aspect of the present invention provides a schema using which procedure interface definition (i.e., the name of the procedure, the parameters and their attributes) can be represented. Such a feature is used to store the procedure definitions on the directory server, thereby enabling a client system to determine the procedure definition prior to sending an RPC request to execute the procedure.