Software Migration Policy Manager for Mobile Environments
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software migration techniques in mobile environments, such as Post-Copy and Pre-Copy Migration, face inefficiencies due to high operating performance costs and excessive data charges, particularly in varying migration environments like network states and device capabilities.
Innovation Solution
A software migration apparatus and method that includes a policy manager to select optimal migration methods like basic copying, duplicate copying, or control transfer based on current migration environments, minimizing data transfer and network usage by analyzing factors like device capabilities and user purposes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If Pre-Copy Migration technique is used to copy entire memory to target device, then software migration completeness is improved, but migration time and data charge increase excessively
Solution Approach 1:
The patent segments the memory copying process into two phases: first copying only essential memory regions (code segments, constant data) to enable basic software execution, then selectively copying additional memory regions (variable data, stack) only when needed. This segmentation resolves the contradiction by achieving migration completeness through staged copying rather than requiring all memory to be copied upfront, thereby reducing initial migration time and data charge.
2Reliability
If Pre-Copy Migration technique is used to copy entire memory to target device, then software migration completeness is improved, but data charge increases due to extended wireless network use
Solution Approach 1:
The patent divides memory copying into essential segments (copied immediately) and non-essential segments (copied later or on-demand). By copying only critical memory regions first, the system achieves sufficient software functionality with minimal data transfer, thereby reducing wireless network usage time and associated data charges while maintaining migration completeness through selective subsequent copying.
Solution Approach 2:
The patent applies partial action by copying only the necessary portion of memory (essential segments) rather than the entire memory space. This partial copying approach provides sufficient functionality for the migrated software to operate, eliminating the need to copy all memory regions and thereby reducing data charge while achieving practical migration completeness.
3Loss of time
If Post-Copy Migration technique is used to copy minimal memory initially, then migration time is reduced, but operating performance deteriorates due to page faults
Solution Approach 1:
The patent performs preliminary action by copying essential memory segments (code, constants) before software execution begins. This preliminary copying ensures that critical code and data are already present in the target device's memory, eliminating page faults during execution of these essential regions and maintaining operating performance while still achieving fast migration through selective copying.
4Loss of time
If Post-Copy Migration technique is used to copy minimal memory initially, then migration time is reduced, but system stability worsens due to frequent page faults
Solution Approach 1:
The patent segments memory into essential and non-essential regions, copying only essential segments initially. This segmentation strategy ensures that critical code and data structures are stable and fault-free from the start, while non-critical regions can be copied later without affecting system stability. The approach maintains system stability by ensuring essential components are always present in target memory.
Data Source
AI summary
Provided is an apparatus for software migration between devices in a mobile environment. The software migration apparatus may include a policy manager configured to select a migration method for target software according to a migration environment, and a migration manager configured to perform migration of the target software according to the migration method. In addition, provided herein is a software migration method which is performed in a mobile environment. The software migration method may involve analyzing a current migration environment, selecting a migration method according to the analyzed current migration environment, and performing the migration of the target software.