In-Vehicle Infotainment Device Virtual Machine Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing in-vehicle infotainment systems face usability issues due to differences in user interfaces between embedded devices, leading to severed usability experiences for drivers.
Innovation Solution
An electronic device with a processor and memory, connected to the in-vehicle infotainment system via a connector, executes instructions to receive and migrate state information, install and execute operating systems, and provide data between devices, enabling the display of a unified screen with visual objects from multiple virtual machines on connected devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple electronic devices operate independently with different user interfaces, then each device can provide its own infotainment service, but usability is severed and user experience deteriorates
Solution Approach 1:
The patent merges multiple independent electronic devices into a unified system by migrating virtual machines between devices. The head unit and portable terminal are combined into a single infotainment system where applications and data can be transferred seamlessly, creating a unified user interface that spans multiple physical devices while maintaining device independence.
Solution Approach 2:
The patent implements universality by enabling the infotainment system to function across multiple device types (head unit, portable terminal) with a single unified interface. The system can provide infotainment services through different devices interchangeably, making the system adaptable to various form factors while maintaining consistent usability.
2Ease of operation
If a unified user interface is implemented across multiple devices, then usability improves, but system complexity increases due to coordination requirements
Solution Approach 1:
The patent uses virtual machine copying and migration to create unified interfaces. Instead of implementing complex coordination protocols between devices, the system copies virtual machines and their states between devices, allowing the same application instance to be accessed through different device interfaces without requiring complex inter-device communication and synchronization.
Solution Approach 2:
The patent introduces a virtualization layer as an intermediary between the physical devices and the user interface. This virtualization layer abstracts the complexity of multi-device coordination, allowing applications to run in virtual machines that can be migrated between devices without requiring direct complex communication between the physical devices themselves.
3Ease of operation
If virtual machine migration is implemented between devices, then seamless user experience is achieved, but data transfer time and processing overhead increase
Solution Approach 1:
The patent performs preliminary actions by pre-establishing communication channels and preparing virtual machine images for migration. The system proactively manages virtual machine states and prepares data for transfer before actual migration is needed, reducing the time required during actual migration operations by having necessary data and configurations ready in advance.
Data Source
AI summary
An electronic device for providing an in-vehicle infotainment (IVI) service using migration and a method thereof are provided. The electronic device includes a housing, a connector exposed through the housing and connected to an IVI system, a processor positioned in the housing and operatively connected with the connector, and a memory positioned in the housing and be operatively connected with the processor. The memory includes a first system software, a hypervisor configured to execute the first system software, and instructions. The instructions, when executed by the processor, control the electronic device to: receive state information about the IVI system through the connector, receive at least part of a second system software of the IVI system through the connector, install the at least part of the second system software to execute on the hypervisor, cause the IVI system to be inactivated, execute the first system software and the second system software on the hypervisor using at least part of the state information, and provide data resulting from operations of the first system software and the second system software to the IVI system through the connector.