Service Bus RPC Routing for Decoupled Data Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication patterns in distributed computing, such as RPC, Publish/Subscribe, and Selective-Subscription, face challenges in automation systems like smart grids, where entities must remain decoupled and unaware of each other, leading to inefficient data distribution and high system load.
Innovation Solution
A method for a remote procedure call (RPC) in a service bus communication system that allows for selective subscription without requiring entities to know each other, utilizing a data exchange system to manage requests and replies, ensuring only needed data is published and reducing system load and initialization calls.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Publish/Subscribe messaging pattern is used, then decoupling between publishers and subscribers is achieved, but all data are always sent to the dataspace causing high system load
Solution Approach 1:
The patent introduces a service bus as an intermediary component that mediates between publishers and subscribers. The service bus receives publish requests, determines which subscribers should receive which data based on subscription criteria, and routes data accordingly. This resolves the contradiction by maintaining decoupling while reducing system load through intelligent data routing that sends only relevant data to appropriate subscribers.
2Loss of energy
If Selective-Subscription pattern is used, then only needed data are published reducing system load, but subscriber needs to know publishers and data the publisher can provide
Solution Approach 1:
The service bus acts as an intermediary that manages the complexity of selective subscription. Subscribers register their data requirements with the service bus without needing to know specific publishers. The service bus maintains knowledge of available data sources and automatically routes relevant data to subscribers based on their subscriptions, thus reducing system load while eliminating the need for subscribers to know publisher details.
Solution Approach 2:
The system enables self-service through automatic data routing. The service bus automatically determines which data should be published to which subscribers based on pre-registered subscription criteria, without requiring manual configuration or knowledge of publisher-subscriber relationships. This resolves the contradiction by reducing system load through selective data publication while eliminating the complexity burden from subscribers.
3Speed
If RPC is used, then direct communication between requester and provider is achieved, but requester must know the provider and intent of the function
Solution Approach 1:
The service bus serves as an intermediary that enables indirect RPC-like communication. Requesters can request data through the service bus without knowing specific providers, while the service bus routes requests to appropriate data sources and returns results. This maintains relatively fast communication speeds while reducing the knowledge requirement about providers, as the service bus handles the provider discovery and routing automatically.
Data Source
AI summary
A method for a remote procedure call can be used between entities in a service bus communication system that includes a first consumer, a data exchange system and a number of publishers. The method includes receiving a first request for data from the first consumer at the data exchange system, transmitting the first request from the data exchange system to the plurality of publishers, receiving, by the data exchange system, a first reply to the first request for data from a first publisher of the plurality of publishers, and transmitting the first reply from the data exchange system to the first consumer.