Construction method of trusted data space connector

Abstract

The invention belongs to the field of data element safety circulation, and particularly relates to a method for constructing a trusted data space connector. Specifically, a strategy enforcement mechanism based on a trusted execution environment (TEE) is constructed, through hardware-level isolation and remote verification, it is ensured that data is only used under the condition meeting the strategy, the whole process can be audited and verified, and objective trust which does not depend on any participant is established.

Description

Technical Field

[0001] This invention belongs to the field of secure data element circulation, specifically a method for constructing a trusted data space connector. Background Technology

[0002] With the rapid development of the global digital economy, the demand for data circulation and sharing has surged. The National Data Standardization Technical Committee released the "Trusted Data Space Technical Architecture TC609-6-2025-01," which states that a trusted data space is a key infrastructure supporting the trusted circulation of data elements. Connectors are a core component of the trusted data space, responsible for enabling secure, reliable, and controllable data interaction between data providers and users.

[0003] However, existing technologies rely on parsing and executing policy contracts in the local environment of the data user or provider, making it difficult to ensure the consistency and enforceability of rules in heterogeneous and open environments. Furthermore, limited by insufficient verifiability and tamper-proof capabilities in the data usage process, the policy execution of existing technologies depends on the trustworthiness of the local system and lacks a verifiable mechanism for the execution environment itself, thus failing to effectively prevent unauthorized access or tampering of data during use.

[0004] Therefore, it is urgent to improve the technical defects in the existing technical solutions in order to enhance the reliability of existing connectors in the data access process. Summary of the Invention

[0005] The purpose of this invention is to propose a method for constructing a trusted data space connector, which, compared with existing technical solutions, solves the problems of low reliability and susceptibility to tampering in the data access process of existing technical solutions.

[0006] To achieve the above objectives, the present invention provides the following technical solution: A method for constructing a trusted data spatial connector includes the following steps: Step S1: The data provider executes the digital contract signed with the data user through the data delivery module. The data delivery module generates a data capsule containing the encrypted original data, the data key of the original data, and the usage policy. The data capsule is delivered to the trusted cloud storage of the capsule consumption TEE through the data delivery module. The data key is the key of the original data, and the original data is provided by the data provider. Step S2: The data user submits a usage request to the capsule consumption TEE. The capsule consumption TEE authenticates the data user and checks the usage request according to the usage policy. After the verification and check in step S2 are passed in step S3, the capsule consumption TEE processes the data capsule, decrypts the original data, and the data user uses the original data within the capsule consumption TEE. After use, the capsule consumption TEE updates the status of the usage strategy.

[0007] The above technical solution produces the following technical effects: This invention addresses how to deeply encapsulate complex data usage rules (such as frequency, time, and operation type) with the data itself into a "data capsule," making it a portable and automatically parsed governance unit. This ensures that policies flow with the data and can be reliably executed in any environment. Furthermore, because this application constructs a policy enforcement mechanism based on a Trusted Execution Environment (TEE), through hardware-level isolation and remote verification, it ensures that data is used only under conditions that comply with the policy, and that the entire process is auditable and verifiable, establishing objective trust independent of any participating party.

[0008] As a further improvement to the method for constructing a trusted data space connector of this application, the process of a data provider and a data user entering into a digital contract includes the following steps: Step S101: After discovering the target data product uploaded by the data provider in the data market, the data user applies to use the data product. The data product includes raw data and product information. Step S102: The data user sets or modifies the usage strategy according to its own needs in the data contract management module; Step S103: After receiving the usage policy, the data provider reviews whether the usage policy is permitted. If rejected, the data user shall edit and resubmit the usage policy. If permitted, proceed to step S104; Step S104: The data contract management module generates a digital contract containing basic contract information, details of the data product, usage strategy, and binding terms; Step S105: The data user and the data provider sign the digital contract according to their respective IBS private keys to complete the conclusion of the digital contract.

[0009] As a further improvement to the method for constructing a trusted data spatial connector of this application, the process of packaging data capsules in step S1 includes the following steps: Step S111: Encrypt the original data to generate a data key corresponding to the original data. The data key is a symmetric data key. Step S112: Encrypt the data key using the IBE public key corresponding to the identity of the data user; Step S113: The data key encrypted with the IBE public key, the encrypted original data, and the usage strategy are packaged to form a data capsule.

[0010] As a further improvement to the construction method of the trusted data space connector of this application, the product information includes: Basic information: data provider, product name, product description, and product format; Usage policy: Preset product usage methods, product usage regions, and whether the product is allowed to be downloaded; Legal constraints: Pre-defined breach of contract scenarios, handling measures, and dispute resolution methods.

[0011] As a further improvement to the construction method of a trusted data space connector of this application, in step S101, the data product is uploaded to the data market by the data provider through the data asset management principle module; Data providers fill in product information and create data products in the data asset management principle module according to the digital contract template. After the data product passes the review process of the data asset management principle module, it is listed on the data marketplace.

[0012] As a further improvement to the construction method of a trusted data space connector of this application, the data provider or data user registers through the user management module. After registration, the user management module provides the data provider or data user with a cryptographic key. Cryptographic keys include the IBE private key and the IBS private key; The IBE private key is used for encrypting and decrypting the identity of the data provider or data user. The IBS private key is used for identity signing by the data provider or data user.

[0013] As a further improvement to the construction method of the trusted data space connector of this application, in step S2, the capsule consumption TEE verification and inspection process includes the following steps: Step S201, Submit a usage request: The data user submits a usage request to the capsule consumer TEE. The usage request includes the data user's IBE private key, the ID of the data capsule to be used, and the specific operation to be performed on the data capsule. Step S202, Identity Verification: The capsule consumption TEE retrieves the corresponding data capsule based on the data capsule's ID and decrypts the encrypted data key using the IBE private key; If decryption fails, the authentication process is terminated. If decryption is successful, proceed to step S203; Step S203, Compliance Check: The capsule consumption TEE performs a check based on the usage request and the usage policy in the data capsule; If the inspection fails, the compliance inspection process will be terminated. If the check passes, proceed to step S3.

[0014] As a further improvement to the construction method of the trusted data space connector of this application, in step S203, the usage request is checked according to the usage policy as follows: Determine if the allowed number of uses in the usage strategy is greater than 0; Determine whether the usage time requested is within the validity period of the contract for the usage strategy; Determine whether the operation requested is within the column-level operation restrictions of the usage strategy.

[0015] As a further improvement to the method for constructing a trusted data space connector of this application, in step S3, the capsule consuming TEE processes the data capsule, including the following steps: Step S301: The capsule consumer TEE uses the decrypted data key in memory to decrypt the original data; Step S302: The user of capsule consumption TEE management data uses the raw data within the scope permitted by the usage policy in the capsule consumption TEE; Step S303: After the original data is used up, it is cleared from memory by the capsule consumption TEE.

[0016] As a further improvement to the method for constructing a trusted data space connector of this application, the strategies used include: Basic information, including data provider, data user, data creator, data creation time, data provider's signature, and data user's signature; The product name, product description, and data format of the data product; Usage policies include preset usage methods, start date, end date, allowed access count, usage region, and whether downloads are allowed; The legal constraints on data products include pre-defined breach scenarios, handling measures, scope of compensation, and dispute resolution methods. Attached Figure Description

[0017] Figure 1 This is a flowchart illustrating the construction method of the trusted data space connector of the present invention. Figure 2 This is a flowchart illustrating the workflow of a digital contract between a data provider and a data user in this invention. Figure 3 This is a flowchart illustrating the process of packaging data capsules in this invention. Figure 4 A flowchart illustrating the process of verifying and inspecting the capsule-based TEE in this invention; Figure 5This is a schematic diagram of the strategy used in this invention; Figure 6 This is a flowchart illustrating the data capsule processing workflow of the capsule consumption TEE in this invention. Figure 7 This is a schematic diagram of the trusted data space connector structure in this invention; Figure 8 This is a flowchart illustrating the workflow of the trusted data space connector in this invention. Detailed Implementation

[0018] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0019] To facilitate an accurate understanding of the solutions provided in the following embodiments of the present invention, the terms involved in the present invention will be explained as follows before describing the technical solutions provided by the present invention: Trusted Execution Environment (TEE) is a hardware-isolated security technology whose core goal is to provide an isolated and protected computing space for sensitive code and data. Even if the device's main operating system, hypervisor, or cloud service provider is attacked or becomes untrusted, the TEE can ensure the security of the data and computation processes within it. Its implementation primarily relies on processor-level hardware support, achieved by creating an independent secure region within the CPU (such as Intel SGX's "Enclave" or ARM TrustZone's "Secure World"). This secure region has its own memory space and is strictly isolated from the external environment through hardware mechanisms.

[0020] Data capsules are an innovative data security governance and encapsulation technology. They are not simply data encryption, but rather a deep binding of encrypted data content with its usage control policies and security metadata, forming an indivisible and securely transferable governance unit. The core idea is to allow data itself to "carry" access rules, ensuring that data, regardless of where it is stored or transferred, follows the data owner's wishes, achieving the goals of "policy changes without data movement" or "controllable data flow."

[0021] A symmetric data key is a key used in symmetric encryption algorithms, the core feature of which is that the same key is used for both encryption and decryption. In the technical solution of this invention, the symmetric data key is used to encrypt the original data to ensure the security of the data during storage and transmission.

[0022] IBE (Identity-Based Encryption) is characterized by using user identity information (such as username and email address) directly as the public key, eliminating the need for pre-exchanging or managing traditional public key certificates. In this invention, the system issues an IBE private key to the user. Data users must use this private key to decrypt the "IBE-encrypted data key" in the data capsule to complete authentication and access control, ensuring that only authorized users can obtain the data key.

[0023] IBS (Identity-Based Signature) verifies the validity of a signature through user authentication without relying on third-party certificates. In this application, the system issues an IBS private key to the user. Data providers and users use this private key to sign digital contracts, ensuring the integrity of the contract (unaltered) and the non-repudiation of the signing action (unable to deny the signing operation). This directly binds the signature to the user's identity, simplifying the signature verification process and making it suitable for scenarios requiring explicit identity attribution, such as contract signing and data notarization.

[0024] In the construction of the space connector, this application has discovered numerous technical defects, such as: 1. Existing technologies rely on parsing and executing policy contracts in the local environment of the data user or provider, making it difficult to ensure the consistency and enforceability of rules in heterogeneous and open environments. Therefore, this application aims to address how to deeply encapsulate complex data usage rules (such as frequency, time, and operation type) with the data itself into a "data capsule," making it a portable and automatically parsed governance unit, ensuring that policies flow with the data and can be reliably executed in any environment.

[0025] 2. Data usage presents challenges in verifiability and tamper-proofing. Existing policies rely on the trustworthiness of the local system for enforcement, lacking a verifiable mechanism for the execution environment itself, thus failing to prevent unauthorized access or tampering of data during use. Therefore, this invention is motivated by the need to construct a policy enforcement mechanism based on a Trusted Execution Environment (TEE). Through hardware-level isolation and remote verification, it ensures that data is used only under policy-compliant conditions, and that the entire process is auditable and verifiable, establishing objective trust independent of any participating party.

[0026] 3. Regarding the issue of defining responsibilities for data use, existing solutions, while introducing electronic contracts, separate contracts from data. The execution process relies on self-recording by participating parties, which can easily lead to disputes such as self-verification, incomplete logs, or tampering. This invention aims to achieve a unified encapsulation of data, strategies, and digital contracts, and automatically record each data usage behavior in a trusted environment, generating tamper-proof electronic credentials. This technically enables automatic definition of responsibilities and full traceability of behavior, supporting legally valid data use evidence preservation.

[0027] The following detailed description is exemplary and intended to provide further detailed explanation of the invention. Unless otherwise specified, all technical terms used in this invention have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this invention is for describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention.

[0028] Example 1 like Figure 1-6 As shown, in order to address the numerous technical shortcomings of the aforementioned technical solutions, this application designs a method for constructing a trusted data space connector, comprising the following steps: Step S1: The user completes registration in the "User Management Module," clearly identifying themselves as either a data provider or a data user. Upon successful registration, the system issues each user two sets of cryptographic keys: an IBE private key and an IBS private key. The IBE private key is used for encryption and decryption of the data provider's or data user's identity. In subsequent processes, the data user uses this private key to decrypt and obtain the data key, thereby completing authentication and access control. The IBS private key is used for identity signing by the data provider or data user. Both parties use this private key to digitally sign digital contracts, ensuring the integrity of the contract and the non-repudiation of the signing action.

[0029] Furthermore, the process of data providers and data users entering into digital contracts includes the following steps: Step S101: After discovering the target data product uploaded by the data provider in the data market, the data user applies to use the data product. The data product includes raw data and product information. Step S102: The data user sets or modifies the usage strategy according to its own needs in the data contract management module; specifically, the data user sets or modifies the specific usage strategy (such as adjusting the number of uses, time, and specific column-level operations) according to its own needs in the data contract management module. Step S103: After receiving the usage policy, the data provider reviews whether the usage policy is permitted. If rejected, the data user shall edit and resubmit the usage policy. If permitted, proceed to step S104; Step S104: The data contract management module generates a digital contract containing basic contract information, details of the data product, usage strategies, and binding clauses. After approval, the system automatically generates a structured "Digital Contract." Specifically, the contract content integrates at least the following: 1) Basic Contract Information: Names of both parties (provider, user), creator, and creation time (create_time). Details of the data product involved in this transaction (name, description, format).

[0030] 2) The usage policy agreed upon by both parties for this transaction (start_date, end_date, usage_region, usage_policy, usage_count, etc.).

[0031] 3) Legally binding binding clauses (violation_types, penalty_measures, compensation, dispute_resolution).

[0032] Furthermore, in step S105, the data provider and the data user each use their respective IBS private keys to sign the contract (provider_signature, user_signature), thus completing a legally binding digital contract.

[0033] Specifically, in step S101, the data product is uploaded to the data marketplace by the data provider through the data asset management principle module; the data provider fills in the product information and creates the data product in the data asset management principle module according to the digital contract template, and after the data product passes the review process of the data asset management principle module, the data product is listed on the data marketplace.

[0034] For specific product information, please refer to the usage strategy (specifically, as follows). Figure 5 Configure the information shown in the diagram, specifically including: Basic information, including data provider, data user, data creator, data creation time, data provider's signature, and data user's signature; The product name, product description, and data format of the data product; Usage policies include preset usage methods, start date, end date, allowed access count, usage region, and whether downloads are allowed; The legal constraints on data products include pre-defined breach scenarios, handling measures, scope of compensation, and dispute resolution methods.

[0035] Furthermore, the data provider executes the digital contract signed with the data user through the data delivery module. The data delivery module generates a data capsule containing the encrypted original data, the data key for the original data, and the usage policy. The data capsule is delivered to the trusted cloud storage of the capsule consumption TEE through the data delivery module. The data key is the same as the key for the original data, which is provided by the data provider. In the above process, this application adopts a data capsule mechanism. This mechanism separates the data user from the data provider, ensuring the security and controllability of the data throughout its entire lifecycle. Specifically, the data capsule acts like a highly secure container, tightly encapsulating the original data, the corresponding key, and the usage policy together. The encrypted original data is securely stored in the trusted cloud storage of the capsule consumption TEE, which enhances the trustworthiness and security of the data storage environment.

[0036] Furthermore, in another specific implementation, the process of packaging data capsules according to this application includes the following steps: Step S111: Encrypt the original data to generate a data key corresponding to the original data. The data key is a symmetric data key. Step S112: Encrypt the data key using the IBE public key corresponding to the identity of the data user; Step S113: The data key encrypted with the IBE public key, the encrypted original data, and the usage strategy are packaged to form a data capsule.

[0037] In the aforementioned packaging process, when generating the data capsule, the data provider first encrypts the original data using a symmetric encryption algorithm, simultaneously generating a corresponding symmetric data key. Then, the symmetric data key is encrypted using the data user's IBE public key (identity-based encryption public key), resulting in an "IBE-encrypted data key." Finally, the encrypted original data, the IBE-encrypted data key, and the usage policy are packaged together into an indivisible "data capsule," achieving secure data encapsulation and delivery. This design combines the efficiency of symmetric encryption (suitable for encrypting large amounts of data) with the security of asymmetric encryption (encrypting the symmetric key with the IBE public key ensures the key can only be decrypted by the designated user), representing a typical application of hybrid encryption schemes and ensuring both efficiency and security during data transfer.

[0038] Furthermore, it is worth noting that during the use of the data capsule in this application, the data capsule is not directly sent to the data user, but is delivered to a neutral, trusted cloud storage. Thus, the data is removed from the provider's control and enters a managed state subject to policy and code constraints. This technical solution innovatively introduces a "data capsule" encapsulation mechanism: encrypted data, usage policy, and IBE-encrypted data keys are packaged into an indivisible governance unit. The usage policy explicitly defines the types of executable operations (such as column computation, SQL queries, specific machine learning algorithms, etc.) in the form of a whitelist, and the corresponding execution program is pre-installed in the consumer capsule TEE; the data provider defines the allowed scope of operations during the encapsulation process, and the consumer capsule TEE strictly controls data usage based on this whitelist. The capsule itself integrates policy parsing and execution logic, and can be transferred to the cloud or any third-party environment along with the data flow, achieving "policy embedding and data autonomy," fundamentally eliminating the problems of policy and data being disconnected and execution relying on external trusted systems.

[0039] Furthermore, it should be noted that while existing technical solutions utilize trusted hardware and Trusted Execution Environments (TEEs), the specific technical implementation and verifiable mechanisms of these environments are not clearly defined. In essence, existing technical solutions still fall under the category of "trusted software stacks." This application implements the mandatory enforcement of policies based on a hardware-level trusted execution environment (TEE): all data decryption, policy compliance checks, and computation execution are completed within the TEE, and a remote authentication mechanism is supported, allowing participating parties to verify the integrity and trusted status of the TEE. This design ensures that even if the hosting provider or host operating system is untrusted, data and policies remain secure, thereby guaranteeing the verifiability and tamper-proof nature of the execution process at the hardware level.

[0040] Step S2: The data user submits a usage request to the capsule consumption TEE. The capsule consumption TEE authenticates the data user and checks the usage request according to the usage policy. The process of validating and inspecting capsule consumer TEEs includes the following steps: Step S201: Submit a usage request: The data user submits a usage request to the capsule consumer TEE. The usage request includes the data user's IBE private key, the ID of the data capsule to be used, and the specific operation to be performed on the data capsule (e.g., count a column). Step S202, Identity Verification: The capsule consumption TEE retrieves the corresponding data capsule based on the data capsule's ID and decrypts the encrypted data key using the IBE private key; Specifically, the Capsule Consumption TEE retrieves the corresponding data capsule from trusted cloud storage based on the submitted data capsule ID. The Capsule Consumption TEE then attempts to decrypt the "IBE-encrypted data key" within the data capsule using the user-submitted IBE private key. If decryption fails (private key and public key do not match), "authentication failed" is returned and the process terminates; If decryption is successful, proceed to step S203; Step S203, Compliance Check: The capsule consumption TEE performs checks based on the usage request and the usage policy in the data capsule; among which, the usage request is checked according to the usage policy as follows: Determine if the allowed number of uses in the usage policy is greater than 0 (usage_count); Determine whether the usage time of the request is within the validity period of the contract for the usage strategy (start_date to end_date); Determine whether the operation requested (such as count) is within the column-level operation restrictions of the usage policy (usage_policy).

[0041] If the inspection fails, the compliance inspection process will be terminated. That is, if any inspection fails, a "policy rejection" error will be returned and the process will be terminated. If the check passes, proceed to step S3.

[0042] After the verification and check in step S2 are passed in step S3, the capsule consumption TEE processes the data capsule, decrypts the original data, and the data user uses the original data within the capsule consumption TEE. After use, the capsule consumption TEE updates the status of the usage strategy.

[0043] Specifically, in step S3, the capsule consumption TEE processes the data capsule, including the following steps: Step S301: The capsule consumer TEE uses the decrypted data key in memory to decrypt the original data; Step S302: The user of the capsule consumption TEE manages the data and uses the original data within the scope permitted by the usage policy. The capsule consumption TEE implements an automatic execution program for the policy, which only performs the operations explicitly permitted by the policy on the decrypted data (e.g., only performing aggregation calculations on specified columns, while other columns are not visible).

[0044] Step S303: After the raw data is used, it is cleared from memory by the capsule-consumed TEE. Only the final calculation result (such as a statistic) is returned to the data user. The raw data never leaves the trusted environment throughout the entire process.

[0045] Furthermore, in the capsule consumption TEE, steps S301-S303 above can be reused repeatedly: the data user can "submit usage method" multiple times. Each time, the verification, checking, and execution process of steps 2 to 4 will be repeated until the strategy resources (such as the number of uses) are exhausted or the contract expires.

[0046] It is worth noting that while existing technologies also mention electronic contract notarization, the separation of the contract from the data usage process makes it difficult to reflect the data status in real time. This solution, through a two-way binding between digital contracts and data capsules, ensures that after each data usage, the consumer capsule (TEE) updates the data capsule status in real time and immutably based on the strategy execution results, guaranteeing that the data status remains synchronized with the contract agreement. This mechanism achieves closed-loop management of synchronized status and verifiable operations at the technical level, providing an objective and real-time basis for defining rights and responsibilities.

[0047] Example 2 like Figure 7-8 As shown, unlike Embodiment 1, this invention constructs a connector for a trusted data space based on data capsule encapsulation technology and a trusted execution environment, enabling secure point-to-point data flow between data providers and data users. It includes: an identity management module, a data resource management module, a data product management module, a digital contract management module, a data delivery module, and a data usage control module. The system comprises several modules: Identity Management for user registration and login; Data Resource Management for managing data uploaded by data providers; Data Providers creating data products using the Data Product Management module, submitting them to the service platform for review before listing them; and Data Providers and Data Users negotiating and signing digital contracts through the Digital Contract Management module to determine the usage strategy for the data products. Finally, Data Providers deliver data products to Data Users via the Data Delivery module, and Data Users utilize the Data Usage Control module to use the data under the agreed-upon usage strategy.

[0048] Other aspects that are the same as in Example 1 will not be repeated in this example.

[0049] It is noteworthy that those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0050] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, as well as combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0051] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0052] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0053] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

[0054] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus.

[0055] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for constructing a trusted data spatial connector, characterized in that, Includes the following steps: Step S1: The data provider executes the digital contract signed with the data user through the data delivery module. The data delivery module generates a data capsule containing encrypted original data, a data key for the original data, and a usage strategy. The data capsule is delivered to the trusted cloud storage of the capsule consumption TEE through the data delivery module. The data key is the key for the original data, and the original data is provided by the data provider. Step S2: The data user submits a usage request to the capsule consumption TEE. The capsule consumption TEE authenticates the data user and checks the usage request according to the usage policy. Step S3: After the verification and check in step S2 are passed, the capsule consumption TEE processes the data capsule, decrypts the original data, and the data user uses the original data within the capsule consumption TEE. After use, the capsule consumption TEE updates the status of the usage strategy.

2. The method for constructing a trusted data spatial connector according to claim 1, characterized in that, The process by which the data provider and the data user enter into the digital contract includes the following steps: Step S101: After discovering the target data product uploaded by the data provider in the data marketplace, the data user applies to use the data product, which includes the original data and product information; Step S102: The data user sets or modifies the usage strategy in the data contract management module according to its own needs; Step S103: After receiving the usage policy, the data provider reviews whether the usage policy is allowed. If rejected, the data user must edit the usage policy and resubmit it. If permitted, proceed to step S104; Step S104: The data contract management module generates the digital contract containing basic contract information, details of the data product, usage strategy, and constraint terms; Step S105: The data user and the data provider sign the digital contract according to their respective IBS private keys to complete the conclusion of the digital contract.

3. The method for constructing a trusted data spatial connector according to claim 2, characterized in that, In step S1, the process of packaging the data capsule includes the following steps: Step S111: Encrypt the original data to generate the data key corresponding to the original data, wherein the data key is a symmetric data key; Step S112: Encrypt the data key using the IBE public key corresponding to the identity of the data user; Step S113: The data capsule is formed by packaging the data key encrypted with the IBE public key, the encrypted original data, and the usage strategy.

4. The method for constructing a trusted data spatial connector according to claim 2, characterized in that, In step S101, the data product is uploaded to the data marketplace by the data provider through the data asset management principle module; The data provider fills in the product information and creates the data product according to the digital contract template in the data asset management principle module. After the data product passes the review process of the data asset management principle module, the data product is listed on the data marketplace.

5. The method for constructing a trusted data spatial connector according to claim 2, characterized in that, The data provider or the data user registers through the user management module. After registration, the user management module provides a cryptographic key to the data provider or the data user. The cryptographic key includes the IBE private key and the IBS private key; The IBE private key is used for encrypting and decrypting the identity of the data provider or the data user. The IBS private key is used for identity signing by the data provider or the data user.

6. The method for constructing a trusted data spatial connector according to claim 1, characterized in that, In step S2, the process of verifying and inspecting the capsule-based consumer TEE includes the following steps: Step S201: Submit the usage request: The data user submits a usage request to the capsule consumption TEE. The usage request includes the data user's IBE private key, the ID of the data capsule to be used, and the specific operation to be performed on the data capsule. Step S202, Identity Verification: The capsule consumption TEE retrieves the corresponding data capsule based on the ID of the data capsule, and decrypts the encrypted data key using the IBE private key; If decryption fails, the authentication process is terminated. If decryption is successful, proceed to step S203; Step S203, Compliance Check: The capsule consumption TEE performs a check based on the usage request and the usage policy in the data capsule; If the inspection fails, the compliance inspection process will be terminated. If the check passes, proceed to step S3.

7. The method for constructing a trusted data spatial connector according to claim 6, characterized in that, In step S203, the usage request is checked according to the usage policy as follows: Determine whether the allowed number of uses in the usage strategy is greater than 0; Determine whether the usage time of the usage request is within the contract validity period of the usage strategy; Determine whether the operation requested by the user is within the column-level operation restrictions of the usage policy.

8. The method for constructing a trusted data spatial connector according to claim 1, characterized in that, In step S3, the capsule-consuming TEE processes the data capsule, including the following steps: Step S301: The capsule consumption TEE decrypts the original data in memory using the decrypted data key; Step S302: The capsule consumption TEE manages the data user to use the raw data within the permitted scope of the usage strategy in the capsule consumption TEE; Step S303: After the original data is used up, it is cleared from memory by the capsule consumption TEE.

9. The method for constructing a trusted data spatial connector according to claim 2, characterized in that, The usage strategy includes: Basic information, including the data provider, the data user, the data creator, the data creation time, the signature of the data provider, and the signature of the data user; The product name, product description, and data format of the data product; The usage strategy includes preset usage methods, start date, end date, allowed number of accesses, usage region, and whether downloads are allowed; The legal constraints on the data products include pre-defined breach scenarios, handling measures, scope of compensation, and dispute resolution methods.

Images