Request Broker for Backend Agent Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complexity and volume of computer programs make it cumbersome for users to manage their capabilities, locations, and methods of operation, leading to difficulties in interacting with multiple backend agents effectively.

Innovation Solution

A request broker system manages communication with multiple backend agents, receiving user input and determining the appropriate agent to provide feedback without the user knowing the agent's identity, maintaining a direct line of communication and receiving feedback, while hiding the agents from the user and allowing for secure, private communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple backend agents are deployed to provide diverse computer program capabilities, then the functionality and versatility of the system is improved, but the complexity of managing and interacting with these agents increases

Engineering Contradiction:
ImprovefunctionalityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a request broker as an intermediary component that sits between users and multiple backend agents. The broker receives requests from users, determines which backend agent should handle each request, and routes the requests appropriately. This mediator architecture allows the system to support diverse backend agents with different capabilities while presenting a unified interface to users, thereby resolving the contradiction between enhanced functionality and increased management complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If users directly interact with multiple backend agents, then access to specific capabilities is improved, but the ease of operation deteriorates due to the need to know agent identities, locations, and methods

Engineering Contradiction:
Improveaccess to capabilitiesVSAvoiduser interaction simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The request broker is designed as a universal interface that can handle requests for multiple different backend agents through a single unified method. Instead of requiring users to know the specific identities, locations, and interaction methods of each backend agent, the broker provides a universal entry point that adapts to route requests to the appropriate agent. This multi-functional design maintains ease of operation while enabling access to diverse capabilities.

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

3Ease of operation

If a request broker is introduced to manage backend agents, then ease of operation is improved, but the device complexity increases due to the additional intermediary component

Engineering Contradiction:
Improveuser interaction simplicityVSAvoidsystem architecture complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the complexity of agent management from the user interaction layer and places it in a dedicated request broker component. By taking out the routing and agent management logic from the user-facing interface, the system achieves simplicity for users while concentrating the necessary complexity in a single manageable intermediary. This extraction allows the broker to handle agent coordination without requiring users to understand or manage the underlying complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10986045B2Integration hub
Publication Date: 2021.04.20 SAP SE
  • US10986045B2 patent drawing
  • US10986045B2 patent drawing
  • US10986045B2 patent drawing

AI summary

Disclosed herein are system, method, and computer program product embodiments for providing a single point of interaction for communicating with a first agent and a second agent. An embodiment operates by a server sending a preliminary request for a preliminary response to the first agent and the second agent and, based on the preliminary request, receiving the preliminary response from the first agent. Thereafter, the server determines that the first agent is a preferred agent based on the preliminary response and maintains a line of communication to the preferred agent. The server then sends a follow-up request for a follow-up response different from the preliminary request to the preferred agent over the line of communication and receives the follow-up response from the preferred agent over the line of communication.