Task-Context Architecture for Seamless Cross-Device Data Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data sharing methods across multiple devices are cumbersome and inefficient, particularly for creative and productive tasks, as they require manual data transfer and lack a seamless mechanism to share the context of the task, leading to disruptions and inefficiencies.

Innovation Solution

A task-context architecture that allows users to create and share metadata-tagged files across devices, enabling seamless transitions and operations by specifying the file, operation, and target device, thereby maintaining task context and intent, without the need for manual data transfer or cloud access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual data transfer methods are used across multiple devices, then data can be shared between devices, but the process becomes cumbersome and inefficient

Engineering Contradiction:
Improvedata sharing efficiencyVSAvoidoperational complexity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent segments data sharing into distinct task contexts (creation, editing, viewing) and routes them to appropriate devices automatically. Each task context is handled independently through specific pathways (e.g., photo editing tasks routed to devices with editing capabilities), eliminating the need for manual intervention in each data transfer operation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a cloud-based intermediary service that automatically manages data routing between devices. This mediator receives task requests, determines the optimal target device based on task context and device capabilities, and executes the data transfer without user intervention, thereby simplifying the operation while maintaining high productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If cloud access is required for data sharing, then data can be synchronized across devices, but the system becomes dependent on cloud connectivity

Engineering Contradiction:
Improvecross-device compatibilityVSAvoidsystem independence
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a dynamic data sharing architecture that adapts its operation mode based on cloud availability. When cloud services are accessible, it utilizes cloud-based routing for comprehensive device coordination. When cloud connectivity is unavailable, it automatically switches to direct peer-to-peer device communication, maintaining functionality and reliability without constant cloud dependency.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes its operational parameters (communication protocol, data routing path) based on cloud connectivity status. It dynamically adjusts between cloud-mediated transfer and direct device-to-device transfer, ensuring both cross-device compatibility and system independence are maintained under different network conditions.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If task context is not maintained during device transitions, then device switching is simple, but task continuity is disrupted

Engineering Contradiction:
Improvetask continuityVSAvoidsystem architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by pre-tagging data with task context information (task type, required capabilities, user preferences) before device transfer. This advance preparation enables the receiving device to immediately understand and continue the task without requiring complex real-time context analysis, maintaining productivity while managing system complexity through structured data preparation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where task execution status and device capability matching information are continuously communicated back to the routing service. This feedback loop enables intelligent task context maintenance by allowing the system to adjust data routing decisions based on actual task progress and device performance, ensuring task continuity across device transitions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9936018B2Task-context architecture for efficient data sharing
Publication Date: 2018.04.03 MCAFEE LLC
  • US9936018B2 patent drawing
  • US9936018B2 patent drawing
  • US9936018B2 patent drawing

AI summary

To provide a more seamless experience across multiple devices, task streaming systems and methods allow a user to create “task-contexts” and manage metadata of files stored across multiple data storage devices and user preferences associated with capabilities of the multiple devices for operating on the file. Furthermore, the task streaming systems and methods are provided to allow task-contexts to be shared from one device to another device. A task-context specifies one or more files and one or more operations to be performed on the one or more files. By providing a task-context from one device to the other device, a user can accomplish a task with a particular file and seamlessly transition between devices with minimal disruption and effort.