Augmented Object Interface for Distributed RPC Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Remote Procedure Call (RPC) methods in distributed systems are inadequate for handling time-critical data transfers and are not universally supported across various devices and programming languages, requiring custom interfaces and specialized programming, which is time-consuming and inefficient.

Innovation Solution

A communication architecture with an augmented object-oriented model that includes a message passing layer and an RPC layer, supporting various member types such as functions, properties, events, objrefs, pipes, callbacks, wires, and memories, allowing for consistent and language-neutral communication across diverse devices and systems, while minimizing latency and enabling real-time operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If conventional RPC methods are used for distributed system communication, then basic function calling between client and server is achieved, but time-critical data transfers cannot be handled effectively and latency is high

Engineering Contradiction:
Improvedata transfer speedVSAvoidcommunication latency
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The patent segments the communication architecture into distinct layers: a message passing layer for non-critical operations and an RPC layer for latency-sensitive operations. This segmentation allows each layer to be optimized independently, with the RPC layer providing low-latency function calls while the message passing layer handles less time-critical communication.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an augmented object-oriented interface as an intermediary between the client and server RPC mechanisms. This interface provides a unified, language-neutral way to access distributed objects, eliminating the need for custom interfaces for each programming language and reducing the overhead associated with language-specific RPC implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If custom interfaces and specialized programming are implemented for each device and programming language, then device-specific communication requirements are met, but development time increases and efficiency decreases

Engineering Contradiction:
Improvedevice compatibilityVSAvoiddevelopment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a universal augmented object-oriented interface that works across multiple programming languages and device types. This single interface provides multi-functional access to distributed objects, eliminating the need to create separate custom interfaces for each language while maintaining full adaptability to different devices and systems.

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

Solution Approach 2:

The patent employs dynamic data type negotiation that allows the system to automatically adapt to different data types and formats based on the client and server capabilities. This dynamic adaptation occurs at runtime, enabling the system to work with diverse devices and programming languages without requiring pre-configured custom interfaces for each combination.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If existing RPC methods are used, then basic distributed communication is achieved, but support for complex data types and dynamic negotiation is limited

Engineering Contradiction:
Improvedata type supportVSAvoidcommunication architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service through automatic data type negotiation mechanisms that allow clients and servers to dynamically determine compatible data types without manual configuration. The system automatically negotiates and adapts to the appropriate data types based on the capabilities of the communicating parties, reducing the need for complex pre-configuration while maintaining broad data type support.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10938960B2System and method for implementing augmented object members for remote procedure call
Publication Date: 2021.03.02 WASON JOHN
  • US10938960B2 patent drawing
  • US10938960B2 patent drawing
  • US10938960B2 patent drawing

AI summary

A communication method and system configured to facilitate integration of complex automation systems composed of disparate components that may run with different processes are distributed over a network or are embedded devices. The system/method allows for a client to rapidly access functionality exposed by a service within a client-service system employing a distributed application structure utilizing an augmented object-oriented model of multiple member types. The system/method allows interconnected nodes to communicate through message passing and remote procedure calling so as to reduce latency within a system composed of distributed resources.