Socket Resource Management via Pause State for Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing socket management technologies degrade user experience by closing sockets during inactivity, leading to perceived delays and resource inefficiency, as they conserve system resources by closing sockets even when applications are inactive, which affects timely data transmission and user experience.
Innovation Solution
Implement a mechanism that allows applications to specify whether inactive sockets should be closed or paused, maintaining socket connectivity while releasing resources on the client machine, allowing sockets to remain open on remote servers, thus conserving resources without degrading user experience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If sockets are closed during inactivity to conserve resources, then system resource efficiency is improved, but user experience deteriorates due to perceived delays and interrupted data transmission
Solution Approach 1:
The socket state is made dynamic rather than static. The system can transition sockets between different states (open, paused, closed) based on activity detection and application preferences. This allows the socket to adapt its state dynamically - remaining open during active use for good user experience, and transitioning to paused or closed state during inactivity to conserve resources, thus resolving the contradiction between resource efficiency and user experience reliability
Solution Approach 2:
The patent changes the parameter of socket state from a binary open/closed state to a multi-state system including paused state. By introducing this intermediate state, the system can conserve resources by pausing sockets during inactivity while maintaining the ability to quickly resume connectivity when needed, thereby improving resource efficiency without significantly degrading user experience
2Productivity
If sockets are closed to conserve resources on client machine, then resource management efficiency is improved, but socket connectivity is lost resulting in data transmission delays
Solution Approach 1:
The system performs preliminary actions by detecting socket inactivity and transitioning to paused state before complete disconnection occurs. This preliminary pause state allows the socket to be quickly resumed when activity is detected, minimizing the time loss that would otherwise occur if sockets were completely closed and re-established. The paused state serves as a preparatory intermediate step that balances resource conservation with quick re-connectivity
3Reliability
If sockets remain open during application inactivity, then socket connectivity is maintained for timely data reception, but system resources are wasted
Solution Approach 1:
The patent applies different quality treatments to different socket states based on local conditions. Instead of uniformly keeping all sockets open, the system selectively manages socket states based on individual application preferences and activity patterns. Some sockets can remain open for critical real-time communication, while others can be paused or closed for resource-intensive applications with lower latency requirements, thus optimizing the balance between connectivity reliability and resource consumption locally
Data Source
AI summary
A computer implemented method includes determining, by at least one processor executing code segments stored on a non-transitory computer readable medium, if an application is de-activated; and one of killing, by the at least one processor, a socket associated with the application or pausing, by the at least one processor, the socket based on a flag set by the application.