Dual Enrollment for Client Device Management Frameworks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current management systems for client devices typically allow enrollment into only one management framework, either OEM or OS management capabilities, limiting the ability to utilize both simultaneously, which restricts multi-user device management and remote administration in enterprise environments.
Innovation Solution
A system that enables client devices to be enrolled in both OEM and OS management services, allowing dual enrollment with separate managed workspaces and device identifiers, enabling simultaneous use of both management channels for comprehensive device management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a device is enrolled in only one management framework (OEM or OS), then the management system is simple and straightforward, but the device cannot utilize both OEM and OS management capabilities simultaneously
Solution Approach 1:
The patent segments the management enrollment into two distinct types: OEM management enrollment and OS management enrollment. Each enrollment type operates independently with its own management component and workspace, allowing the device to be enrolled in both simultaneously without conflict. This segmentation resolves the contradiction by enabling multi-framework support while maintaining clear separation of management functions.
Solution Approach 2:
The device is designed to support multiple management frameworks universally by implementing both OEM and OS management capabilities. The system can function under OEM management, OS management, or both simultaneously, making it adaptable to different enterprise requirements. This multi-functionality directly addresses the versatility improvement while the modular architecture manages the complexity.
2Adaptability or versatility
If dual enrollment is implemented, then both OEM and OS management capabilities can be utilized, but the enrollment structure becomes more complex
Solution Approach 1:
The enrollment structure is segmented into distinct OEM enrollment and OS enrollment pathways. Each enrollment type has its own management component (OEM management component and OS management component) that operates independently. This segmentation allows dual enrollment capability while managing complexity through clear separation of enrollment processes and management functions.
Solution Approach 2:
The patent introduces an intermediary mechanism that coordinates between OEM management and OS management systems. This intermediary layer handles the complexity of dual enrollment by managing the interactions and data flow between the two management frameworks, allowing both to function simultaneously without direct conflict.
3Ease of operation
If single enrollment is used, then the management system is straightforward, but multi-user device management and remote administration are restricted
Solution Approach 1:
The device management system is designed to support multiple management frameworks universally, enabling it to adapt to different operational requirements. By supporting both OEM and OS management capabilities, the system can provide comprehensive multi-user device management and remote administration functions while maintaining ease of operation through standardized management interfaces.
Solution Approach 2:
The patent adds another dimension to device management by implementing separate workspaces for OEM-managed applications and OS-managed applications. This dimensional separation allows different management operations to occur simultaneously in different spaces, enhancing versatility while maintaining operational simplicity within each workspace.
4Reliability
If both OEM and OS management are enabled, then comprehensive device management is achieved, but the system complexity increases
Solution Approach 1:
The management system is segmented into distinct OEM management and OS management components, each with its own workspace and management protocols. This segmentation ensures that both management frameworks can operate reliably and independently, achieving comprehensive device management while containing system complexity through modular architecture.
Solution Approach 2:
Different parts of the device management system have different qualities and management approaches. OEM-managed applications operate with OEM management controls, while OS-managed applications operate with OS management controls. This local differentiation allows comprehensive management coverage while maintaining simplicity within each management domain.
Data Source
AI summary
Disclosed are various examples for facilitating enrollment of a client device into more than one management framework. A client device can be enrolled with a management service as a fully managed device. The client device can also be enrolled with the management service as a personal or bring-your-own-device (BYOD), which causes a workspace to be created on the device that is segregated from the rest of the client device. Both enrollments can be managed by a remotely executed management service.