Cross-OS Application Management via Intermediary Bridge

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional hybrid system architectures face challenges in managing applications across different operating systems, leading to poor user experience due to limitations in invoking and managing applications between connected devices, inefficient data synchronization, and cumbersome application backup processes.

Innovation Solution

An application management method and apparatus that enables a first apparatus to connect with a second apparatus, map applications, detect operations, and transmit management commands to manage applications seamlessly across different systems, allowing for efficient synchronization and backup without the need for manual installation of client software.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a hybrid architecture system with independent operating systems is used, then system functionality and versatility are improved, but application management capability deteriorates because one operating system cannot invoke or manage applications in another operating system

Engineering Contradiction:
Improvesystem functionalityVSAvoidapplication management capability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces an application management module as an intermediary component that bridges multiple independent operating systems. This module can invoke and manage applications across different OS instances, resolving the isolation problem while preserving the benefits of having multiple independent systems. The intermediary translates and coordinates application management commands between the user interface and the target operating system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The application management module is designed with universal functionality to handle application invocation, management, and control across diverse operating systems. It provides a unified interface that can adapt to different OS types (e.g., Android, iOS, Windows), enabling one system to manage applications in multiple other systems without requiring OS-specific implementation details.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If conventional synchronization methods connecting only two devices through a data line are used, then data consistency between the two devices is maintained, but the system cannot meet varied complex needs of current users who require synchronization across multiple devices

Engineering Contradiction:
Improvedata consistencyVSAvoidmulti-device synchronization capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent merges multiple independent synchronization connections into a unified synchronization network. Instead of treating each device pair separately, the system combines their synchronization states and coordinates data consistency across all devices simultaneously. This allows users to access and synchronize data across multiple devices (phone, tablet, computer) while maintaining consistency through a single coordinated mechanism.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The synchronization system transitions from a one-dimensional pairwise connection model to a multi-dimensional network model. Data synchronization is no longer limited to sequential device pairs but operates across a network of devices simultaneously, adding dimensional complexity to enable multi-device support while maintaining consistency through coordinated updates across all connection dimensions.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If manual application running and content opening between devices is used, then device connectivity is maintained, but user convenience deteriorates due to the inconvenient and complex操作流程

Engineering Contradiction:
Improvedevice connectivityVSAvoiduser convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system implements self-service functionality where applications and their associated content are automatically launched and opened across devices without requiring manual user intervention. When a user accesses an application on one device, the system automatically identifies the corresponding content on other devices and opens it seamlessly, eliminating the need for users to manually navigate through multiple devices and operations.

Inventive Principle:
Principle #25Self-service

4Reliability

If client software must be installed locally to backup applications, then backup functionality is achieved, but the backup process becomes cumbersome and inefficient

Engineering Contradiction:
Improvebackup functionalityVSAvoidbackup process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the backup functionality from the requirement of installing full client software on each device. Instead, a lightweight backup agent or service is deployed that provides the essential backup capability without the overhead of complete client software installation. This agent can communicate with a central backup server or cloud service, enabling application backup across multiple devices without requiring each device to run a full client application.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS9779106B2Application management method and device
Publication Date: 2017.10.03 LENOVO (BEIJING) LTD
  • US9779106B2 patent drawing
  • US9779106B2 patent drawing
  • US9779106B2 patent drawing

AI summary

Disclosed are an application management method and device, applied to a first device connected to a second device. The method includes mapping at least one application in the second device, to obtain at least one corresponding application identifier; detecting a first operation; when the first operation satisfies a first preset condition, determining an application identifier of a first application according to the at least one application identifier; detecting a second operation; when the second operation satisfies a second preset condition, obtaining a corresponding application management command according to the second operation; and sending the application management command to the second device, so that the second device manages the first application according to the application management command.