Data Sharing Across Applications Through Resource Access Policies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In scenarios where different applications or devices generate data for separate platforms, there is a lack of efficient data sharing mechanisms, leading to potential disharmony in product styles due to limited user design knowledge, especially in Custom to Manufacture (C2M) scenarios, where uniformity of products is challenging.

Innovation Solution

A data sharing method that involves receiving a data acquisition request, setting resource access control policies to enable entities to access each other's resources, and sending a data acquisition response, including target data, with options for updating or creating temporary access control policies to manage data sharing and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a common service platform is used to centralize data from multiple devices and applications, then data accessibility is improved, but data security and access control become more complex

Engineering Contradiction:
Improvedata accessibilityVSAvoidaccess control complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The access control system is segmented into multiple independent components: access tokens, permission policies, and resource identifiers. Each component handles a specific aspect of access control, making the overall system more manageable and less complex despite serving multiple applications and devices.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary access control mechanism that mediates between applications and device data. The system uses access tokens and permission policies as intermediaries to manage data sharing, reducing the complexity of direct access control while maintaining security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If applications can access each other's data freely on the platform, then data sharing efficiency is improved, but data security and privacy protection deteriorate

Engineering Contradiction:
Improvedata sharing efficiencyVSAvoiddata security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The access control system is dynamic rather than static. Access permissions are granted temporarily through access tokens that have expiration times and specific scope limitations. The system dynamically adjusts access rights based on the specific data sharing needs of each application, enabling efficient data sharing while maintaining security through time-limited and scope-limited permissions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Different access control policies are applied to different applications and data resources. Instead of a uniform access control mechanism, the system implements local quality by tailoring permission settings, token expiration times, and access scopes to the specific requirements of each application-data pair, thereby balancing data sharing efficiency with security.

Inventive Principle:
Principle #3Local quality

3Reliability

If access control policies are strictly enforced for all data access requests, then data security is improved, but system operation complexity and processing time increase

Engineering Contradiction:
Improvedata securityVSAvoidaccess request processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Access control permissions are established in advance through pre-issued access tokens and predefined permission policies. When an application needs to access device data, the system validates the pre-existing token rather than creating access controls in real-time, significantly reducing processing time while maintaining strict security enforcement.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses access tokens as copies or representations of actual access rights. Instead of directly evaluating complex permission rules for each data access request, the system validates the copied token information, which has already encapsulated the access control decisions, thereby reducing processing overhead while maintaining security.

Inventive Principle:
Principle #26Copying

4Productivity

If multiple applications access the same device data, then data utilization efficiency is improved, but the risk of data misuse and conflicts increases

Engineering Contradiction:
Improvedata utilization efficiencyVSAvoiddata misuse risk
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The system changes key parameters of data access control: it introduces time-limited access tokens, scope-limited permissions, and revocable access rights. These parameter changes enable multiple applications to access the same device data simultaneously while controlling the risk of data misuse through expiration mechanisms and scoped permissions that limit potential harm.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12432212B2Data sharing method, apparatus and system, and server and computer storage medium
Publication Date: 2025.09.30 BEIJING BOE TECH DEV CO LTD
  • US12432212B2 patent drawing
  • US12432212B2 patent drawing
  • US12432212B2 patent drawing

AI summary

Provided are a data sharing method, apparatus and system, and a server and a computer storage medium. The data sharing method includes: receiving a data acquisition request from a first entity, wherein the data acquisition request includes an identifier of a resource of a second entity for storing target data, and sharing operation indication information; on the basis of the data acquisition request, setting respective resource access control policies for the first entity and the second entity, such that the first entity and the second entity can access each other's resources to realize data sharing; and sending a data acquisition response to the first entity, wherein the data acquisition response includes the target data.