Sentinel Thread Connectivity Notification System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network systems, such as enterprise networks, often experience communication interruptions between remote terminals and central servers due to high traffic, security issues, or signal loss, leaving end-users unaware of the disruptions.
Innovation Solution
A remote desktop client software system that employs a sentinel thread to monitor connectivity between remote computers and servers, generating notifications upon connection loss and automatically restarting the connection when data exchange is restored, thereby minimizing processing overhead and ensuring user awareness of connectivity status.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If a sentinel thread is added to monitor connectivity, then user awareness of connectivity status is improved, but device complexity increases
Solution Approach 1:
The remote desktop client software is divided into two independent threads: a main thread that handles primary data exchange and a sentinel thread that monitors connectivity. This segmentation allows the monitoring function to operate independently without interfering with the main data exchange operations, resolving the contradiction by adding functionality while maintaining modular complexity.
Solution Approach 2:
The sentinel thread acts as an intermediary between the main thread and the connectivity status. It indirectly monitors connectivity by checking for the presence of sentinels (marker packets) in the data stream without directly interrupting the main data exchange process, thus improving awareness while minimizing structural complexity.
2Measurement precision
If continuous monitoring is performed, then connectivity detection precision is improved, but processing overhead increases
Solution Approach 1:
Instead of continuous monitoring, the sentinel thread performs periodic connectivity checks by looking for sentinels at regular intervals within the data stream. This periodic approach maintains detection precision by consistently checking for connectivity markers while significantly reducing processing overhead compared to continuous active monitoring.
Solution Approach 2:
The main thread inadvertently provides connectivity information to the sentinel thread by including sentinels in its data exchanges. The sentinel thread simply needs to detect these self-provided markers rather than actively generating probe signals, reducing the monitoring burden and processing overhead while maintaining detection precision.
Data Source
AI summary
An example method includes presenting a first notification indicating a potential interruption in connectivity between a server and a remote terminal. If the potential interruption is resolved before the expiration of a restart time interval, the first notification is removed. If the potential interruption is not resolved before the expiration of the restart time interval, a second notification is presented, the second notification indicating a loss of connectivity between the server and the remote terminal.