Virtualization-Aware Device Management for Mobile Platforms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional device management servers are unable to effectively manage multiple virtual devices on a single virtualized platform, as they are limited to interacting with the underlying hardware platform and lack the capability to direct management commands to individual virtual environments.
Innovation Solution
A virtualization-aware device management (VADM) server is introduced, which identifies and manages multiple virtual devices by associating unique identifiers with each virtual environment, allowing it to interact with device management clients within these environments and execute commands specifically for each virtual device, even as the virtualization status of the device changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a conventional device management server is used, then it can manage non-virtualized devices with a single operating system, but it cannot manage multiple virtual devices on a virtualized platform
Solution Approach 1:
The patent segments the device management functionality by creating separate device management clients for each virtual device environment. The virtualized device runs multiple instances of the device management client, one for each virtual device, allowing the server to manage each virtual environment independently while maintaining a unified server architecture
Solution Approach 2:
The device management server is designed with universal functionality to handle both non-virtualized and virtualized devices through a common interface. The server can process management commands for multiple virtual devices on a single platform using the same device identifier exchange mechanism, eliminating the need for separate management systems
2Measurement precision
If a single device identifier is used for the underlying platform, then hardware credentials can be checked, but individual virtual environments cannot be uniquely identified
Solution Approach 1:
The patent implements a nested identification structure where the device identifier for each virtual device contains both the underlying platform hardware identifier and a virtual environment-specific identifier. This nested approach allows the system to maintain the hardware-level identification while embedding additional information about the specific virtual environment within the same identifier structure
Solution Approach 2:
The system creates copied instances of the device management client for each virtual environment, with each copy using the platform device identifier exchanged during registration. This allows each virtual environment to have its own management instance while sharing the underlying hardware identification mechanism
3Ease of operation
If management commands are sent to the underlying platform, then hardware-level control is achieved, but commands cannot be directed to specific virtual devices
Solution Approach 1:
The device management client acts as an intermediary between the server and the virtual device environments. The client receives management commands from the server using the exchanged device identifier, then routes these commands to the appropriate virtual environment or aggregates them for platform-level execution, simplifying the command management process
Data Source
AI summary
A virtualization aware device management (VADM) server manages mobile devices, including mobile devices that have been virtualized. Each virtualized mobile device supports multiple virtual devices. Each virtual device can be managed independently by the VADM server, in similar manner to non-virtualized devices. The VADM server interacts with one or more device management clients (DMCs) running on a virtualized mobile device to manage the virtual devices installed thereon. In a mobile virtualized device, a DMC can run exclusively within the virtual machine monitor (VMM) for remote management of some or all of the virtual devices on the mobile virtualized device; within each virtual device for remote management of the respective virtual device; or a combination thereof, with a DMC in the VMM acting as a bridge for DMCs within the virtual devices.