Loopback Remote Desktop for Persistent Software Robot Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software robots face interruptions and vulnerability to unauthorized access when executing tasks, particularly in locked or disconnected states, as they require interactive and non-interactive actions while being protected from tampering.
Innovation Solution
A system and method that establish a loopback remote desktop connection within the same operating system, allowing a software robot to execute in an unlocked desktop interface protected from external access, using a service session and remote desktop session configuration, enabling persistent interactive actions without network dependence and tampering risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a software robot executes in a locked or disconnected state, then security protection from unauthorized access is improved, but interactive actions are interrupted and reliability deteriorates
Solution Approach 1:
The system divides the execution environment into two separate sessions: a service session for background operation and a remote desktop session for interactive actions. This segmentation allows the software robot to maintain persistent execution in the service session while enabling protected interactive access through the remote desktop session, resolving the contradiction between continuous operation and security protection
Solution Approach 2:
A loopback remote desktop connection acts as an intermediary between the service session and remote desktop session. This intermediary mechanism enables the software robot to perform interactive actions through the remote desktop session while remaining protected in the locked service session, allowing both security and continuous operation without interruption
2Ease of operation
If a remote desktop connection is established for software robot execution, then interactive actions are enabled, but network dependence and vulnerability to tampering increase
Solution Approach 1:
The system merges the service session and remote desktop session into a single computing device with a loopback connection. This combination allows interactive actions to be performed through the remote desktop interface while the actual execution remains protected in the service session on the same device, eliminating network dependence and reducing vulnerability to external tampering
Solution Approach 2:
The loopback remote desktop connection serves as a secure intermediary that enables interactive actions without exposing the software robot to external network risks. By routing interactions through this internal mechanism rather than external networks, the system maintains ease of operation while enhancing protection from tampering
Data Source
Figure 1
Figure 2
Figure 3
AI summary
According to at least one aspect, a system configured to execute a software robot such that interactive actions may be performed by the software robot without interruption is provided. The system comprises at least one hardware processor configured to execute an operating system. The system further comprises at least one non-transitory computer-readable storage medium storing processor-executable instructions configured to execute in a service session in the operating system that, when executed by the at least one hardware processor, causes the at least one hardware processor to: start a first remote desktop session in the operating system, establish a loopback remote desktop connection between the first remote desktop session and the service session, and start a software robot computer program in the first remote desktop session.