Wearable Data Sync via Permissioned App Mediation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data synchronization methods for wearable devices, such as smartwatches, require multiple operations to synchronize data with applications that do not adapt to the wearable device, leading to low efficiency and complexity.

Innovation Solution

A method where a first application on a terminal device starts a second application that has data access permission, allowing the second application to synchronize data from a wearable device to the first application, reducing the need for multiple operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a first application that does not have data access permission receives a data synchronization request, then the application cannot directly access data from the wearable device, but the user must perform multiple data synchronization operations through different applications

Engineering Contradiction:
Improvedata access permissionVSAvoiddata synchronization operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces a second application as an intermediary that has data access permission to the wearable device. When the first application receives a data synchronization request, it triggers the second application to access and synchronize the data. This mediator approach allows the first application to indirectly obtain data without having direct access permission, resolving the contradiction between permission requirements and operational simplicity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent merges the data access functionality of the second application with the data synchronization request of the first application. By combining these two functions, the system allows a single operation in the first application to trigger data synchronization through the permission-holding second application, reducing the need for multiple separate operations while maintaining proper permission control.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If the user performs data synchronization through multiple applications to access wearable device data, then data access permission is maintained, but the synchronization process becomes complex and time-consuming

Engineering Contradiction:
Improvedata access permissionVSAvoiddata synchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-establishing the permission relationship between the second application and the wearable device. When data synchronization is needed, the first application can immediately trigger the pre-configured second application without requiring additional permission setup or multiple sequential operations, thereby reducing synchronization time while maintaining permission security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The second application serves as a mediator that is pre-configured with data access permission. This intermediary enables rapid data retrieval and synchronization when triggered by the first application, eliminating the need for the user to manually navigate through multiple applications and operations, thus reducing time loss while preserving permission control.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If the first application directly accesses data from the wearable device, then data synchronization is simplified, but the application lacks the necessary data access permission

Engineering Contradiction:
Improvedata synchronization operationVSAvoiddata access permission
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent uses the second application as an intermediary that possesses the required data access permission. The first application maintains operational simplicity by triggering the synchronization process, while the second application handles the permission-required data access. This separation allows simplified user interaction without compromising permission security.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If multiple data synchronization operations are performed across different applications, then proper permission control is maintained, but the overall synchronization efficiency decreases

Engineering Contradiction:
Improvepermission controlVSAvoiddata synchronization efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges the permission-holding capability of the second application with the user-initiated synchronization request of the first application. This combination allows a single user operation to trigger a complete data synchronization process that leverages the pre-configured permission relationship, thereby improving efficiency without sacrificing permission control.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The second application acts as an efficient intermediary that is already authorized to access wearable device data. When triggered by the first application, it can immediately retrieve and synchronize data without requiring additional permission checks or multiple operations, thus enhancing synchronization efficiency while maintaining proper permission control through the intermediary's pre-established authorization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260072941A1Data Synchronization Method, Electronic Device, and Computer-Readable Storage Medium
Publication Date: 2026.03.12 HUAWEI TECH CO LTD
  • US20260072941A1 patent drawing
  • US20260072941A1 patent drawing
  • US20260072941A1 patent drawing

AI summary

A data synchronization method implemented by a terminal device includes a first application and a second application. The first application does not have data access permission of a wearable device, and the second application has the data access permission of the wearable device. When a user performs a data synchronization operation on the first application, the first application may start the second application. After the second application starts, the second application may send a data synchronization request to a firmware program of the wearable device, to request the firmware program of the wearable device to synchronize data of the wearable device to the second application. Then, the second application synchronizes, to the first application, the data synchronized by the firmware program of the wearable device.