Unified Endpoint Management Resource Context Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Unified Endpoint Management (UEM) systems face inefficiencies in resource distribution, leading to significant delays and wasted employee time due to lengthy system queues when multiple employees check out devices simultaneously, resulting in substantial daily costs.
Innovation Solution
The UEM system employs a method where user devices send attributes to create a device context, which is matched to a resource context to quickly identify and provide necessary resources, eliminating the need for extensive querying of services on future requests by creating a new resource context for known combinations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the UEM system queues each device with every service to determine resource allocation, then resource distribution accuracy is improved, but system processing time increases significantly
Solution Approach 1:
The system pre-calculates and stores resource context information for different device types and configurations in a database. When a device checks out, the system retrieves pre-computed resource contexts based on device attributes rather than calculating resources in real-time, dramatically reducing configuration time while maintaining accurate resource allocation
Solution Approach 2:
The system creates a buffer by pre-processing and storing resource context data during off-peak times. This cushion of pre-computed information allows the system to quickly serve multiple concurrent device checkouts without queuing delays, absorbing the computational workload before peak demand occurs
2Reliability
If the UEM system processes check-out requests sequentially through service queues, then resource allocation reliability is improved, but productivity decreases due to long wait times
Solution Approach 1:
The system segments the resource allocation process into distinct components: device attribute extraction, context matching, and resource retrieval. Each segment can be independently optimized and processed in parallel, allowing multiple device checkouts to be handled simultaneously without compromising allocation reliability
Solution Approach 2:
The system introduces a context database as an intermediary layer between device check-out requests and resource services. This mediator stores pre-computed resource contexts and enables rapid lookup based on device attributes, eliminating the need for sequential service queue processing while maintaining reliable resource allocation
3Measurement precision
If the UEM system performs extensive service queries for each check-out request, then resource context accuracy is improved, but system resource consumption increases
Solution Approach 1:
The system creates simplified copies of resource context information and stores them in a database indexed by device attributes. Instead of querying all services for each device, the system retrieves pre-computed context copies that contain all necessary resource allocation information, dramatically reducing computing resource consumption while maintaining accuracy
Solution Approach 2:
The system pre-computes and stores resource context data during system initialization or off-peak periods. This preliminary processing eliminates the need for extensive real-time service queries, reducing energy consumption during peak checkout periods while preserving accurate resource context information
Data Source
AI summary
Systems and methods presented herein provide examples for distributing resources in a UEM system. In one example, the UEM system can receive a request to check out a user device enrolled in the UEM system. The request can include a profile identifier (“ID”) of a user profile making the request and attributes of the user device. The UEM system can create a hash of group IDs associated with the profile ID. The UEM system can create a device context that includes the device attributes and the hash. The UEM system can then determine if the device context matches to a resource context. Resource contexts can identify a set of UEM resources associated with a device context. Where a match is found, the UEM system can provide the corresponding resources to the user device.