Cross-App Drag Framework Using Metadata Handoff

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing drag functions in applications require software adaptation, limiting data sharing between applications on devices and increasing development workload.

Innovation Solution

A data dragging method that utilizes a drag framework to recognize and execute drag operations without requiring application adaptation, allowing simultaneous execution of drag and non-drag operations, and supports data sharing across devices through a collaborative connection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If an application implements a drag function through software adaptation, then the drag function can be supported, but the application development workload increases

Engineering Contradiction:
Improvedrag function supportVSAvoidapplication development workload
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a drag framework as an intermediary layer between the application and the drag operation. The drag framework includes a drag operation recognition module that handles drag detection and processing, while the application only needs to send messages indicating drag operations without implementing the full drag functionality themselves. This mediator approach allows applications to support drag functions without bearing the full development workload.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The drag framework is designed as a universal solution that can be applied across multiple applications. By implementing the drag operation recognition module at the framework level rather than in each individual application, the system provides multi-functional drag support that benefits all applications using the framework, reducing redundant development effort.

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

2Reliability

If an application handles drag operations independently, then the drag function works, but data sharing between applications is limited

Engineering Contradiction:
Improvedrag operation executionVSAvoiddata sharing capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent merges drag operation handling from individual applications into a unified drag framework. Multiple applications can participate in drag operations through the common framework, enabling data sharing between applications. The drag operation recognition module consolidates drag processing logic, allowing seamless data transfer across application boundaries while maintaining reliable drag functionality.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If the application recognizes and processes drag operations, then the drag function is supported, but the operation response time increases

Engineering Contradiction:
Improvedrag operation recognitionVSAvoidoperation response time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent extracts the time-consuming drag operation recognition and processing logic from the application into the drag framework. The application only needs to perform simple message sending when a drag operation is detected, while the complex recognition and processing is handled by the framework's drag operation recognition module. This extraction reduces the time burden on individual applications.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP4708012A1Data dragging method, and electronic device and storage medium
Publication Date: 2026.03.11 HUAWEI TECH CO LTD
  • EP4708012A1 patent drawingFigure 1A
  • EP4708012A1 patent drawingFigure 1B
  • EP4708012A1 patent drawingFigure 1C

AI summary

This application provides a data dragging method, an electronic device, and a storage medium. The electronic device includes a first application and a first drag operation recognition module. The first application receives a first operation on first data in the first application, where the first operation is a drag operation; the first application sends a first message to the first drag operation recognition module, where the first message indicates that the first operation is the drag operation; and the first drag operation recognition module obtains and saves first metadata information of the first data in response to the drag operation, where the metadata information of the first data includes any one or more of the following: a first data type of the first data, a creation time of the first data, a file size of the first data, an identifier of the application to which the first data belongs, and a storage location of the first data. In this method, after the application recognizes the drag operation, the application does not need to perform the drag operation, but hands over the drag operation to a drag framework for execution, so that workload of application development can be reduced.