Cross-Device Transient Data Sharing With Hub-Based Security Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is no secure method for sharing transient data between applications on different user devices, and existing solutions like copy-and-paste pose security risks and are limited in data types and sizes.

Innovation Solution

A hub service manages data sharing between devices via local agents, encrypting data, and using a server to convert formats and assess security compliance before transmission, ensuring secure cross-device direct transient data sharing (DTDS) without exposing data to third parties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If copy-and-paste technology is used for data sharing, then data can be transferred between applications, but security is compromised because the clipboard is accessible by multiple applications including untrustworthy ones

Engineering Contradiction:
Improvedata sharing capabilityVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a hub service as an intermediary that mediates data sharing between devices. Instead of direct clipboard access between applications, data flows through the hub service which enforces security policies, authentication, and authorization. This mediator resolves the contradiction by enabling data sharing operationally while maintaining security through controlled access mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent uses DTDS (Direct Transient Data Sharing) which transfers data directly between applications through IPC mechanisms without creating persistent copies in accessible storage like the clipboard. This copying mechanism enables data transfer while preventing unauthorized access because the data exists only transiently in memory and is not exposed to the general application environment.

Inventive Principle:
Principle #26Copying

2Ease of operation

If traditional copy-and-paste is used, then data sharing between applications is possible, but data size is limited and only tags or links can be shared rather than underlying data

Engineering Contradiction:
Improvedata sharingVSAvoiddata size
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The hub service provides a universal data sharing platform that handles multiple data types and sizes through a single mechanism. Unlike copy-and-paste which is limited to text and small data, the hub service can transfer images, videos, documents, and large datasets by leveraging the underlying DTDS capability and network transmission, making the system multi-functional for various data sharing needs.

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

Solution Approach 2:

The patent replaces the mechanical clipboard system with an electronic DTDS-based transmission system. Instead of relying on OS-level clipboard buffers with size limitations, the system uses direct memory-to-memory transfer mechanisms combined with network protocols, substituting the mechanical constraint-based system with an electronic system that has much higher capacity and flexibility.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Device complexity

If cross-device data sharing is implemented without a hub service, then device complexity is reduced, but security risk increases due to lack of centralized control and policy enforcement

Engineering Contradiction:
Improvesystem architectureVSAvoidsecurity
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent adds a new dimensional layer to the data sharing architecture by introducing the hub service as a centralized coordination point. Instead of peer-to-peer direct sharing between devices, the hub service creates a managed dimension where authentication, authorization, and policy enforcement occur. This additional layer manages security without significantly increasing device-level complexity since the hub operates as a separate service.

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

4Reliability

If DTDS is used for cross-device sharing, then security is improved through IPC mechanisms, but compatibility issues arise between different operating systems

Engineering Contradiction:
ImprovesecurityVSAvoidOS compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The hub service acts as an intermediary that handles OS compatibility translation. Each device runs a local agent that communicates with the hub service, which mediates between different OS platforms. The hub service receives data from one OS type, translates or adapts it according to the destination OS requirements, and forwards it appropriately, thus resolving compatibility issues while maintaining the security benefits of DTDS on each platform.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes parameters such as data format, encoding, and protocol to accommodate different operating systems. The hub service detects the OS type of the destination device and adjusts transmission parameters accordingly, converting data between formats and protocols while maintaining security. This parameter adaptation enables cross-OS compatibility without compromising the underlying DTDS security mechanism on each platform.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12481774B2Secure cross-device direct transient data sharing
Publication Date: 2025.11.25 OMNISSA LLC
  • US12481774B2 patent drawing
  • US12481774B2 patent drawing
  • US12481774B2 patent drawing

AI summary

Systems and methods can allow for secure cross-device sharing of transient data using direct transient data sharing (“DTDS”). A source destination can share data using local DTDS with an agent on a first device. The agent can send the data to a hub server that runs a security control process and data formatting process. The hub server can determine risk scores for the source and destination devices and allow the sharing to occur if a safety threshold is met. Then an agent on the destination device can receive the transient data and use local DTDS to send the data to a destination application.