Trusted Execution Environment for Secure Data Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data sharing techniques are inadequate for low-power environments like mobile phones and IoT devices, as they rely on cloud-based systems that are costly, inflexible, and vulnerable to software exploits, and often require sensitive data to be stored in the cloud, undermining security and limiting access control options.

Innovation Solution

A peer-to-peer data sharing system using a trusted execution environment (TEE) on the receiver device for granular access control, where the TEE provides a root of trust for local data access and enforces access policies cryptographically, eliminating the need for a cloud server and enhancing security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cloud-based systems are used for data sharing, then centralized access control can be implemented, but cost increases and flexibility decreases

Engineering Contradiction:
Improveaccess controlVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the trusted hardware security module from the cloud server and places it on the receiver's device. This removes the dependency on cloud-based infrastructure for security operations, reducing system complexity and cost while maintaining access control reliability. The receiver's device becomes self-sufficient for cryptographic operations.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The receiver's device performs cryptographic operations locally using its own trusted hardware module, eliminating the need for cloud server intervention in decryption processes. This self-service approach reduces operational costs and increases flexibility while maintaining security.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If data is stored in the cloud, then centralized management is achieved, but security is undermined and access control options are limited

Engineering Contradiction:
Improvedata managementVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

Instead of centralizing data in the cloud and managing access remotely, the patent inverts the approach by placing the security trust anchor in the receiver's local device. Data can be distributed or stored locally, and access control is enforced through the local trusted module rather than remote cloud management.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The trusted hardware security module acts as an intermediary between the encrypted data and the processing system. It provides the root of trust locally, enabling secure data management without requiring cloud-based intermediaries for cryptographic operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If software-based policy engines are used, then access policies can be enforced, but the system becomes vulnerable to software exploits

Engineering Contradiction:
Improvepolicy enforcementVSAvoidsoftware exploits
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent replaces software-based policy enforcement with hardware-based cryptographic enforcement. The trusted hardware security module executes cryptographic operations that inherently enforce access policies, eliminating the vulnerability to software exploits while maintaining policy enforcement reliability.

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

Solution Approach 2:

The trusted hardware module provides beforehand protection by cryptographically enforcing access policies before data is decrypted or accessed. This prevents software exploits from interfering with policy enforcement, as the cryptographic checks are performed in a protected hardware environment.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Ease of operation

If cloud servers are used for decryption, then centralized control is maintained, but security of the link between server and receiver is compromised

Engineering Contradiction:
Improvecentralized controlVSAvoidlink security
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the decryption capability from the cloud server and places it in the receiver's trusted hardware module. This eliminates the need for secure communication channels between server and receiver for decryption operations, as decryption occurs locally in the protected hardware environment.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The receiver's device performs decryption operations independently using its local trusted hardware module, without requiring cloud server participation in the decryption process. This self-service approach eliminates link security vulnerabilities while maintaining centralized control through key management.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11347882B2Methods and systems for secure data sharing with granular access control
Publication Date: 2022.05.31 HUAWEI TECH CO LTD
  • US11347882B2 patent drawing
  • US11347882B2 patent drawing
  • US11347882B2 patent drawing

AI summary

Methods and devices for secure data sharing with granular access control are described. A modified attribute-based encryption (ABE) scheme is used to perform cryptographically-enforced ABE using attributes of a file access policy. A sender sends to a receiver a file encrypted using a file encryption key, the file encryption key encrypted using ABE based on a file access policy set by the sender, and a set of private ABE keys decryptable using a key stored in a trusted execution environment (TEE) of the receiver. The private ABE keys are decrypted by the receiver TEE when the file is accessed, decrypting a file encryption key only when the attributes of the receiver access action satisfy the file access policy. The decrypted file encryption key grants access to the file contents via a trusted viewer application. A user password may also be required and cryptographically enforced as part of the ABE decryption.