Cross-Domain Activity View Coordination via Proxy Links

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Devices with multiple operating system domains face challenges in managing cross-domain tasks seamlessly, as applications in different domains have limited access and visibility, hindering a unified and cohesive presentation of related information.

Innovation Solution

The use of proxy links across operating system domains allows for the coordination of transitions between activity views from different domains, enabling the grouping of applications into unified cross-domain tasks, where proxies communicate and manage the presentation as if they belong to a single task, despite being from different OS domains.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple operating system domains are implemented to maintain security and isolation, then security and domain isolation are improved, but task coordination and unified presentation across domains deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoidtask coordination
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a task coordinator as an intermediary component that operates across multiple operating system domains. This coordinator manages task states and coordinates activity views between domains without requiring direct access between domain applications, thus maintaining security isolation while enabling unified task presentation and coordination.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If domain isolation mechanisms are enforced to protect security, then security is improved, but application visibility and access across domains deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoidapplication visibility
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the system into distinct operating system domains with isolated applications, each maintaining its security boundaries. The task coordinator is segmented as a separate entity that can observe and coordinate across domains without applications needing direct cross-domain visibility, thus preserving security while enabling task-level information sharing.

Inventive Principle:
Principle #1Segmentation

3Reliability

If separate operating system domains are used to maintain isolation, then security is improved, but unified task management and cohesive presentation deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoidtask management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The task coordinator is designed as a universal component that operates across all operating system domains with a unified interface and state management mechanism. It provides multi-functional capabilities including task creation, coordination, state tracking, and activity view management across domains, simplifying task management despite the underlying domain complexity.

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

Data Source

PatentEP2963544B1Coordinating activity views across operating system domains
Publication Date: 2020.07.08 BLACKBERRY LTD
  • EP2963544B1 patent drawingFigure 1A~1B
  • EP2963544B1 patent drawingFigure 2
  • EP2963544B1 patent drawingFigure 3

AI summary

A device and its operations are described herein. In some examples, the operations can include executing a first application within a first operating system domain of a device, the first application associated with at least a first activity view. The operations can further include detecting user input associated with the first application. The user input is associated with activating a second activity view of a second application. The operations can further include determining that the second application corresponds to a second operating system domain of the device. The operations can further include establishing a first proxy link within the first operating system domain that corresponds with a second proxy link within the second operating system domain. The first proxy link is associated with causing the second proxy link to invoke the second activity view of the second application within the second operating system domain.