Endpoint Agent Software Module Deployment Without Downtime
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional IT departments face challenges in managing mobile devices due to rapid changes and compatibility issues, making it cumbersome to deploy new applications or features, which can lead to organizations avoiding updates or new security procedures.
Innovation Solution
A system and method for deploying software modules using a file server, module manager, manifest server, and agents on endpoints, allowing automatic download and installation of feature modules without significant downtime, facilitated by a scripting engine and heartbeat server for status reporting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual download and installation of applications is required, then users can control what is installed, but the deployment process becomes cumbersome and time-consuming
Solution Approach 1:
The system enables self-service deployment where the mobile device automatically checks for available applications and updates through the agent, downloads them from the file server, and installs them without requiring user intervention. The device autonomously manages its own software updates by communicating with the heartbeat server and file server.
Solution Approach 2:
Applications and updates are prepared in advance on the file server, organized in the manifest file with download locations and installation instructions. The agent on the mobile device retrieves this pre-prepared information and executes the installation process automatically, eliminating the need for users to manually search for and download applications.
2Reliability
If applications are updated manually by users or IT personnel, then installation control is maintained, but the update process becomes invasive and requires device restart
Solution Approach 1:
The mobile device performs self-updating through the agent component, which automatically checks for updates via the heartbeat server, downloads new versions from the file server, and installs them without requiring user action or IT personnel intervention. The device manages its own software lifecycle autonomously.
Solution Approach 2:
The agent acts as an intermediary between the mobile device, heartbeat server, and file server. It facilitates the update process by communicating with the heartbeat server to check for updates, retrieving download information, and coordinating with the file server to obtain and install application updates, thereby eliminating the need for direct user or IT personnel involvement in the update process.
3Adaptability or versatility
If new applications are separately downloaded and installed, then feature functionality is added, but the installation process interferes with device use and requires multiple restarts
Solution Approach 1:
The system enables continuous operation during application installation by allowing the mobile device to maintain its functionality throughout the update process. The agent downloads and installs new applications in the background without requiring device restart, ensuring that the device remains operational and useful throughout the deployment process.
Solution Approach 2:
The manifest file contains pre-prepared installation information including download locations and installation instructions for new applications. The agent retrieves this information in advance and executes the installation process automatically, allowing applications to be installed without interrupting device usage or requiring restarts.
4Ease of operation
If users are required to manually install applications, then installation control is maintained, but users are slow to upgrade or install new applications
Solution Approach 1:
The mobile device autonomously performs application installation and updates through the agent component, which automatically checks for available applications via the heartbeat server, downloads them from the file server, and installs them without requiring user action. This self-service mechanism dramatically accelerates deployment speed while maintaining organizational control through centralized management.
Solution Approach 2:
The manifest file contains pre-prepared information about available applications, updates, and their installation requirements. The agent retrieves this information in advance and automatically executes the installation process, eliminating the need for users to manually search for, download, and install applications, thereby dramatically increasing deployment speed.
5Adaptability or versatility
If organizations outsource MDM tasks to third party vendors, then expertise in managing mobile devices is gained, but access to physical devices is lost making deployment complicated
Solution Approach 1:
The agent acts as an intermediary that enables third-party vendors to manage and deploy applications to mobile devices remotely without physical access. The agent on the device communicates with the vendor's servers (heartbeat server and file server), allowing the vendor to push applications and updates to devices anywhere in the organization, thereby maintaining ease of deployment despite outsourcing.
Solution Approach 2:
The mobile device autonomously executes application installation and updates by receiving instructions from the third-party vendor's servers through the agent. The device self-manages the deployment process locally, allowing the vendor to maintain control and expertise while the device handles the actual deployment operations without requiring physical access or complex remote procedures.
Data Source
AI summary
Systems and methods facilitate the deployment of software modules from a file server to agents on endpoints. Agents can contact a heartbeat server to receive information about a latest manifest file that identifies the software modules that should be installed on the endpoint. Agents can then determine from the manifest information whether new files need to be downloaded and automatically download them. A scripting engine can be used to allow run-time installation of modules without causing significant downtime of the endpoint. The scripting engine can utilize the agent to report back status and data from the software modules to allow modules to be used with a mobile device management platform.