Mobile Application Manager Priority Queue Enforcement
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise mobile device management, compliance checks are often delayed due to limited resources and first-in-first-out queuing, leading to prolonged enforcement times, especially for devices in unsecured locations or without prior checks.
Innovation Solution
A mobile application manager determines priority levels for mobile devices based on characteristic data and inserts entries into corresponding processing queues, retrieving and performing compliance checks when higher priority queues are empty, ensuring timely enforcement of compliance policies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a first-in-first-out (FIFO) queue is used to process compliance checks, then the system is simple to implement and manage, but compliance checks for critical mobile devices are delayed for relatively long periods of time
Solution Approach 1:
The single FIFO queue is segmented into multiple priority-level queues (e.g., high, medium, low priority). Each queue handles compliance checks appropriate to its priority level, allowing critical devices to be processed separately from non-critical devices. This segmentation resolves the contradiction by maintaining simple FIFO processing within each queue while enabling time-critical checks to be prioritized through the multi-queue structure.
Solution Approach 2:
Different queues are assigned different priority levels based on the characteristics of mobile devices they handle. High-priority queues are allocated for devices in unsecured locations or requiring immediate compliance verification, while low-priority queues handle routine checks. This local differentiation of queue qualities allows the system to optimize enforcement time for critical devices without complicating the overall queue management mechanism.
2Reliability
If compliance checks are performed periodically for all enrolled mobile devices, then comprehensive security monitoring is achieved, but the limited resources of the mobile application manager result in long waiting periods in the processing queue
Solution Approach 1:
The system dynamically assigns mobile devices to different priority queues based on real-time characteristics such as device location (secured vs. unsecured), user role changes, and compliance status. This dynamic allocation allows the mobile application manager to concentrate resources on high-priority devices requiring immediate attention while maintaining periodic monitoring for lower-priority devices, thereby improving overall processing throughput without compromising comprehensive security coverage.
Solution Approach 2:
The system continuously monitors mobile device characteristics and compliance status, using this feedback to dynamically adjust queue assignments and processing priorities. When a device enters an unsecured location or undergoes role changes, the feedback mechanism triggers re-evaluation and potential reassignment to higher-priority queues, ensuring that compliance checks are performed efficiently based on current risk levels rather than following a rigid periodic schedule for all devices.
3Reliability
If the mobile application manager processes compliance checks for a large number of enrolled mobile devices, then comprehensive enterprise network security is maintained, but the capacity and load of the mobile application manager cause delays in enforcement
Solution Approach 1:
The large volume of compliance checks is segmented across multiple priority-level queues, allowing the mobile application manager to process high-priority devices (those in unsecured locations or with critical security requirements) more quickly while maintaining periodic processing for lower-priority devices. This segmentation maintains comprehensive security coverage across all enrolled devices while reducing enforcement delays for critical cases by preventing them from being buried deep in a single monolithic queue.
Data Source
AI summary
A method, non-transitory computer readable medium, and mobile application manager computing device that determines a priority level for a mobile device requiring a compliance check based on characteristic data associated with, or an identified user of, the mobile device. An entry comprising identifying data for the mobile device is inserted into a processing queue associated with the priority level. A determination is made when each of the processing queues associated with a higher priority level than the one priority level is empty. The entry is retrieved from the processing queue, the compliance check is performed on the mobile device, and a status of the mobile device is marked as out-of-compliance or in-compliance based on a result of the compliance check, when the determining indicates each of the processing queues associated with a higher one of the priority levels than the one priority level determined for the mobile device is empty.