Trusted Execution Environment for Tamperproof Data Usage Records
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In data sharing platforms, the lack of a tamperproof mechanism to record and verify data usage leads to potential cheating by platforms, where user data is rolled back to eliminate usage traces, making it difficult for data providers to track and charge for data usage accurately.
Innovation Solution
Implementing a method that uses a Trusted Execution Environment (TEE) to execute operation codes, generate operation logs, and increment execution counts, which are then combined into operation records stored on a blockchain-type ledger, ensuring an undeniable and tamperproof record of data usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the platform stores and manages operation records centrally, then data sharing and processing efficiency is improved, but the platform can potentially cheat users by rolling back data to eliminate usage traces
Solution Approach 1:
The patent introduces a TEE (Trusted Execution Environment) as an intermediary between the platform and operation records. The TEE executes operation codes in an isolated, verified environment that cannot be manipulated by the platform, ensuring that operation records are generated truthfully while still allowing efficient centralized management. This mediator prevents the platform from rolling back or tampering with records.
Solution Approach 2:
The patent replaces the traditional mechanical/centralized record storage system with a blockchain-based distributed ledger. Instead of relying on the platform's central database that can be manipulated, the system uses blockchain's immutable chain of blocks to store operation records, making them tamper-proof while maintaining accessibility for data sharing operations.
2Reliability
If operation records are stored on a blockchain-type ledger, then tamperproof and verifiable records are achieved, but system complexity increases
Solution Approach 1:
The patent segments the system into distinct functional modules: a TEE module for executing operation codes, a blockchain module for storing operation records, and a database server for additional data management. This segmentation allows each component to perform its specific function independently, reducing overall system complexity while achieving tamperproof records through the blockchain component.
Solution Approach 2:
The blockchain-type ledger serves multiple functions: it stores operation records, provides tamperproof verification, enables audit trails, and maintains data integrity. By making the blockchain multi-functional, the patent reduces the need for separate specialized systems, thereby reducing overall complexity while achieving reliable tamperproof records.
3Reliability
If a TEE is used to execute operation codes, then operation record authenticity is ensured, but execution time and computational resources increase
Solution Approach 1:
The patent applies partial action by executing only the necessary operation codes within the TEE rather than all possible operations. The TEE selectively executes codes related to data usage tracking while leaving other operations to conventional environments, reducing unnecessary computational overhead while ensuring authenticity for critical operations.
Solution Approach 2:
The patent uses copying by creating a simplified representation of operation records in the blockchain ledger rather than storing all raw execution data. This copy approach reduces the amount of data that needs to be processed and verified in the TEE, decreasing execution time while maintaining the essential authenticity and verification capabilities.
Data Source
AI summary
In an implementation, operation instructions indicating application data to be used for performing one or more operations sent by a first client device are received. The application data is determined based on the operation instructions. One or more second client devices associated with the application data are determined. Operation codes in a trusted execution environment (TEE) associated with the application data to be executed are determined. That the operation codes has been executed for K times based on an indicator is determined. The operation codes are executed in the TEE based on the application data to generate an operation log. An indicator indicating a number of times the operation codes are executed is updated. The operation log and the indicator are sent as an operation record to a database server, the first client device, and the one or more second client devices to be stored.