Embedded Robot Invocation Using Listener-Based Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing robotic process automation (RPA) systems require users to invoke robots through a robot tray or conductor API, limiting their ability to do so from different applications.
Innovation Solution
A method and system that allow invoking robots from within applications by launching a robot link, initiating a port discovery process, generating a randomized code, and requesting user consent, which enables authentication and communication with robots through local and global listener modules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users invoke robots through robot tray or conductor API, then robot invocation is controlled and secure, but users cannot invoke robots from different applications
Solution Approach 1:
The patent introduces an intermediary authentication mechanism that mediates between applications and robots. The port discovery process and randomized code verification act as intermediaries that enable secure communication while allowing invocation from multiple applications. This intermediary layer resolves the contradiction by providing both versatility (multiple applications can invoke) and security (through controlled authentication).
Solution Approach 2:
The patent creates a universal invocation mechanism that works across different applications. By implementing a standardized port discovery and authentication process that can be accessed from any application, the system achieves multi-functionality. The robot link embedded in applications provides a universal interface that maintains security while enabling invocation from diverse sources.
2Adaptability or versatility
If robot link is embedded within applications, then users can invoke robots from applications, but security risks increase without proper authentication
Solution Approach 1:
The patent applies preliminary action by performing port discovery and generating randomized codes before actual robot invocation. The authentication process is initiated in advance, with the application generating a randomized code that must be verified before the robot can be invoked. This preliminary authentication ensures security is established before any robot interaction occurs.
Solution Approach 2:
The patent implements feedback mechanisms through the authentication process. The system provides feedback to the user about the authentication status and requires user confirmation before invoking the robot. The randomized code verification provides feedback to ensure the invocation is authorized, thereby maintaining security while enabling application-based invocation.
Data Source
AI summary
A process for invoking a robot from an application may include launching the application from a computing system to invoke a robot link embedded within the application. The process may also include initiating from the application a port discovery process to identify a port, port details, and a token. The process may further include generating by the application a randomized code and invoking a consent application requesting approval from a user of the computing system to invoke the robot from the application. The process may also include registering the randomized code with a local listener module and passing user information and the token to a global listener module. The process may further include receiving from the global listener module the token and port identification, allowing the application to authenticate itself with, and communicate with, the robot, thereby completing the robot invoking process.