Extended JSON RPC Mediator for Distributed Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current remote procedure call (RPC) systems in distributed computing are limited in the information they can include in requests and responses, lacking the ability to effectively manage additional properties required for method execution and communication in complex scenarios.
Innovation Solution
A system and method that convert requests and responses between Extensible Markup Language (XML) and extended JavaScript Object Notation (JSON) RPC formats, using a mediator to include additional properties such as device identification, user identification, and timestamps, enabling more comprehensive method execution and response handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traditional RPC format is used, then system complexity is reduced, but information completeness in requests and responses is limited
Solution Approach 1:
The patent introduces a mediator component that acts as an intermediary between the client and target device. This mediator handles the conversion between traditional RPC format and extended JSON RPC format, managing the additional properties (device ID, user ID, timestamp) without requiring changes to the core RPC mechanism. The mediator absorbs the complexity of information management while preserving the simplicity of the underlying system architecture.
Solution Approach 2:
The patent segments the RPC communication into distinct property categories: first properties for method execution and second properties for additional information (device ID, user ID, timestamp). This segmentation allows the system to handle different types of data separately, improving information completeness while maintaining clear structure and manageable complexity through organized property handling.
2Adaptability or versatility
If additional properties are included in RPC requests, then method execution capability is enhanced, but data processing complexity increases
Solution Approach 1:
The patent divides RPC request properties into two distinct segments: first properties that are essential for method execution (method name, parameters) and second properties that provide additional context (device ID, user ID, timestamp). This segmentation enables enhanced method execution capability while managing data processing complexity by organizing properties into logical groups that can be handled separately.
Solution Approach 2:
The extended JSON RPC format creates a universal request structure that can handle both traditional RPC needs and additional information requirements through a single standardized format. The first properties handle method execution while second properties provide supplementary information, allowing the same data structure to serve multiple functions without increasing processing complexity proportionally.
3Loss of information
If extended JSON RPC format is used, then communication comprehensiveness is improved, but conversion overhead is introduced
Solution Approach 1:
The patent implements preliminary action by pre-defining the structure and organization of extended JSON RPC properties. The first properties and second properties are structured in advance with clear roles and formats, allowing for efficient conversion processes. This pre-structuring reduces the actual conversion overhead during runtime by eliminating the need for complex dynamic analysis of property structures.
Solution Approach 2:
The mediator serves as a buffer that handles the conversion between traditional RPC and extended JSON RPC formats. By centralizing the conversion logic in the mediator, the system pays the conversion overhead cost in a controlled manner while achieving comprehensive communication. The mediator caches and manages property mappings, reducing repeated conversion efforts and minimizing time loss.
Data Source
AI summary
Systems and methods for providing an extended JavaScript Object Notation (JSON) remote procedure call (RPC) with a mediator in a management software in a host computing device. The management software implements a mediator using the extended JSON RPC format to forward a request from a remote computing device to a device to perform a method. In operation, the management software receives the request from the remote computing device. Then the mediator converts the request to an extended JSON RPC request, which includes first properties for performing a method on a target device and second properties not for performing the method. The mediator may store the first and second properties based on the extended JSON RPC request for internal use. Then the mediator generates a command based on the first properties of the extended JSON RPC request, and sends the command to the target device to perform the method.