Persistent Connection Architecture for IT Endpoint Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise environments, managing and communicating with multiple endpoints for IT tasks is challenging due to varying hardware and software configurations, and establishing new communication channels for each endpoint results in significant overhead, especially when endpoints go offline.
Innovation Solution
A system and method that establish persistent connections between IT automation appliances and managed endpoints, allowing for efficient communication and plugin management, using built-in and functional plugins to maintain connections and coordinate IT tasks across different platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a new communication channel is established with each managed endpoint, then communication can be initiated, but significant overhead is incurred especially when endpoints go offline
Solution Approach 1:
The system performs preliminary action by establishing persistent communication channels in advance before they are needed. The management computer maintains pre-established connections with managed endpoints, so when communication is required, the channel is already available rather than needing to be created at that moment. This eliminates the time overhead of establishing new channels while ensuring communication reliability.
Solution Approach 2:
The patent implements continuity of useful action through persistent connections that remain open and ready for communication. Instead of repeatedly establishing and tearing down communication channels, the system maintains continuous connections that can be used immediately when needed, eliminating repeated setup overhead while ensuring the communication path is always available.
2Adaptability or versatility
If support software is installed on all managed endpoints with varying configurations, then IT tasks can be performed, but the installation and maintenance process becomes difficult
Solution Approach 1:
The patent applies universality by designing a standardized software architecture with a common core that can operate across different managed endpoints regardless of their varying hardware and software configurations. The functional plugins are designed to be universally compatible while adapting to specific endpoint requirements, allowing the same base software to serve multiple platforms without requiring complex custom installations for each configuration.
Solution Approach 2:
The software is segmented into a core component and separate functional plugins. The core software handles universal communication and management functions that work across all endpoints, while specific functionality is divided into separate plugins that can be independently installed and configured. This segmentation simplifies the installation process by allowing selective deployment of only the necessary plugins for each endpoint type.
3Productivity
If a management computer communicates with thousands of managed endpoints, then comprehensive IT task coverage is achieved, but establishing communication channels becomes inefficient
Solution Approach 1:
The patent merges multiple communication channels into a unified persistent connection framework. Instead of managing separate communication pathways for each endpoint individually, the system consolidates them into a standardized persistent connection model that can handle multiple endpoints efficiently. This reduces the complexity of channel management while maintaining the ability to communicate with thousands of endpoints for comprehensive IT task coverage.
Data Source
AI summary
A system performs information technology (IT) tasks using a computer. Examples of IT tasks include installing or configuring software, displaying alerts, executing programs or scripts on the endpoint, or logging activities. In an embodiment of the system, a connection initialization module receives a request for a persistent connection over a network from a managed endpoint. The request is accepted and a persistent connection is opened with the managed endpoint. A tier-1 module then receives configuration information from the managed endpoint over the persistent connection. The configuration information includes a list of functional plugins on the managed endpoint, where a functional plugin comprises a software module for performing an IT task. The tier-1 module stores this configuration information along with information describing the persistent connection and maintains the persistent connection in an open state.