Analytics Driven Update Notification for Managed Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current device management systems update all components regardless of usage, leading to performance issues on devices with limited storage, as they consume excessive resources for rollback information.
Innovation Solution
Implementing analytics-driven update notifications where an agent on a managed device monitors application usage and reports to a management server, which generates rankings and recommends updates based on active duration, ensuring only used components are updated.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all components are updated regardless of usage, then system reliability is improved through comprehensive updates, but storage resources are consumed excessively due to rollback information for unused components
Solution Approach 1:
The patent applies partial action by updating only the subset of components that are actively used on the device, rather than updating all available components. The system identifies used components through monitoring mechanisms and limits update operations to those specific components, thereby avoiding storage consumption from rollback information of unused components while still maintaining reliability for the actually used software parts
Solution Approach 2:
The patent implements local quality by treating different components differently based on their usage status. Used components receive updates and maintain rollback capability, while unused components are excluded from updates. This differentiated approach optimizes storage allocation by applying update operations only where necessary rather than uniformly across all components
2Reliability
If all components are updated regardless of usage, then comprehensive system coverage is achieved, but device performance deteriorates due to limited storage resources
Solution Approach 1:
The system performs partial updates by identifying and updating only the components that are actively used on the device. Through monitoring mechanisms that track component usage, the system limits update operations to the necessary subset, thereby maintaining adequate system coverage for used components while preserving device performance by avoiding storage consumption from updating unused components
3Reliability
If rollback information is stored for all updated components, then update reliability is improved through rollback capability, but storage consumption increases excessively
Solution Approach 1:
The patent applies local quality by providing rollback capability only for used components that are updated, rather than maintaining rollback information for all components. The system monitors component usage and selectively enables rollback functionality only where update operations are performed, thereby maintaining update reliability for actively used components while minimizing storage consumption by eliminating unnecessary rollback data for unused components
Data Source
AI summary
Analytics driven update notifications can be provided. An agent on a managed device can monitor which applications are being used on the managed device and can provide a report of these application usage details along with other details of components on the managed device to a management server. The management server can evaluate reports received from a number of agents to generate rankings of applications and components that are based at least partially on usage. The management server can then identify available updates and present recommendations for deploying the updates based on the rankings.