Virtualized Mobile Device Usage Control via Hypervisor

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices face limitations in memory and CPU resources, which hinder their usage due to their design and power-saving features, and existing technologies struggle to effectively manage and secure virtual machines on these devices, especially in terms of isolation and resource management.

Innovation Solution

A virtualized mobile device architecture that incorporates a hypervisor and virtualization software layer to run guest operating systems and applications, utilizing device emulators and transformers to manage physical device access, ensuring isolation and security, while allowing for the management of virtual machines and physical devices through a management server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If virtualization software is implemented to run multiple virtual machines, then device functionality and security are enhanced, but device complexity increases

Engineering Contradiction:
Improvedevice functionalityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the mobile device into multiple isolated virtual machines, each capable of running independent applications and services. The virtualization software divides the physical device resources (CPU, memory, storage) into separate virtualized environments, allowing multiple functions to coexist securely while managing complexity through structured resource allocation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The virtualization software acts as an intermediary layer between the physical device hardware and the virtual machines. This mediator manages resource allocation, enforces security policies, and coordinates access to shared resources, thereby enhancing functionality while containing complexity within a standardized software interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple virtual machines are run simultaneously, then device versatility improves, but memory and CPU resources are consumed

Engineering Contradiction:
Improvedevice versatilityVSAvoidmemory and CPU resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system merges multiple virtual machine environments onto a single physical mobile device, consolidating what would traditionally require separate physical devices into one shared platform. The virtualization software combines CPU cycles, memory capacity, and storage space into poolable resources that can be dynamically allocated across multiple virtual machines, achieving versatility without proportionally increasing physical resource consumption.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The virtualization software dynamically changes resource allocation parameters based on demand, adjusting the amount of memory and CPU time each virtual machine receives. This allows the system to optimize resource utilization by allocating more resources to active virtual machines and reducing allocation to inactive ones, thereby supporting multiple simultaneous virtual machines within the constraints of available physical resources.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP2446354B1Controlling usage in virtualized mobile devices
Publication Date: 2019.11.06 VMWARE INC
  • EP2446354B1 patent drawingFigure 1

AI summary

One embodiment is a method of controlling usage in a virtualized mobile device including virtualization software that supports one or more virtual machines, the method including: (a) receiving control information at the virtualized mobile device that includes one or more limits pertaining to one or more uses of the virtualized mobile device; (b) collecting usage information relating to the one or more uses; (c) determining whether usage information corresponding to one of the one or more uses exceeds a corresponding one of the one or more limits; and if so; (d) carrying out a predetermined action relating to the one of the one or more uses.